[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ae72650707271453s223bd484xd1d70ef8ad5b3d77@mail.gmail.com>
Date: Fri, 27 Jul 2007 23:53:02 +0200
From: "Kay Sievers" <kay.sievers@...y.org>
To: "Jeff Garzik" <jeff@...zik.org>
Cc: "Bjorn Helgaas" <bjorn.helgaas@...com>,
"Yinghai Lu" <yhlu.kernel@...il.com>,
"Shaohua Li" <shaohua.li@...el.com>,
"Sébastien Dugué" <sebastien.dugue@...l.net>,
linux-kernel <linux-kernel@...r.kernel.org>, ambx1@....rr.com,
akpm@...ux-foundation.org, lenb@...nel.org, rmk@....linux.org.uk,
mjg59@...f.ucam.org, castet.matthieu@...e.fr
Subject: Re: commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices - broke my serial console
On 7/27/07, Jeff Garzik <jeff@...zik.org> wrote:
> Bjorn Helgaas wrote:
> > And couldn't we use udev to associate a fixed name with a MAC
> > address? Then the user could use the same persistent name,
> > regardless of the order in which the driver found the devices.
>
>
> I don't know about udev, but people are definitely using fixed names
> based on MAC address for ethernet devices already: nameif(8) and
> /etc/mactab, iftab(5) and ifrename(8).
That's all obsolete with udev, it creates persistent name entries on
first device discovery, and keeps them forever.
You can edit the automatically created/updated udev rules, if you want
different names, but by default there is no intervention needed to
have stable network device names out of the box, regardless of any
kernel module loading/linking order or whatever.
Kay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists