kolejność interfejsów eth

[Daniel Dawid Majewski]

Pewnego dnia wpadła wieść od krzysztof manijak i powiedziała :
>>>> KERNEL=="eth?", SYSFS{address}=="00:01:02:03:04:05", NAME="wlan0"
>>>> KERNEL=="eth?", SYSFS{address}=="AA:BB:CC:DD:EE:FF", NAME="eth0"
>>> no próbowałem, ale może coś nie teges.... obadam jeszcze raz
>>> po czym poznać że to działa?
>> # udevadm test class/net/eth0
> 
> [root w smssrv etc]# udevadm test class/net/eth0
> This program is for debugging only, it does not run any program,
> specified by a RUN key. It may show incorrect results, because
> some values may be different, or not available at a simulation run.
> 
> parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/10-udev-example.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/13-netiface.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/40-alsa.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/50-udev-default.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/51-modprobe.rules' as rules file
> add_to_rules: PHYSDEV* values are deprecated and will be removed from a
> future kernel,
> please fix it in /etc/udev/rules.d/51-modprobe.rules:5parse_file:
> reading '/etc/udev/rules.d/55-hotplug_map.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/60-cdrom_id.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/60-persistent-input.rules' as
> rules file
> parse_file: reading '/etc/udev/rules.d/60-persistent-storage-tape.rules'
> as rules file
> parse_file: reading '/etc/udev/rules.d/60-persistent-storage.rules' as
> rules file
> parse_file: reading '/etc/udev/rules.d/61-persistent-storage-edd.rules'
> as rules file
> parse_file: reading '/etc/udev/rules.d/64-device-mapper.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/80-drivers.rules' as rules file
> parse_file: reading '/etc/udev/rules.d/95-udev-late.rules' as rules file
> unable to open device 'class/net/eth0'
Stary udev i konfiguracja...
Warto czasem się po własnym dysku rozejrzeć w okolicach
/usr/share/docs/udev*
>> No i oczywiście trywialne pytanie - która wersja udev ? 133 była popsuta
>> i właśnie losowało się coś z siecią...
> [root w smssrv etc]# rpm -q udev
> udev-124-2.x86_64
U mnie na TH  działa i to dwie karty na tym samym chipie
poldek:/all-avail> ls -I udev*
udev-135-2.x86_64
udev-core-135-2.x86_64
udev-initrd-135-2.x86_64
udev-libs-135-2.x86_64

-- 
Pozdrawiam,
Daniel Dawid Majewski
jabber:light-i/jid.pl