Hi List,
Yesterday, I applied all available patches on a SLES10-SP2 machine using
YaST Online Update.
Since I updated, every time I reboot the machine, the file
/etc/udev/rules.d/30-net_persistent_names.rules is modified.
After 3 reboots, my file contains :
> SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.eb08",
> IMPORT="/lib/udev/rename_netiface %k eth0"
> SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.eb00",
> IMPORT="/lib/udev/rename_netiface %k eth1"
> *SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.eb00",
> IMPORT="/lib/udev/rename_netiface %k eth2"
> SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.eb00",
> IMPORT="/lib/udev/rename_netiface %k eth3"
> SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.eb00",
> IMPORT="/lib/udev/rename_netiface %k eth4"
> *
Any clues ?
Here is some info :
SVLD10C0:~ # vmcp q v nic
> Adapter EB00.P00 Type: QDIO Name: UNASSIGNED Devices: 3
> MAC: 02-01-03-00-00-1D VSWITCH: SYSTEM VS096SGS
> Adapter EB08.P00 Type: QDIO Name: UNASSIGNED Devices: 3
> MAC: 02-01-03-00-00-1E VSWITCH: SYSTEM VS021SGS
>
SVLD10C0:~ # uname -a
> Linux SVLD10C0 2.6.16.60-0.33-default #1 SMP Fri Oct 31 14:24:07 UTC 2008
> s390x s390x s390x GNU/Linux
>
SVLD10C0:~ # SPident -vv
>
> Summary (using 232 packages)
> Product/ServicePack conflict match update (shipped)
> SLE-10-s390x 0 0% 63 27.2% 46 (1992 3.2%)
> SLE-10-s390x-SP1 0 0% 101 43.5% 47 (2086 4.8%)
> SLE-10-s390x-SP2 0 0% 184 79.3% 47 (2181 8.4%)
> Unknown 48 20.7%
>
> Legend for Package Details:
> - conflicting package (found < expected)
>
> CONCLUSION: System is up-to-date!
> found SLE-10-s390x-SP2 + "online updates"
>
Thanks.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
