Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!pipex!sunic!EU.net!ieunet!news.ieunet.ie!jkh From: jkh@whisker.hubbard.ie (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.questions Subject: Re: Stable *BSD for Intel Date: 27 Mar 1994 13:28:02 GMT Organization: Jordan Hubbard Lines: 22 Distribution: world Message-ID: <JKH.94Mar27142802@whisker.hubbard.ie> References: <2l81of$rmp@pdq.coe.montana.edu> <2lqd2a$12e@pdq.coe.montana.edu> <1994Mar15.205532.19577@pegasus.com> <MYCROFT.94Mar17222306@duality.gnu.ai.mit.edu> <2mnb20$8us@pdq.coe.montana.edu> <CGD.94Mar26180926@eden.CS.Berkeley.EDU> NNTP-Posting-Host: whisker.hubbard.ie In-reply-to: cgd@eden.CS.Berkeley.EDU's message of 26 Mar 94 18:09:26 In article <CGD.94Mar26180926@eden.CS.Berkeley.EDU> cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: well, i saw at least one piece of mail go by in which the author of the mail claimed that the new FreeBSD wd driver did "Bad Things" (TM) to his file systems... It's funny how such people are always willing to yell about something like that in public but go strangely silent when you ask them to report such things directly to the maintainers for examination. 9 times out of ten, what transpires is that the culprit has done something functionally equivilent to plugging their ethernet controller into the toaster oven, or something similarly boneheaded. I think they secretly suspect as much and thus find it easy to post but become more reluctant when asked to actually try to debug the problem with the aid of one of the developers! :-) I also don't think that this is a problem endemic to FreeBSD. I'm sure the NetBSD camp could share a few war stories! :-) Jordan -- Jordan K. Hubbard FreeBSD core team Electric Bivalves Anonymous On the net, no one can hear you scream.