From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Excluding some device types from persistent-net (xen, s390)
Date: Wed, 18 Apr 2007 21:00:11 +0000 [thread overview]
Message-ID: <200704182300.11920.zzam@gentoo.org> (raw)
In-Reply-To: <200704120944.10520.zzam@gentoo.org>
On Montag, 16. April 2007, Cornelia Huck wrote:
> On Fri, 13 Apr 2007 22:08:19 +0200,
>
> Matthias Schwarzott <zzam@gentoo.org> wrote:
> > s390: For s390 I don't know the facts, please others discuss if there is
> > something special necessary or not.
>
> It may be a good idea to use the bus id for ccwgroup devices, something
> like eth-0.0.fd00. Reasons:
> - Unlike the mac address, it is always there :)
> - It is unique. The bus id of the ccwgroup device is the bus id of the
> 'leading' slave ccw device, and ccw devices have unique ids.
>
> Maybe we should still leave out netiucv (iucv bus) devices, since they
> are created by the user writing the id of the remote VM guest...
That sounds like a good idea.
We just need some code:
Some questions for this:
1. should write_net_rules detect itself what kind of device - or should the
rules detect this (they already do) and pass this to write_net_rules?
2. How to get the unique identifier of that ccwgroup?
First from a udev-rule and then from write_net_rules?
Matthias
--
Matthias Schwarzott (zzam)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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-18 21:00 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
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 [this message]
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=200704182300.11920.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).