So, a slightly more detailed plan for fixing this:
- Add a script to rootskel that will run before udev and check the
kernel command line for things of the form: module.param=value
and call register-module to add the parameter.
(Done in svn.)
- Modify register-module to not always add modules to /etc/modules.
There needs to be a way to make it only register parameters for a
module:
register-module -p -a module params
(Done in svn.)
- Modify register-module to write to /etc/modules.conf in the d-i
initrd, so that modprobe will pick up the module params for 2.4
kernels.
(Done in svn.)
- Modify register-module to also write to /etc/modprobe.d/ (d-i and
/target), so it will work with 2.6.
(Done in svn.)
- Modify syslinux boot screens to document the right parameter names
including the module names.
(Done, uncommitted.)
- Remove all the code in hw-detect (and anything else) to prompt for
module parameters with debconf. Only support passing module params at
the kernel command line.
- Update manual.
One unresolved thing is that this yeilds some silly stuff like
"floppy.floppy=thinkpad". Does the kernel require that if floppy is
built in, or does it special case it in the case where the module and
parameter are the same so that floppy=thinkpad works? We should strive
to match whatever strings work when a module is built into the kernel.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature