
TODO for modutils
-----------------

[ Bug 64260, ]
- Have update-modules store a md5sum file of modules.conf in
/var/lib/modutils/modules.conf.md5sum and compare against these file
everytime it tries to generate it. It could either warn the user 
his changes will be modified or abort.

Another alternative, to permit users changes of modules.conf, is to
have modules.conf point to a static place (/var/lib/modutils/modules?),
and have update-modules modify that static place instead of modules.conf.
So that the user can break the relationship by breaking the symlink.
This also avoids the hack of comparing if /etc/modules.conf is autogenerated
or not.

This needs to be though of carefully, and consider upgrades from previous
situations.

[ Bug 109776 ]
- It might be worthwhile having rc.modutils load /etc/modules-$KVER as
module-init-tools does. The bug report provides a generic patch that does it.
If this package should not support 2.6 kernels (and users should be redirected
to module-init-tools) then proper code should be added to detect if the 
user is running modutils with a 2.6 kernel and appropiate warning notes
should be presented (in postint too, maybe)

[ Bug 116142 ]
- Generating modules.conf is a hack (but very convenient) that might force
user's mistakes (#64260) because most documentation out there probably says
it should be modified. Maybe the include directive can be used to change
the way modutils works (but then, arch directories probably need to use
'if XXX' statements)

[ Bug 134813 ]
- lsmod and kernelversion should be in /bin instead of /sbin, however, since
module-init-tools already provides an 'lsmod' it needs to be diverted. 
This changes needs investigation (where there module-init-tools that didn't
divert lsmod?) so that appropiate Conflicts: are added.

[ Bug 212176 ]
- Patch for AMD64 support, should be reviewed and included.

[ Bug #224669 ]
- Support for sparc62 when running sparc32 in depmod, tricky, since it
bases itself on uname.

[ Other stuff ]
- Make the package build using debhelper, since it might be better 
  (for maintenance, and policy compliance) than what it's currently done.
