On Tue, Jul 28, 1998 at 03:28:05AM +0200, Wichert Akkerman wrote:
> Previously Rob Browning wrote:
> > Can this go away when we move to the 2.2 kernel if we switch over to
> > using the module daemon to load all modules on demand?
>
> You can't do that for lowlevel SCSI drivers and NIC drivers.
Speaking of which, are there any plans to move to an initrd-based setup
for the standard kernel image, so that less of those lowlevel SCSI drivers
need to be compiled into the default kernel?
Right now, the first thing I do after installing Debian is compile a
custom kernel to get rid of all those other SCSI drivers I don't need.
On my laptop this saved me over 400K of RAM. (well, I needed to recompile
to get APM, anyway, which is definitely *not* something that can be
enabled by default)
Kernel-package does make compiling a kernel easy, but I imagine that not
everyone has space for 40MB of kernel sources, or the inclination to
compile, reboot, and face the possibility of recompiling if something
goes wrong.
How substantial a change to the boot floppies would this entail? I guess
the Rescue Disk would have to continue using a monolithic,
'one-size-fits-all' kernel, but it also seems like a good idea to make
the Rescue Disk specifically geared to system rescue, and use a different
disk for starting the installation.
I know this has been talked about before, and IIRC the consensus was
'wait till after Hamm is released'... is it doable, or even desireable,
for slink?
Cheers
--
David Huggins-Daines - bn711@freenet.carleton.ca
PGP public key #63A8B719 on public key servers
fingerprint=4F 38 A2 34 E1 E0 B7 6E C3 DA 6C E3 C6 6A 05 62
Attachment:
pgpnCmSaQ3KR_.pgp
Description: PGP signature