netdev - RE: [PATCH] udev: create empty regular files to represent net interfaces

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <EDA0A4495861324DA2618B4C45DCB3EE589654@blrx3m08.blr.amer.dell.com>
Date:	Thu, 29 Oct 2009 00:45:06 +0530
From:	<Narendra_K@...l.com>
To:	<kay.sievers@...y.org>, <Matt_Domsch@...l.com>
Cc:	<dannf@...com>, <linux-hotplug@...r.kernel.org>,
	<netdev@...r.kernel.org>, <Jordan_Hargrave@...l.com>,
	<Charles_Rose@...l.com>, <bhutchings@...arflare.com>
Subject: RE: [PATCH] udev: create empty regular files to represent net interfaces


>That all sounds very much like something which will hit us 
>back some day. I'm not sure, if udev should publish such dead 
>text files in /dev, it does not seem to fit the usual 
>APIs/assumptions where /sys and /dev match, and libudev 
>provides access to both. It all sounds more like a database 
>for a possible netdevname library, which does not need to be 
>public in /dev, right?

The char device nodes under /dev/netdev/ do seem to adhere to the
assumption of what is there under /sys and /dev match.

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