From owner-freebsd-hackers  Sun Nov  5 08:03:01 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA04937
          for hackers-outgoing; Sun, 5 Nov 1995 08:03:01 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA04931
          for <hackers@freebsd.org>; Sun, 5 Nov 1995 08:02:57 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA08360; Mon, 6 Nov 1995 02:58:19 +1100
Date: Mon, 6 Nov 1995 02:58:19 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199511051558.CAA08360@godzilla.zeta.org.au>
To: bde@zeta.org.au, grog@lemis.de
Subject: Re: machine reboot & kernel maxusers option
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
Precedence: bulk

>> >need to keep things in that you don't have (I haven't found a clean
>> >way to remove CD-ROM support, for example).  You're right, though,
>> >that doesn't make it good.
>> 
>> I would at least disable the drivers for hardware that doesn't exist.
>> This doesn't reduce the space bloat but it makes driver probes more
>> reliable and turns "Not found" warnings into errors.

>Sure, but how?  If I remove CD-ROM support for my dickless
>workstations, I get unresolved references from other modules which do
>need to stay.  Sure, I could go in and throw in some #ifdefs--maybe.
>But that's going beyond a simple kernel rebuild.

I meant to just turn off the the driver enable flag at boot time.

The cdrom support should already be correctly ifdefed.  It's a bit harder
to remove than most drivers because there is an option (ATAPI) for it as
well as a driver (wcd0).

Bruce