Date: Wed, 10 Jul 1996 10:37:29 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: davidg@Root.COM Cc: Joe Greco <jgreco@brasil.moneng.mei.com>, dawes@rf900.physics.usyd.edu.au, SimsS@infi.net, hackers@freebsd.org Subject: Re: Some recent changes to GENERIC Message-ID: <199607101637.KAA23661@rocky.mt.sri.com> In-Reply-To: <199607101554.IAA04210@root.com> References: <199607101541.KAA25663@brasil.moneng.mei.com> <199607101554.IAA04210@root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > What's wrong with using -c at the Boot: prompt? Rebuilding the kernel is > certainly not necessary to get the change in an "emergency" situation. Because it's basically un-documented until *after* the system is installed. It would be nice to have it explained in the README where you get the boot floppies, but it isn't. (Or is it that I don't see it in the GAMMA distribution). > >However, I will definitely scream if anyone removes sio2/sio3. Disabled by > >default, MAYBE. Removed, NO. I have seen far too many people who have > >three or four STANDARD SERIAL PORTS and sio2/3 directly map to COM3/4. > >There should be NO reason to screw around with this. These lines support > >standard PC hardware. If you remove them, remove sio1 too because you > >obviously only need one serial port to do an install. > > We have no mechanism in -stable to disable devices by default. "COM3" and > "COM4" aren't 'standard', either. For one thing, the interrupt selections > for these are often switched. I agree to a point, but see below. > >I fail to see what dropping sio2/sio3/ed1 buys anyways, since these device > >drivers are already required by sio0/sio1/ed0. I assume it might save a FEW > >bytes in kernel size for the extra entries. BIG stinkin' deal. That's a > >small price to pay for making it work the way people would expect. > > We have to remove sio3 because we can't disable it by default and > it conflicts with the most common SVGA cards. The only other > option is to bring in the necessary changes to config(8) to allow > "disable". Considering that we're in code freeze and about 3 days > from a release, this seems just a little bit crazy to me...but > hey, I aim to please! :-) Jordan already did that last night. :( While I don't really agree with it coming in so soon, as long as it's there you may as well use it. (He brought it in for the psm0 driver), which should be 'disabled' by default due to keyboard conflicts. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607101637.KAA23661>