Return to BSD News archive
Xref: sserve comp.os.linux:31026 comp.os.386bsd.questions:1011 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!curtis From: curtis@cs.berkeley.edu (Curtis Yarvin) Newsgroups: comp.os.linux,comp.os.386bsd.questions Subject: Re: 386bsd, linux: which runs more out of the box? Date: 24 Mar 1993 21:56:53 GMT Organization: CS Dept. Snakepit - Do Not Feed. Lines: 32 Message-ID: <1oqlf5$i8b@agate.berkeley.edu> References: <CGD.93Mar23030821@erewhon.CS.Berkeley.EDU> <hwr.732890376@snert.ka.sub.org> <SCT.93Mar23224452@belnahua.dcs.ed.ac.uk> NNTP-Posting-Host: cobra.cs.berkeley.edu In article <SCT.93Mar23224452@belnahua.dcs.ed.ac.uk> sct@dcs.ed.ac.uk (Stephen Tweedie) writes: >hwr@snert.ka.sub.org (Heiko W.Rupp) writes: > >> There is another thing to consider: 386bsd has a stable BSD-FFS and >> stable networking, while there are bugs in the Linux efs and in their >> networking. > >Whoah there!!!! > >To the very best of my knowledge - and filesystems is What I Do on Linux >- there are no known bugs in the efs, minix or xiafs file systems. Bollocks. I've had huge problems with the minix filesystem in a number of recent releases, and I've seen reports of similar-looking efs snafus. This isn't a SCSI problem; I have IDE. My guess, in fact, is that the bug is in fsck (and efsck, which is based on fsck). The "standard" SLS system doesn't run fsck on boot, so it's not surprising that there have been few such bug reports; I think we might see a lot more if Peter got round to putting a decent shutdown/rc package in SLS. I don't mean to be complaining about free software, but I've lost a lot of valuable data from the minix fs on a lot of occasions, and it rather disturbs me when people claim that it's bug-free. Fsck is a necessary part of the filesystem; if you can't recover all written data after an arbitrary crash, then your filesystem is broken. Period. c