From: David Miller <davem@davemloft.net>
To: dh.herrmann@gmail.com
Cc: netdev@vger.kernel.org, teg@jklm.no, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] Provide netdev naming-policy via sysfs
Date: Fri, 28 Mar 2014 17:02:22 -0400 (EDT) [thread overview]
Message-ID: <20140328.170222.346040641241669437.davem@davemloft.net> (raw)
In-Reply-To: <CANq1E4TxaNnZoqfw5DiifAhk28hVq5HJJMd07ZDFAjdc68nKKg@mail.gmail.com>
From: David Herrmann <dh.herrmann@gmail.com>
Date: Fri, 28 Mar 2014 20:34:47 +0100
> However, as mentioned in the discussions on v1, there're more
> use-cases than that. Imagine a 3rd party initrd renames a
> network-device early, if udev runs in the main system, we would rename
> the device again. If we could detect the rename via NET_NAME_RENAMED,
> we wouldn't break such setups. The only reason to rename devices in
> udev is to get reliable names. If someone else already renamed a
> device, we always expect them to provide better names than we do, so
> udev should only touch devices that have kernel-enumerated names.
> Of course, this can be fixed by requiring all the initrd developers to
> somehow tag devices as already renamed. But this would replicate
> information that the kernel already has.
You want to use the kernel to facilitate communication between two
userland components.
Imagine if we had to do that for everything.
Really, it's not a good reason, sorry.
next prev parent reply other threads:[~2014-03-28 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 13:05 [PATCH v5 0/4] Provide netdev naming-policy via sysfs David Herrmann
2014-03-26 13:05 ` [PATCH v5 1/4] net: add name_assign_type netdev attribute David Herrmann
2014-03-26 13:05 ` [PATCH v5 2/4] mac80211: set NET_NAME_USER for user-space created ifs David Herrmann
2014-03-26 13:05 ` [PATCH v5 3/4] ath6kl: set NET_NAME_USER for P2P ifs David Herrmann
2014-03-26 13:05 ` [PATCH v5 4/4] brcmfmac: " David Herrmann
2014-03-28 18:54 ` [PATCH v5 0/4] Provide netdev naming-policy via sysfs David Miller
2014-03-28 19:34 ` David Herrmann
2014-03-28 21:02 ` David Miller [this message]
2014-03-28 20:51 ` Tom Gundersen
2014-03-28 21:21 ` David Miller
2014-03-28 22:39 ` Tom Gundersen
2014-03-29 1:42 ` David Miller
2014-03-29 9:46 ` Tom Gundersen
2014-03-29 19:37 ` David Miller
[not found] ` <20140329.153737.671362434625537776.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2014-03-29 19:48 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140328.170222.346040641241669437.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dh.herrmann@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=teg@jklm.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).