From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: using udev for network devices?
Date: Fri, 23 Jan 2004 02:59:44 +0000 [thread overview]
Message-ID: <20040123025944.GA16893@kroah.com> (raw)
In-Reply-To: <26879984$10748155624010624ac05fc8.26438349@config3.schlund.de>
On Fri, Jan 23, 2004 at 01:06:01AM +0100, Arnd Bergmann wrote:
> The attached patch adds code to use the SIOCSIFNAME ioctl
> for naming network devices from udev. This is a solution to
> the problem of persisting naming for network devices that
> don't have a MAC address. The problem is very common for
> virtual network devices on s390, but I'm sure others have it
> as well.
>
> Note that this is just proof-of-concept. The code is missing
> some checks and I'm not sure if udev is the right place
> to this (maybe an libsysfs'ified extended nameif or a new
> tool might be better).
Nice patch, but I really think that a libsysfs'ified version of nameif
would be the better place for this.
I also think there are some Nokia people with some patches to nameif
that do much the same thing (but I think they rely on pci ids.)
But if the nameif maintainers, and the network developers think that
udev is an approiate tool to name network devices, I could be
convinced...
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
prev parent reply other threads:[~2004-01-23 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 0:06 using udev for network devices? Arnd Bergmann
2004-01-23 2:59 ` Greg KH [this message]
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=20040123025944.GA16893@kroah.com \
--to=greg@kroah.com \
--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.