netdev - Re: [PATCH] udev: create empty regular files to represent netinterfaces

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20091029175045.GD3612@ldl.fc.hp.com>
Date:	Thu, 29 Oct 2009 11:50:46 -0600
From:	dann frazier <dannf@...nf.org>
To:	Narendra_K@...l.com
Cc:	greg@...ah.com, Matt_Domsch@...l.com, kay.sievers@...y.org,
	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
 netinterfaces

On Thu, Oct 29, 2009 at 10:52:52PM +0530, Narendra_K@...l.com wrote:
> 
> >Sure, it's never guaranteed by the kernel that this will 
> >happen, especially as we speed up the boot process by doing 
> >things async.
> 
> >So again, just fix your installer, or write a new udev rule 
> >for your hardware platforms, or both.  But I still fail to see 
> >why multiple names for network devices _in the kernel_ is a 
> >solution for your issue.
> >
> 
> The char device nodes solution does not propose having multiple names
> for the network interfaces _in the kernel_.

Nor does the udev-only implementation I posted which doesn't rely on
new character devices.

-- 
dann frazier

--
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