Date: Mon, 27 May 1996 01:21:52 +1000 From: Bruce Evans <bde@zeta.org.au> To: j@uriah.heep.sax.de, jkh@time.cdrom.com Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/1250: chroot to nullfs causes kernel panic Message-ID: <199605261521.BAA30237@godzilla.zeta.org.au>
next 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? Yes, the broken stuff should all be disabled except for things that are actually used like nfs and msdosfs. For file systems, disablement is easy - just don't build the lkms, and mark things as broken in LINT. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605261521.BAA30237>