Bug#235579: discover should be able to edit the module configuration
Package: discover
Version: 1.5-2
Severity: wishlist
I have a laptop. My configuration never changes. Discover runs on every
boot, and I boot many times a day. Each discover run takes like 30s
time.
It was very good to have discover when I installed the system. But now
it is annoying me.
I would like to have some option like runonce, so that it detects all my
hw it can find on installation, or on a new release of discover, then it
just edits my module configuration (ex. /etc/modutils/discover for 2.4,
/etc/modprobe.d/discover for 2.6), adding some aliases, like
alias eth0 e100
alias sound-slot-0 maestro or whatever.
So that next time I don't have to run discover to load a bunch of unused
modules, taking my memory, and taking a lot of time to detect the same
hardware configuration again, but when I want to use something the
corresponding module gets loaded automatically.
If there are some modules that can't get loaded automatically (I am
really sorry such things exist) those can be added to /etc/modules so
that they are loaded at boot always.
Regards,
Gabor
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: LANG=C, LC_CTYPE=C
Versions of packages discover depends on:
ii dash 0.4.21 The Debian Almquist Shell
ii debconf 1.3.22 Debian configuration management sy
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libdiscover1 1.5-2 hardware identification library
-- debconf information excluded
Reply to: