Package: ifupdown Version: 0.6.8 Severity: wishlist It was unclear to me whether the renaming accomplished by mapping affected the name by which the device is known in the rest of the system. In particular, should iptables -i used the original name or the mapped name?
Inspecting /proc, /dev and ksysinfo seems to show the original name is the one used elsewhere, i.e., the mapping is only effective while /etc/network/interfaces is being processed. If that's true, it would be helpful to say so. (It's also unfortunate, since then one still needs to fiddle the firewall rules if the rules of the devices change.) A couple of semi-related points while I'm here: Some discussion of the relation of the mapping facility to the naming facilities provided by 2.6 kernels and udev would be useful. For example, is one method preferred over the other? The use of the keyword hotplug and reference to the hotplug "subsystem" implicit in the current language is a bit confusing, since the hotplug package was removed from Debian. I guess udev supplies hotplug functionality, and the keyword remains for historical reasons. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages ifupdown depends on: ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii net-tools 1.60-17 The NET-3 networking toolkit ifupdown recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
