From: Philip_Perucci@p100.f2003.n241.z2.fidonet.org (Philip Perucci) Subject: 386bsd, linux: which runs mo.. Date: Fri, 26 Mar 1993 11:22:00 GMT
AREA:COMP.OS.LINUX
From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci)
Organization: Naval Medical Research & Development Command
In article <1993Mar24.205842.5753@ucsu.Colorado.EDU> farrow@ucsu.Colorado.EDU
(J. Scott Farrow) writes:
>root@hal.gnu.ai.mit.edu (Square Root) writes:
>
>>In article <SCT.93Mar24134609@colonsay.dcs.ed.ac.uk> sct@dcs.ed.ac.uk
>>(Stephen Tweedie) writes:
>>>
>>> There have been quite a few reports recently of apparent file system
>>> problems occurring because of SCSI problems, but I have not heard of
>>> any actual extfs bugs recently.
>
>>That seems unlikely to have been my problem, since the machine it lost
>>on most frequently has an ESDI disk.
>
>>> If you could give some idea of what your problems are, it might be
>>> possible to isolate the problem and even find a solution.
>
>>It is not worth my time to track it down.
>
>Then why are you bitching about it?
>
>For my $.02 worth, I have been using extfs since September and haven't had
>a single problem with it. The one time I trashed the fs so bad that the
>machine wouldn't boot, I just booted off a floppy, ran efsck, and had no
>further problems with it.
The Linux file-systems are pretty stable. I have used minix, e2fs, and
extfs, all with no problems. I am currently in the process of getting
up 386BSD (had to send my HD back for another) for networking and BSD
portability, but sure wish the BSD file-system had the "-c" switch on
"newfs" the way Linux does on "mkfs". It sure is nice to automagically scan
for bad blocks with Linux...