I might propose that any driver supported under sysinstall needs to support kldloading but I haven't really thought that through :-)
The issue here is that the BOOTMFS kernel has traditionally (for freebsd) been derived by filtering GENERIC. GENERIC has been changed in a way that causes BOOTMFS to be too large. With the current hack^Wmethod used by make release we are required to add elements to a shell script which deletes items from the GENERIC configuration to create BOOTMFS. If my proposition holds water we can do away with the linkage to GENERIC in favor of a statically defined and minimal BOOTMFS kernel. Cheers, Jerry Hicks [EMAIL PROTECTED] On Sunday, July 14, 2002, at 08:44 PM, Terry Lambert wrote: > W Gerald Hicks wrote: >> No, the problem is because the kernel has grown too large to >> fit on the md(4) filesystem prepared for it. >> >> src/release/<ARCH>/dokern.sh needs to be adapted to omit >> new drivers added to GENERIC. > > All drivers not in the boot or install paths should be omitted, but > only if it's possible to end up with a GENERIC without their > omission after the install is complete. > > This is actually a pretty thorny problem, since sound drivers > could be argued to be in the installation path at some point, > if one support interfaces for the blind (a putative pin-reader > driver that allowed the pins to follow a region surrounding the > mouse pointer would also fall into the same category). > > -- Terry > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
