Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.bugs Subject: Re: more on the "mysterious reboot" problem Date: 25 Jan 1995 20:00:59 GMT Organization: University of California, Berkeley Lines: 20 Message-ID: <3g6alr$9pk@agate.berkeley.edu> References: <3g520d$amg@satisfied.elf.com> <3g61sh$imt@ivory.lm.com> NNTP-Posting-Host: violet.berkeley.edu In article <3g61sh$imt@ivory.lm.com>, Peter Berger <peterb@telerama.lm.com> wrote: >I also noticed the "mving files between MSDOS filesystems and FFS filesystems >causes spontaneous reboot" problem as well; I haven't noticed this since I >replaced the hardware, but I haven't pushed too hard either. Maybe I'll >do some testing tonight. This is a known bug, and is fixed in -current. >On a related note, I compiled a kernel -without- the options MSDOSFS option, >but can still mount my msdos filesystem. I do get an ugly looking message >when booting, though. Need I worry, or is that just lint? You're now using the MSDOS LKM - make sure that root is the FIRST thing in your /etc/fstab, probably /usr too if you have it on a seperate filesystem. This is because modload is looking for ld when the msdos filesystem is seen. Jordan