From: Kyle Moffett <mrmacman_g4@mac.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
"Yinghai Lu" <yhlu.kernel@gmail.com>,
"Shaohua Li" <shaohua.li@intel.com>,
"Sébastien Dugué" <sebastien.dugue@bull.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
ambx1@neo.rr.com, akpm@linux-foundation.org, lenb@kernel.org,
rmk@arm.linux.org.uk, mjg59@srcf.ucam.org,
castet.matthieu@free.fr
Subject: Re: commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices - broke my serial console
Date: Sun, 29 Jul 2007 13:21:33 -0400 [thread overview]
Message-ID: <A2444507-569E-4D35-A694-C8F0CD24ED00@mac.com> (raw)
In-Reply-To: <46AA5E1A.8020303@garzik.org>
On Jul 27, 2007, at 17:05:30, Jeff Garzik 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).
I was doing that for a while, but now Debian and RedHat and most
other modern distros have a udev rules file called something like: /
etc/udev/rules.d/z30-persistent-net-generator.rules Under Debian it
generates a file /etc/udev/rules.d/z25-persistent-net.rules which
automatically renames net devices based on their mac address. The
persistent-net-generator takes the current name and MAC and stuffs
them in an appropriate file. So really once you've booted with the
network card in, all you have to do is modify the persistent-
net.rules file to change the name of your NIC and rerun udevtrigger.
I've gotten into the habit of using descriptive names lately (7 chars
is the most that ifconfig will show without truncating, and it seems
to be unable to properly sort/display/operate-on longer ones).
For example, my Debian firewall box has:
world: Connection to the cable modem
switch: Connection to my VLAN-capable switch
main0: "Primary" VLAN on my switch.
main1: A local gigabit switch for connections to a couple other
systems
main: A bridge of main0 and main1 which is used as the primary LAN
interface
hbeat: Dedicated NIC for Linux-HA (HeartBeat)
debian: A Debian netinst net-boot VLAN with support for PXE and
OpenFirmware
radius: A VLAN used by my wireless AP for radius traffic
wifi: A VLAN used for private wireless traffic
Most of those interfaces are virtual and created by custom "/etc/
network/if-pre-up.d/*" scripts, but you can see the "world",
"switch", "main1", and "hbeat" interfaces are actual physical
interfaces. Such naming (with appropriate comments in /etc/network/
interfaces) vastly eases the management of a box with a shitton of
interfaces. The fact that ifconfig has some outstanding bugs with
big interface names is mostly irrelevant since I use the iproute2
tool ("ip") to do almost all administration.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2007-07-29 17:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 14:28 Sébastien Dugué
2007-07-24 15:48 ` Bjorn Helgaas
2007-07-24 17:49 ` Jeff Garzik
2007-07-24 18:09 ` Andrew Morton
2007-07-24 19:07 ` Jeff Garzik
2007-07-24 18:17 ` Maciej W. Rozycki
2007-07-24 19:53 ` Bjorn Helgaas
2007-07-24 20:13 ` Jeff Garzik
2007-07-24 20:33 ` Yinghai Lu
2007-07-25 2:34 ` Bjorn Helgaas
2007-07-25 4:27 ` Yinghai Lu
2007-07-25 12:55 ` Bjorn Helgaas
2007-07-25 15:57 ` Yinghai Lu
2007-07-25 16:11 ` Bjorn Helgaas
2007-07-25 16:45 ` Yinghai Lu
2007-07-24 20:34 ` Bjorn Helgaas
2007-07-24 20:40 ` Jeff Garzik
2007-07-24 20:56 ` Bjorn Helgaas
2007-07-24 21:05 ` Jeff Garzik
2007-07-24 22:07 ` Alan Cox
[not found] ` <p73ir88sax1.fsf@bingen.suse.de>
2007-07-25 15:48 ` Alan Cox
2007-07-25 16:06 ` Bjorn Helgaas
2007-07-25 16:47 ` Jeff Garzik
2007-07-25 17:34 ` Alan Cox
2007-07-25 17:38 ` Alan Cox
2007-07-24 22:06 ` Alan Cox
2007-07-25 7:45 ` Sébastien Dugué
2007-07-25 13:16 ` Bjorn Helgaas
2007-07-25 13:32 ` Sébastien Dugué
2007-07-25 13:38 ` Sébastien Dugué
2007-07-25 22:41 ` Bjorn Helgaas
2007-07-26 0:37 ` Yinghai Lu
2007-07-26 1:35 ` Yinghai Lu
2007-07-26 2:21 ` Shaohua Li
2007-07-26 3:33 ` Bjorn Helgaas
2007-07-27 18:16 ` Bjorn Helgaas
2007-07-27 18:38 ` Yinghai Lu
2007-07-27 18:56 ` Bjorn Helgaas
2007-07-27 20:35 ` Yinghai Lu
2007-07-27 20:58 ` Bjorn Helgaas
2007-07-27 21:05 ` Jeff Garzik
2007-07-27 21:53 ` Kay Sievers
2007-07-29 17:21 ` Kyle Moffett [this message]
2007-07-29 18:03 ` Russell King
2007-07-26 8:08 ` Sébastien Dugué
2007-07-25 15:51 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2007-07-22 21:04 Linus 2.6.23-rc1 Linus Torvalds
2007-07-23 18:38 ` 2.6.23-rc1: BUG_ON in kmap_atomic_prot() Alexey Dobriyan
2007-07-23 19:01 ` Alexey Dobriyan
2007-07-23 20:24 ` Andrew Morton
2007-07-23 20:40 ` Alexey Dobriyan
2007-07-23 21:01 ` Alexey Dobriyan
2007-07-23 21:11 ` Andrew Morton
2007-07-23 21:28 ` Linus Torvalds
2007-07-24 17:59 ` Adrian Bunk
2007-07-24 18:14 ` Linus Torvalds
2007-07-26 6:09 ` commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices - broke my serial console H. Peter Anvin
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=A2444507-569E-4D35-A694-C8F0CD24ED00@mac.com \
--to=mrmacman_g4@mac.com \
--cc=akpm@linux-foundation.org \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=jeff@garzik.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rmk@arm.linux.org.uk \
--cc=sebastien.dugue@bull.net \
--cc=shaohua.li@intel.com \
--cc=yhlu.kernel@gmail.com \
/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®