Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!usc!howland.reston.ans.net!pipex!zaphod.crihan.fr!jussieu.fr!ensta!itesec!frmug.fr.net!fasterix.frmug.fr.net!pb From: pb@fasterix.frmug.fr.net (Pierre Beyssac) Subject: Re: Stable *BSD for Intel References: <2mnb20$8us@pdq.coe.montana.edu> <CGD.94Mar26180926@eden.cs.berkeley.edu> <2n4h1c$ct4@pdq.coe.montana.edu> <hastyCnCns4.J54@netcom.com> Organization: considered harmful Date: Thu, 31 Mar 1994 00:34:09 GMT Message-ID: <1994Mar31.003409.10164@fasterix.frmug.fr.net> Lines: 29 In article <hastyCnCns4.J54@netcom.com>, Amancio Hasty Jr <hasty@netcom.com> wrote: >Well, this sort of postings doesn't help either FreeBSD or NetBSD... > >However, unbiased comments from users of either FreeBSD or NetBSD >will probably be vastly more useful. Okay, here we go... I used : NetBSD 0.8, NetBSD 0.9 and now I run FreeBSD 1.0.2. I have a single drive IDE. With NetBSD 0.8 and 0.9 I had problems with the wd driver locking regularly with the busy LED on, about once or twice a week. With FreeBSD 1.0.2 it became a nightmare. Same problem, much more often : about *6* lockups a day (generally during light to heavy disk usage). Since I have installed the "wd timeout" fix (still under 1.0.2) I haven't seen a single lockup. I'm waiting 1.1 to see how the new wd driver behaves. Sorry, that's all : no data corruption horror story to report :-) -- Pierre Beyssac FreeBSD@home: pb@fasterix.frmug.fr.net FreeBSD, NetBSD, Linux -- Il y a moins bien, mais c'est plus cher. You can also get less bang for more bucks. (translation F. Berjon)