From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Excluding some device types from persistent-net (xen, s390)
Date: Thu, 12 Apr 2007 07:44:10 +0000 [thread overview]
Message-ID: <200704120944.10520.zzam@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
Hi there!
I have a change to persistent-net behaviour, to exclude xen-devices, and
s390-devices.
Can that rule be formatted better?
Does that syntax work: SUBSYSTEMS!="xen|ccwgroup"
I saw the ACTION!="add|change" commit, but does that apply to the SUBSYSTEMS
list also?
Matthias
--
Matthias Schwarzott (zzam)
[-- Attachment #2: udev-108-persistent-net-excludes.diff --]
[-- Type: text/x-diff, Size: 1151 bytes --]
diff --git a/extras/rule_generator/75-persistent-net-generator.rules b/extras/rule_generator/75-persistent-net-generator.rules
index 21eb0c6..72d3412 100644
--- a/extras/rule_generator/75-persistent-net-generator.rules
+++ b/extras/rule_generator/75-persistent-net-generator.rules
@@ -1,6 +1,7 @@
# these rules generate rules for persistent network device naming
-ACTION=="add", SUBSYSTEM=="net", KERNEL=="eth*|ath*|wlan*|ra*|sta*" \
+ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS!="xen", SUBSYSTEMS!="ccwgroup" \
+ KERNEL=="eth*|ath*|wlan*|ra*|sta*" \
NAME!="?*", DRIVERS=="?*", GOTO="persistent_net_generator_do"
GOTO="persistent_net_generator_end"
@@ -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}"
[-- Attachment #3: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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
next reply other threads:[~2007-04-12 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 7:44 Matthias Schwarzott [this message]
2007-04-12 10:14 ` Excluding some device types from persistent-net (xen, s390) Kay Sievers
2007-04-12 10:33 ` Matthias Schwarzott
2007-04-12 11:33 ` Cornelia Huck
2007-04-12 12:30 ` Kay Sievers
2007-04-12 13:22 ` Matthias Schwarzott
2007-04-12 13:47 ` Cornelia Huck
2007-04-12 14:12 ` Mike Frysinger
2007-04-13 14:44 ` Cornelia Huck
2007-04-13 14:51 ` Mike Frysinger
2007-04-13 15:05 ` Cornelia Huck
2007-04-13 20:08 ` Matthias Schwarzott
2007-04-14 11:46 ` Matthias Schwarzott
2007-04-14 12:35 ` Matthias Schwarzott
2007-04-16 8:16 ` Cornelia Huck
2007-04-18 21:00 ` Matthias Schwarzott
2007-04-20 11:27 ` Cornelia Huck
2007-04-21 13:35 ` Matthias Schwarzott
2007-04-23 9:03 ` Cornelia Huck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704120944.10520.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.