Package: ifplugd Version: 0.28-4 Severity: wishlist Here is better integration idea for ifplugd to ifupdown and other network scripts.
Currently, ifplugd uses -i option to specify interfaces to control. Actually, debconf stores them for each occasion in /e/default/ifplugd as: INTERFACES="" HOTPLUG_INTERFACES="" Since recent ifupdown started using "allow-[CLASS]", it may be a good idea to support "allow-ifplugd-auto" stanza and "allow-ifplugd-hotplug" which specify interfaces for each types. (I think current debconf script needs to be changed though) Since these [CLASS] are not used by other programs, it means nothing to others and I think no new code need to be written for ifupdown. With this entry, you only need to see /e/n/interfaces to know which interfaces are controled by which program. * auto or allow-auto: boot script of ifupdown * allow-hotplug: hotplug script (probably run bu udev) * allow-ifplugd-auto: boot script of ifplugd * allow-ifplugd-hotplug": hotplug script (probably run bu udev) which invoke ifplugd I think similar idea can be deployed for waproamd too. Then configuration is much more clear. Please note this idea has not been fully tested. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ifplugd depends on: ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy ii libc6 2.7-9 GNU C Library: Shared libraries ii libdaemon0 0.12-1 lightweight C library for daemons Versions of packages ifplugd recommends: ii ifupdown 0.6.8 high level tools to configure netw -- debconf information: * ifplugd/interfaces: * ifplugd/hotplug_interfaces: * ifplugd/args: -q -f -u0 -d10 -w -I * ifplugd/suspend_action: stop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]