lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 16 Oct 2009 19:32:50 +0530 From: <Narendra_K@...l.com> To: <dannf@...com> Cc: <netdev@...r.kernel.org>, <linux-hotplug@...r.kernel.org>, <Matt_Domsch@...l.com>, <Jordan_Hargrave@...l.com>, <Charles_Rose@...l.com> Subject: RE: PATCH: Network Device Naming mechanism and policy >On Tue, Oct 13, 2009 at 11:36:38AM -0600, dann frazier wrote: >> Right - so any reason this couldn't be implemented completely in >> userspace by having udev manipulate plain text files under say >> /etc/udev/net/? >> >> I do agree that it would be nice for admins/installers to tweak/use >> nic names in a similar way to storage names (udev rules), >and it might >> let us take advantage of a lot of the existing udev code. > >Is there interest in this approach? > - modify udev to manage network devices names as regular (non-device) > files (stored in /etc/udev, /dev/netdev, or wherever) Yes. Would you elaborate little more on "modify udev to manage network devices as regular files". Does it mean some custom rules which will generate a regular file under, say, /dev/netdev/ or extend udev itself ? And how would the regular file look like in terms of holding ifindex of the interface, which can be passed to libnetdevname. > - use the existing udev rules to manage symlinks to these files > - point libnetdevname at these text files for its name resolution > >I've started prototyping this, and it certainly looks possible >w/o any kernel changes. However, I could probably use some >advice from a udev person to do a proper implementation. With regards, Narendra K -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists