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
| ||
|
Message-ID: <20091106223524.GA27121@bongo.bofh.it>
Date: Fri, 6 Nov 2009 23:35:24 +0100
From: md@...ux.IT (Marco d'Itri)
To: Matt Domsch <Matt_Domsch@...l.com>
Cc: Narendra_K@...l.com, bryan@...zban.is-a-geek.net, dannf@...com,
bhutchings@...arflare.com, netdev@...r.kernel.org,
linux-hotplug@...r.kernel.org, Jordan_Hargrave@...l.com,
Charles_Rose@...l.com, Sandeep_K_Shandilya@...l.com
Subject: Re: PATCH: Network Device Naming mechanism and policy
On Nov 06, Matt Domsch <Matt_Domsch@...l.com> wrote:
> > As a distribution developer I highly value solutions like this which do
> > not require patching every application which deals with interface names
> > and then teaching users about aliases which only work in some places and
> > are unknown to the kernel.
> Fair enough - but would you object if we changed the naming scheme
> from eth%d to something else?
I suppose that this would depend on what else. :-)
Since you want radical changes I recommend that you design the new
persistent naming infrastructure in a way that will allow root to choose
to use the classic naming scheme, or many users will scream a lot and at
least some distributions will do it anyway.
I also expect that providing choice at the beginning of development may
lead to more acceptance later if and when the new scheme will have
proved itself to be superior (at least in some situations).
You have tought about this for a long time and if so far you have not
found a solution which is widely considered superior then I doubt that
one will appear soon. Providing your favourite naming scheme as an
optional add on will immediately benefit those who like it and greatly
reduce opposition from those who do not.
--
ciao,
Marco
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists