linux-kernel - Re: Network Device Naming mechanism and policy

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: <1237912977l.501l.10l@mofo>
Date:	Tue, 24 Mar 2009 11:42:57 -0500
From:	"Karl O. Pinc" <kop@...e.com>
To:	Matt Domsch <Matt_Domsch@...l.com>
Cc:	netdev@...r.kernel.org, linux-hotplug@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Network Device Naming mechanism and policy

My thoughts on the subject; from someone who is not
particularly qualified to have opinions.

Reading over your post, I searched for a single sentence describing
the problem you're trying to solve.  What I came up with was
this:

On 03/24/2009 10:46:17 AM, Matt Domsch wrote:

>  Users continue to have to figure out, for each system type
> and
> potentially for each boot, which NIC is connected to which name.  This
> has been the #1 customer complaint about Linux on Dell servers for
> several years.  I'd prefer not to keep it this way.

Perhaps a little magic in the udev rule that creates the
z70_persistent-net-rules file would solve the basic problem.
It could sort the nics by mac address when creating the
names.  It need only run when the z70 file does not exist.
I presume this would produce consistent results in most cases
and it feels technically feasible; although I am not
fully qualified to make that judgment.

Rather that put the onus on udev to make the above
change Dell could just run a little program at first
boot that mungs the z70 file as desired.  (It could then
force a reboot; I forget if this would be needed.)
I imagine Dell boots the boxes once at the factory,
but if not then the user has to suffer with a longer
boot process at first boot.  Because this is driven
by Dell, Dell would know exactly what nic has what
name.  And Dell knows what nics are on the mobo and
what are not, and so can control the mac address sort
order as desired.

The other solution that screams out at me is to ditch
those legacy BIOSes and go to something like LinuxBIOS.
Again, I'm not really qualified, but it sure feels like
there's an answer in this approach.

The other point that struck me was that sometimes, it seems,
users want persistence in the naming of their network devices
and sometimes they want device names based on bus position.

The sucky thing is that symlinks and nics don't mix well
and so it seems impossible to satisfy both the above
requirements at the same time.  This is an area that
IMHO could be better addressed by the Linux community.

Karl <kop@...e.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/