From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Schwarzott Date: Thu, 12 Apr 2007 13:22:05 +0000 Subject: Re: Excluding some device types from persistent-net (xen, s390) Message-Id: <200704121522.05069.zzam@gentoo.org> MIME-Version: 1 Content-Type: multipart/mixed; boundary="Boundary-00=_9JjHGO7VSs4k9IP" List-Id: References: <200704120944.10520.zzam@gentoo.org> In-Reply-To: <200704120944.10520.zzam@gentoo.org> To: linux-hotplug@vger.kernel.org --Boundary-00=_9JjHGO7VSs4k9IP Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Donnerstag, 12. April 2007, Kay Sievers wrote: > On Thu, 2007-04-12 at 12:33 +0200, Matthias Schwarzott wrote: > > On Donnerstag, 12. April 2007, you wrote: > > > On 4/12/07, Matthias Schwarzott wrote: > > > > I have a change to persistent-net behaviour, to exclude xen-devices, > > > > and s390-devices. > > > > > > It's not needed, or does not work for xen and s390? > > > > xen creates random macs per default I think. And s390 does create macs on > > login or similar? Perhaps someone really using a s390 could comment on > > this. > > > > > or does > > SUBSYSTEMS=="xen|ccwgroup", GOTO="persistent_net_end" > > or > > That should work too, only the != has the weird behavior. > Updated patch with this variant attached. Now we can discuss if the rules itself are usfull. 1. xen: I think for xen the persistence framework itself is not usefull, as the order of the devices is every time the same, isn't it. The only known problem is caused by the rules itself: When mac is randomly assigned udev counts up xen[0-9]. 2. s390 / ccwgroup I have no such machine, but I have this request to re-add (the for s390 completely removed persistence-net): http://bugs.gentoo.org/show_bug.cgi?id=173797 Cornelia Huck (IBM Deutschland Entwicklung GmbH) wrote: > There are a few cases where the mac address can be zero (some VM Guest > Lan, iirc), and some ccwgroup devices don't have a mac address (keep in > mind that ccwgroup is just the bus; devices can be fundamentally > different, like qeth and ctc). But these cases should be handled well > during persistent rule generation. > > Also, not all s390 network devices are on the ccwgroup bus; however > netiucv device are already excluded since they use iucv* and don't have > mac addresses anyway. that is part of the used rules: apply persistence only on this condition: KERNEL=="eth*|ath*|wlan*|ra*|sta*" That means qeth and ctc (if that is the device name) should already be ignored. Matthias -- Matthias Schwarzott (zzam) --Boundary-00=_9JjHGO7VSs4k9IP Content-Type: text/x-diff; charset="iso-8859-15"; name="udev-108-persistent-net-excludes.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="udev-108-persistent-net-excludes.diff" diff --git a/extras/rule_generator/75-persistent-net-generator.rules b/extras/rule_generator/75-persistent-net-generator.rules index 21eb0c6..eeef4d1 100644 --- a/extras/rule_generator/75-persistent-net-generator.rules +++ b/extras/rule_generator/75-persistent-net-generator.rules @@ -1,5 +1,6 @@ # these rules generate rules for persistent network device naming +SUBSYSTEMS=="xen|ccwgroup", GOTO="persistent_net_generator_end" ACTION=="add", SUBSYSTEM=="net", KERNEL=="eth*|ath*|wlan*|ra*|sta*" \ NAME!="?*", DRIVERS=="?*", GOTO="persistent_net_generator_do" @@ -10,7 +11,6 @@ LABEL="persistent_net_generator_do" SUBSYSTEMS=="pci", ENV{COMMENT}="PCI device $attr{vendor}:$attr{device} ($attr{driver})" SUBSYSTEMS=="usb", ENV{COMMENT}="USB device 0x$attr{idVendor}:0x$attr{idProduct} ($attr{driver})" SUBSYSTEMS=="ieee1394", ENV{COMMENT}="Firewire device $attr{host_id})" -SUBSYSTEMS=="xen", ENV{COMMENT}="Xen virtual device" ENV{COMMENT}=="", ENV{COMMENT}="$env{SUBSYSTEM} device ($attr{driver})" IMPORT{program}="write_net_rules $attr{address}" --Boundary-00=_9JjHGO7VSs4k9IP Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV --Boundary-00=_9JjHGO7VSs4k9IP Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel --Boundary-00=_9JjHGO7VSs4k9IP--