With the introduction of modutils 2.1.85-12 I think it's time to discuss kernel modules in here. I'm new on this list, so be gentle :) There are a couple of things about modules that should IMHO be stated in policy: 1) where to install modules. 2) how to configure modules 1) is outlined in /usr/doc/modutils/placement.Debian.gz, which I won't repeat here. 2) has changed with the latest modutils package. In the old days everything was configured in /etc/conf.modules. This proved to be a less then optimal solution when Roman Hodek told me m68k actually has conflicting configuration options for different subarchitectures. This, together with the problem that some packages needed to modify /etc/conf.modules (most noticably the alsadriver package) let me do redesign this. Inspired by the menu-system there is now a /etc/modutiles directory, where all packages can put a file with their own configuration. This means packages don't have to directly modify /etc/conf.modules anymore. It also introduces update-modules, which scans those files and creates a new global configuration. I propose a section for this is added to policy manual which states both points. What I'm not entirely sure about is how to handle depmod. Currently update-modules doesn't run it, but it might be a good idea to do so. Wichert. -- ============================================================================== This combination of bytes forms a message written to you by Wichert Akkerman. E-Mail: wakkerma@wi.LeidenUniv.nl WWW: http://www.wi.leidenuniv.nl/~wichert/
Attachment:
pgpMSBTZI9_yU.pgp
Description: PGP signature