From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Schwarzott Date: Wed, 18 Apr 2007 21:00:11 +0000 Subject: Re: Excluding some device types from persistent-net (xen, s390) Message-Id: <200704182300.11920.zzam@gentoo.org> List-Id: References: <200704120944.10520.zzam@gentoo.org> In-Reply-To: <200704120944.10520.zzam@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Montag, 16. April 2007, Cornelia Huck wrote: > On Fri, 13 Apr 2007 22:08:19 +0200, > > Matthias Schwarzott 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