Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!mcsun!ieunet!ieunet!dec4ie.ieunet.ie!jkh From: jkh@whisker.lotus.ie (Jordan K. Hubbard) Subject: Re: [NetBSD 0.9] File system corruptions In-Reply-To: adam@veda.is's message of 14 Sep 93 14: 57:54 GMT Message-ID: <JKH.93Sep14200134@whisker.lotus.ie> Sender: usenet@ieunet.ie (USENET News System) Nntp-Posting-Host: whisker.lotus.ie Organization: Lotus Development Ireland References: <MARK_WEAVER.93Sep14041323@excelsior.cs.brown.edu> <CDCMwx.6DJ@veda.is> Date: Tue, 14 Sep 1993 20:01:34 GMT Lines: 18 >FreeBSD has the same problem, but it might manifest slightly differently >with different hardware, or maybe not at all with some hardware (this >applies to NetBSD also). The wd driver is either not stable enough or not Actually, FreeBSD does not use the Barsoom driver, so it's hard to say whether or not it will have this problem for you. When one of our group attempted to run NetBSD on one of his IDE machines, it died an evil death, and ever since then we've decided to stick with our driver until we know a little more about what's wrong with the Barsoom code. This is an active topic of discussion on the freebsd mailing lists at the moment, and all I can promise is that all known bugs are being worked on. Jordan -- Jordan Hubbard jkh@violet.berkeley.edu, jkh@al.org, jkh@whisker.lotus.ie