From: scott@scottnz.com
To: "David Miller" <davem@davemloft.net>
Cc: scott@scottnz.com, netdev@vger.kernel.org,
scott.parlane@alliedtelesis.co.nz
Subject: Re: [PATCH rfc net] Allow the autoconfigured network interface to be renamed.
Date: Mon, 11 Jun 2012 22:44:34 +1200 [thread overview]
Message-ID: <db9468c7722be0c4131ad015bdae2e31.squirrel@scottnz.com> (raw)
In-Reply-To: <20120611.031053.1433253186495303724.davem@davemloft.net>
> From: scott@scottnz.com
> Date: Mon, 11 Jun 2012 21:58:45 +1200
>
>> They use nfsroot which prevents udev rules from working correctly
>> (because you cant take down the interface to rename it)
>
> This is why I hate nfsroot as implemented in the kernel.
>
The same is true for root over nfs as configured by the initramfs,
conviently there is a small window where you can interfere with it
(at the initramfs stage), or I should say there-was,
its not available anymore, specifically because glibc dropped the sunrpc
code. (This is probably an artifact of gentoo's initramfs more than anything,
but it was the last distro that I could find to network boot without fully
RYO)
> Do this right and use an initial ramdisk, then you won't have
> this huge disconnect between different device names due to
> lack of udev.
>
> Thanks, you've confirmed that this patch is totally inappropriate.
So be it, we will continue to run it, because its the simpliest way to
get what we want done (and most of our software developers can deal
with kernel code, more so than libc)
Regards,
Scott
prev parent reply other threads:[~2012-06-11 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 7:48 [PATCH rfc net] Allow the autoconfigured network interface to be renamed Scott Parlane
2012-06-10 15:53 ` Scott Parlane
2012-06-10 17:20 ` Jan Ceuleers
2012-06-11 3:08 ` David Miller
2012-06-11 3:25 ` David Miller
2012-06-11 9:58 ` scott
2012-06-11 10:10 ` David Miller
2012-06-11 10:44 ` scott [this message]
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=db9468c7722be0c4131ad015bdae2e31.squirrel@scottnz.com \
--to=scott@scottnz.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=scott.parlane@alliedtelesis.co.nz \
/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).