Date: Sat, 18 Jun 2011 14:35:44 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-arch@freebsd.org Subject: Re: [RFC] shipping kernels with default modules? Message-ID: <iti62s$arn$1@dough.gmane.org> In-Reply-To: <20110611171834.GA38142@zim.MIT.EDU> References: <BANLkTin2AwKRT7N6HWqBctJcT72_mR=Otg@mail.gmail.com> <20110611171834.GA38142@zim.MIT.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/06/2011 19:18, David Schultz wrote:
> OS X has an interesting solution, intended to preserve the
> flexibility of dynamic modules, while minimizing boot time.
> It provides a kextcache utility, which packages the kernel
> and all of the needed modules into a single binary for better
> locality on disk. Unlike recompiling the kernel, running
> kextcache is fast, and the system runs it automatically when
> hardware or driver changes necessitate it.
This seems like the goldilocks solution, but also dangerously close to
the Linux's horrendeous initrd system where, if you change the disc
controller (which nowadays can mean simply switching it in BIOS from ATA
to AHCI to RAID modes) and you get a magically unbootable system.
I'd go for something like that only if there's a fallback mode acting
like "ok, the previous boot failed, now automagically load ALL the
modules and try again". You pretty much need to load all the drivers
because except for some obvious exceptions (like the sound drivers,
VESA, etc.) many can host devices for file systems ("normal"
controllers, network cards, iSCSI, GEOM, USB, Infiniband, etc.). Doing
it without this kind of fallback mode is a step backwards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?iti62s$arn$1>