dsl@ wrote: > On Wed, May 30, 2012 at 05:11:09PM -0700, John Nemeth wrote: > > On Oct 11, 4:10pm, "David Laight" wrote: > > } > > } Module Name: src > > } Committed By: dsl > > } Date: Mon May 21 21:34:16 UTC 2012 > > } > > } Modified Files: > > } src/sys/arch/i386/stand/lib: exec.c > > } src/sys/arch/sandpoint/stand/altboot: main.c > > } src/sys/lib/libsa: ext2fs.c ffsv1.c ffsv2.c globals.c lfsv1.c lfsv2.c > > } stand.h ufs.c > > } > > } Log Message: > > } Remove the code that tries to load the "ffs" kernel module during boot. > > } This is in line with the core decision than even modular kernels should > > } contain the ffs code. > > } I've left in the code that tries to load "nfs" and "ext2fs", but it > > } isn't clear that is necessary. > > } Removes a warning message that (usually) flashes past to fast to read. > > } AFAICT all the relevant kernels contain ffs (and nfs for that matter). > > > > Just because all shipping kernels are currently required to > > contain ffs doesn't mean a user can't build a kernel without it > > "knowing" that /boot will load the appropriate module. At the very > > least, this should have been a knob so that people can build a /boot > > that will load the appropriate filesystem if they wish. > > IIRC you can explicitly request (from boot.cfg) that any module be > loaded. There is no need for boot itself to always try to load > such a module. > > The problem is that there was no was of stopping boot trying to > load (typically) ffs.kmod, and if the kernel does contain it then > it doesn't seem correct at all.
Can't we have an option for autoloading rootfs modules, like console settings configurable via installboot? --- Izumi Tsutsui