From: "Tiago Manuel Nunes Marques" <a28427@alunos.det.ua.pt>
To: linux-kernel@vger.kernel.org
Subject: Assignment of network interface names at boot time
Date: Mon, 23 Mar 2009 16:41:16 +0000 [thread overview]
Message-ID: <web-75609548@controller.cgpmail.ua.pt> (raw)
Hi all,
I don't know if this would be more appropriate to submit
as a bug report but I would like to know where I could
start tackling this issue instead of submitting a bug
report.
I administer a small cluster which I have now started to
migrate to diskless root but I seem to be having problems
with the network interfaces, which, on boot, are randomly
assigned eth0 or eth1. This is a behavior that I didn't
experienced in 2.6.24 but 2.6.26 has some patches that I
would like to have.
UDEV rules are not a solution, since I need to boot from
the interface, hopefully having a way to define the same
interface to all the machines, for instance: have lower
MAC interfaces be eth0, boot from them, having the network
administrator change these interfaces for the PXE network,
if necessary. Right now, sometimes the test machine boots,
sometimes it gives eth0 to the other interface and fails
to mount the root filesystem.
Where can I start, as this been tackled yet? I searched
google but found no one with the same issues.
Best regards,
Tiago Marques
reply other threads:[~2009-03-23 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=web-75609548@controller.cgpmail.ua.pt \
--to=a28427@alunos.det.ua.pt \
--cc=linux-kernel@vger.kernel.org \
/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