From: "davide rossetti" <davide.rossetti@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: origin of __tmp1930643048 network device name: kernel-space or user-space
Date: Fri, 7 Sep 2007 18:44:28 +0200 [thread overview]
Message-ID: <6e7a378f0709070944l23ac5ca5te6e204e215457c59@mail.gmail.com> (raw)
In-Reply-To: <6e7a378f0709060802r677b4a8emb9c8cb7530f8028b@mail.gmail.com>
> > I'm assuming you're running some sort of Fedora/RHEL/
> > derivative; this is what you get when you have a device that starts
> > out named ethX, but which needed to be renamed so that an already
> > configured ethX could be changed to that name.
>
> yes, it's FC6.
>
> > For the new device, either add a HWADDR in a ifcfg-ethX file for
> > that interface, add something to /etc/mactab, or add a udev rule.
>
> seems like HWADDR is incompatible with bonding.... there is some
> message using HWADDR as well as MASTER=bond0 and SLAVE=yes.
for the records I worked-around it:
- problem seems to be the interface 'bond0', which is started first,
stops the ability to create another device named 'eth0' (WHY?)
- so I shifted all of the interface names: 0->1, 1->2,...
now it is ok. still I do not understand why bond0 seems to interfere
with eth0...
davide
--
davide.rossetti@gmail.com ICQ:290677265 SKYPE:d.rossetti
next prev parent reply other threads:[~2007-09-07 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 17:14 davide rossetti
2007-09-04 20:50 ` Kay Sievers
2007-09-06 12:49 ` Jan Engelhardt
2007-09-06 13:35 ` Bill Nottingham
2007-09-06 15:02 ` davide rossetti
2007-09-07 16:44 ` davide rossetti [this message]
2007-09-08 7:21 ` Jan Engelhardt
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=6e7a378f0709070944l23ac5ca5te6e204e215457c59@mail.gmail.com \
--to=davide.rossetti@gmail.com \
--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
all inboxes | Powered by JetHome®