Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!gatech!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!acs.ucalgary.ca!cpsc.ucalgary.ca!xenlink!fsa.ca!deraadt From: deraadt@fsa.ca (Theo de Raadt) Subject: Re: my bug list In-Reply-To: sef@Kithrup.COM's message of 27 Feb 1993 19: 59:28 -0800 Message-ID: <DERAADT.93Mar11154207@newt.fsa.ca> Sender: news@fsa.ca Nntp-Posting-Host: newt.fsa.ca Organization: little lizard city References: <C33u2A.Ap0@unix.portal.com> <1993Feb27.235240.7476@coe.montana.edu> <1mpdb0INNo8a@ftp.UU.NET> Date: Thu, 11 Mar 1993 22:42:07 GMT Lines: 21 nate@cs.montana.edu (Nate Williams) writes: >They do things that Berkeley Unix avoids. In article <1mpdb0INNo8a@ftp.UU.NET> sef@Kithrup.COM (Sean Eric Fagan) writes: > Since all commercial unices, as well as Linux, manage to work around this, > the thing that they do, that Berkeley Unix avoids, must be "working > correctly." It's unbelievable how often this comes up. Normal Berkeley Unix resets the entire world when it comes up. 386BSD is broken because it does NOT. The device configuration architecture in 386BSD is very weak compared to normal Berkeley Unix. Don't get fooled into thinking that 386BSD == Berkeley Unix. -- This space not left unintentionally unblank. deraadt@fsa.ca