Date: Sun, 26 May 1996 07:25:49 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: J Wunsch <j@uriah.heep.sax.de> Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/1250: chroot to nullfs causes kernel panic Message-ID: <19460.833120749@time.cdrom.com> In-Reply-To: Your message of "Sun, 26 May 1996 02:00:02 PDT." <199605260900.CAA15301@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ya know, it was tossed around as a working model before we released 2.0 that everything in the system should either be: 1. Working 2. Broken and disabled (badly broken) 3. Broken and documented as broken. #1 is obviously how you _want_ everything to be, #2 is a matter of facing reality and all the things you won't be able to do before release time. What we seem to have wound up with instead is 1. Working and 2. Broken. Stuff just hasn't been documented, nor have the gaping holes in the road been covered over. :-( Does anyone else think that a merciless drive to disable or document all of our broken filesystems and other misfeatures would be a good thing to start? Jordan > The following reply was made to PR kern/1250; it has been noted by GNATS. > > From: J Wunsch <j@uriah.heep.sax.de> > To: brion@queeg.com > Cc: FreeBSD-gnats-submit@FreeBSD.org > Subject: Re: kern/1250: chroot to nullfs causes kernel panic > Date: Sun, 26 May 1996 10:50:44 +0200 (MET DST) > > As Brion Moss wrote: > > > > >Number: 1250 > > >Category: kern > > >Synopsis: chroot to nullfs causes kernel panic > > nullfs is known to be broken. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIP E > Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19460.833120749>