All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@bork.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: eth0 in dmesg became eth1 from kernel
Date: Fri, 06 Oct 2006 12:47:30 +0000	[thread overview]
Message-ID: <20061006124730.GL10751@bork.org> (raw)
In-Reply-To: <4525F3F0.6000209@magellan-technology.com>


[-- Attachment #1.1: Type: text/plain, Size: 459 bytes --]


On Fri, Oct 06, 2006 at 04:13:04PM +1000, Aras Vaichas wrote:
> Hello,
> 
> I'm working on a Linux live filesystem CD and I've come across a very strange
> problem. My system is based on a Debian system with a custom 2.6.17 kernel.
> 

Debian keeps track of MAC addresses and uses udev to keep the names
persistent.  Take a look at:

/etc/udev/rules.d/z25_persistent-net.rules

mh

-- 
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      reply	other threads:[~2006-10-06 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  6:13 eth0 in dmesg became eth1 from kernel Aras Vaichas
2006-10-06 12:47 ` Martin Hicks [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=20061006124730.GL10751@bork.org \
    --to=mort@bork.org \
    --cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.