From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] All my Pcmcia cards are 'eth0'
Date: Fri, 21 Nov 2003 03:40:58 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106938638329078@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106938471327975@msgid-missing>
On Thu, 20 Nov 2003 22:28:19 -0500 Bill Nottingham <notting@redhat.com> wrote:
| Jean Tourrilhes (jt@bougret.hpl.hp.com) said:
| > One of the main problem is that they are all assigned 'eth0',
| > and therefore all configured with the same IP address. This is really
| > pathetic.
| >
| > The usual answer is : you should use 'nameif' :
| > http://www.xenotime.net/linux/doc/network-interface-names.txt
| > Well, of course, nobody ever bothered to try it, so it doesn't
| > work. No comments.
|
| Well, no offense, but I'd think comments are necessary about no
| one bothering to try it and it not working. I've had an orinoco_cs
| device 'bob' using nameif for a while.
Jean, have you given me any feedback on that small howto and it
not working? If so, I've missed it and I apologize for that.
I use that method both at home and at work all the time,
with no problems, but I haven't tried it with PCMCIA cards, so
that's something that might need some work, as you have discovered.
home:
[rddunlap@midway rddunlap]$ ifconfig
ethmain Link encap:Ethernet HWaddr 00:07:E9:09:09:A8
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:134362 errors:0 dropped:0 overruns:0 frame:0
TX packets:166363 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:72537067 (69.1 Mb) TX bytes:22872312 (21.8 Mb)
Interrupt:11 Base address:0xde80 Memory:ff9a0000-0
work:
[rddunlap@gargoyle rddunlap]$ /sbin/ifconfig
ethmain Link encap:Ethernet HWaddr 00:02:55:1A:35:D4
inet addr:172.20.1.49 Bcast:172.20.255.255 Mask:255.255.0.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17339 errors:0 dropped:0 overruns:0 frame:0
TX packets:777 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1668859 (1.5 Mb) TX bytes:103545 (101.1 Kb)
Interrupt:16 Base address:0x7000
| There are some situations where you have to jump through hoops
| because it can't atomically swap two device names (i.e.,
| eth0 <-> eth1, but the code itself seems to work ok in use here...
--
~Randy
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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
next prev parent reply other threads:[~2003-11-21 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 3:13 [PATCH] All my Pcmcia cards are 'eth0' Jean Tourrilhes
2003-11-21 3:28 ` Bill Nottingham
2003-11-21 3:40 ` Randy.Dunlap [this message]
2003-11-21 17:22 ` Jean Tourrilhes
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=marc-linux-hotplug-106938638329078@msgid-missing \
--to=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).