Package: udev Version: 0.125-7 Severity: normal
user case (1): - one of my customers bought a Linux system that uses the /etc/network/interfaces file with wpa_supplicant and the wlan0 device to enable an configure his secure network now something happens with the network card, being in this case an usb wireless stick. And the user buys a new Linux compatible device from his favorite Linux shop. He plugs in the device reboots his computer and his network does not work! He gets frustrated blames Debian and Linux and the local person of the Linux shop. The Linux shop need to refund the device and possible guarantee clams that tolled him it will work directly. user case (2): - one of my customers is upgrading his system and after upgrading the network does not work anymore... problem (1): - udevs persistent-net-generator names new hardware in an incrementing way, for example I plug in wlandevice(0) and it becomes wlan0 then I remove the stick because it is broken, and add a new one the generator will name it as wlan1 and the network will not work because it is configured for wlan0. solution (1): - change the behavior of the persistent-net-generator. Only increment a device name when there is a device attached with the used name for example, I plug in wlandevice0 it will become wlan0 if I add an other wlandevice1 it will become wlan1, but if I removed wlandevice0 and then add wlandevice1 it should become wlan0 so the network settings do not break! Of course there are situations where wlan1, wlan2, wlan3 are wanted but this is more likely to be an advance user that and can setup his network on his own. But for non computer literate person the network should just keep working when configured. problem (2): - somehow a new version of udev and kernel detects the device differently and renames the devices as a new wlan1 device, breaking the previous working network configuration. solution (2): - make sure configuration file are backwards compatible and wont break excising network configuration. Also see solution (1). ---- I have had several cases where the network configuration becomes broken after upgrading or plugging in new devices. The frustration for my customers are high, because they don't understand why it is so fragile and unreliable in there eyes. It gets me personally a bad name and I lose money because of this issues on guarantee claims. I am willing to help with a developer to provide a possible solution. I would very much like this issue to be discussed. Thanks in advance, Jelle de Jong -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages udev depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-16 GNU C Library: Shared libraries ii libselinux1 2.0.65-5 SELinux shared libraries ii libvolume-id0 0.125-7 libvolume_id shared library ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip udev recommends no packages. udev suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
