From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Excluding some device types from persistent-net (xen, s390)
Date: Thu, 12 Apr 2007 10:33:12 +0000 [thread overview]
Message-ID: <200704121233.12767.zzam@gentoo.org> (raw)
In-Reply-To: <200704120944.10520.zzam@gentoo.org>
On Donnerstag, 12. April 2007, you wrote:
> On 4/12/07, Matthias Schwarzott <zzam@gentoo.org> 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.
>
> > Can that rule be formatted better?
>
> With the current logic, only one SUBSYSTEMS-key (same for most other
> keys) is supported per rule.
> (I have a patch pending, that removes the limitation and just creates
> a big linear match/action from of the rules, without the limitation on
> the count of keys, but that patch is not finished now.)
>
> > Does that syntax work: SUBSYSTEMS!="xen|ccwgroup"
> > I saw the ACTION!="add|change" commit, but does that apply to the
> > SUBSYSTEMS list also?
>
> It should work for all match-keys, yes.
>
But that means for now I have to use
SUBSYSTEMS="xen", GOTO="persistent_net_end"
SUBSYSTEMS="ccwgroup", GOTO="persistent_net_end"
or does
SUBSYSTEMS="xen|ccwgroup", GOTO="persistent_net_end"
or
...., SUBSYSTEMS!="xen|ccwgroup", ...
work, as this IS just one SUBSYSTEMS per line.
Greetings
Matthias
--
Matthias Schwarzott (zzam)
-------------------------------------------------------------------------
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ÞVDEV
_______________________________________________
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 prev parent reply other threads:[~2007-04-12 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 7:44 Excluding some device types from persistent-net (xen, s390) Matthias Schwarzott
2007-04-12 10:14 ` Kay Sievers
2007-04-12 10:33 ` Matthias Schwarzott [this message]
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=200704121233.12767.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.