Re: trimmed down rescue/root/driver disk sets
Randolph Chung wrote:
> A question for you all: what is the minimum set of options that need to be
> built into the kernel?
The following comments are my opinions as a Debian user and do not
reflect attitudes or philosophies subscribed to by the boot-floppies
In my case, I don't need much. As long as the kernel can read the IDE
disks and CD, I'm fine. The first thing I do after running the install
is replace the kernel and module library with ones built for my
production config. I exit the installation selecting "no" to the tasksel
and "quit" when getting to dselect. I return to dselect's apt-get
method after replacing the kernel and module library and configuring the
system to use the network. Most people probly wouldn't do that though.
It's no big deal for me since the whole thing is scripted.
Personally, I think it wouldn't be bad to have a set of kernels
available to install with. It seems rather a big bite to chew using a
single kernel that is expected to support many different
configurations. IMHO, the present kernel is already too bloated and
inadequate for use in a production system.
I think it is a good idea to stick with multiple driver disks since
incorporating drivers into the kernel for the sake of minimizing the
number of disks is not worth further convolving an already convoluted
situtation. Another possibility would be to offer the option of using
driver disks on an individual basis with driver groupings based on
typical configurations. In my special case, it would be nice to be able
to skip the driver disks completely since I don't need to load any. On
the other hand, if there were a big enough set of kernels available,
then the necessity to load modules during install could be practically
eliminated. But that might be bad mojo to get away from the modular
philosophy and a maintenance nightmare to boot, so to speak.
Having seperate boot and root disks may simplify the process of kernel
selection in the event that multiple kernels are made available. So
keeping them seperate may be a good thing.
Craig H. Block, Debian ia32 user
Linux 2.2.13 SMP i686 building CVS bf