Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
Le Sun, 28 Jan 2007 00:51:57 -0500, James Lockie [EMAIL PROTECTED] a écrit : Richard Watson wrote: Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem is that although rc-update show indicates all my interfaces are NOT being loaded other than net.lo at boot (which is what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 in the default run level. Can anybody help? It's very frustrating waiting for these interfaces to try and connect before timing out. I've always run my network connection on this basis as Gentoo is on my laptop and depending where I am will determine which interface I want to use. Thanks, Richard rm /etc/init.d/net.eth0 rm /etc/init.d/net.ath1 That's a solution. Unfortunately, not always the good one. Richard : you should have a look at RC_PLUG_SERVICES in /etc/conf.d/rc Another solution if you are dhcp-ing is (from /etc/conf.d/net.example) : # For passing custom options to dhcpcd use something like the following. This # example reduces the timeout for retrieving an address from 60 seconds (the # default) to 10 seconds. #dhcpcd_eth0=-t 10 But !!! Yes, there is a but... Be carefull. On some networks, it might takes a bit more than 10sec to receive an dhcp answer. -- Cordialement, Patrice BOUVARD, Networks Systems Engineer -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
Richard Watson wrote: Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem is that although rc-update show indicates all my interfaces are NOT being loaded other than net.lo at boot (which is what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 in the default run level. Can anybody help? It's very frustrating waiting for these interfaces to try and connect before timing out. I've always run my network connection on this basis as Gentoo is on my laptop and depending where I am will determine which interface I want to use. Thanks, Richard rm /etc/init.d/net.eth0 rm /etc/init.d/net.ath1 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Wed, 2007-01-10 at 20:39 +, Mick wrote: On Tuesday 09 January 2007 23:12, Iain Buchanan wrote: On Tue, 2007-01-09 at 19:56 +, Mick wrote: On Tuesday 09 January 2007 01:13, Iain Buchanan wrote: hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the bluetooth service is still started automatically (not in any runlevel). thoughts? thanks, Does it still start if you rc-update del it? If yes, then I'm thinking that it may be that the device is modprobed by udev and then ifplug, or what-have-you, picks it up? yes, it starts even though I've 'rc-update del'ed it! hmm, if it's modprobed by udev, then who's starting the service? I can't really compare with mine because bluetooth won't come up no matter what. :-( that's what this list is for :-) I think mine is a hardware problem. I can't see it in lshw lspci. I have posted about it in the past and some good souls tried to help but I didn't get far. Still using the IrDA to spk to my mobile. :-( what about lsusb? -- Iain Buchanan iaindb at netspace dot net dot au Dear Lord: I just want *one* one-armed manager so I never have to hear On the other hand, again. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Tuesday 09 January 2007 23:12, Iain Buchanan wrote: On Tue, 2007-01-09 at 19:56 +, Mick wrote: On Tuesday 09 January 2007 01:13, Iain Buchanan wrote: hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the bluetooth service is still started automatically (not in any runlevel). thoughts? thanks, Could it be that bluetooth is the wrong name for it? Is it identified as bluetooth in ifconfig? bluetooth is the name of the init.d service at least, but it's not a network interface, so ifconfig won't show anything there... Of course. My mistake. Does it still start if you rc-update del it? If yes, then I'm thinking that it may be that the device is modprobed by udev and then ifplug, or what-have-you, picks it up? I can't really compare with mine because bluetooth won't come up no matter what. :-( that's what this list is for :-) I think mine is a hardware problem. I can't see it in lshw lspci. I have posted about it in the past and some good souls tried to help but I didn't get far. Still using the IrDA to spk to my mobile. :-( -- Regards, Mick pgp7sw3wfmQHo.pgp Description: PGP signature
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Tuesday 09 January 2007 01:13, Iain Buchanan wrote: hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the bluetooth service is still started automatically (not in any runlevel). thoughts? thanks, Could it be that bluetooth is the wrong name for it? Is it identified as bluetooth in ifconfig? I can't really compare with mine because bluetooth won't come up no matter what. :-( -- Regards, Mick pgp6cgedbA56S.pgp Description: PGP signature
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Tue, 2007-01-09 at 19:56 +, Mick wrote: On Tuesday 09 January 2007 01:13, Iain Buchanan wrote: hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the bluetooth service is still started automatically (not in any runlevel). thoughts? thanks, Could it be that bluetooth is the wrong name for it? Is it identified as bluetooth in ifconfig? bluetooth is the name of the init.d service at least, but it's not a network interface, so ifconfig won't show anything there... I can't really compare with mine because bluetooth won't come up no matter what. :-( that's what this list is for :-) -- Iain Buchanan iaindb at netspace dot net dot au It is often easier to ask for forgiveness than to ask for permission. -- Grace Murray Hopper -- gentoo-user@gentoo.org mailing list
[gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem is that although rc-update show indicates all my interfaces are NOT being loaded other than net.lo at boot (which is what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 in the default run level. Can anybody help? It's very frustrating waiting for these interfaces to try and connect before timing out. I've always run my network connection on this basis as Gentoo is on my laptop and depending where I am will determine which interface I want to use. Thanks, Richard
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Tue, 9 Jan 2007 10:42:37 +1000, Richard Watson wrote:
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I
found that net.eth0 was grabbing my firewire port (ieee1394) and I
needed to create net.eth2 for my NIC as net.eth1 was being assigned to
my wireless. My problem is that although rc-update show indicates all
my interfaces are NOT being loaded other than net.lo at boot (which is
what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2
in the default run level. Can anybody help? It's very frustrating
waiting for these interfaces to try and connect before timing out.
Add RC_PLUG_SERVICES=!net.* to /etc/conf.d/rc to stop the interfaces
coming up at boot. Use udev rules to have the naming as you want. For
example, I use
KERNEL==eth*, SYSFS{address}==00:1a:23:3c:76:26, NAME:=eth0
KERNEL==eth*, SYSFS{address}==00:2d:94:ef:f2:c0, NAME:=eth1
KERNEL==eth*, SYSFS{address}==00:3c:99:ff:fe:3c:76:26, NAME:=eth2
To make my wired interface eth0, wireless eth1 and firewire eth2. The
address strings are the MAC addresses of the interfaces.
Alternatively, you can get rid of the firewire interface altogether by
unsetting CONFIG_IEEE1394_ETH1394 in your kernel config
--
Neil Bothwick
Will we ever get out of this airport? asked Tom interminably.
signature.asc
Description: PGP signature
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Tue, 2007-01-09 at 10:42 +1000, Richard Watson wrote: Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem is that although rc-update show indicates all my interfaces are NOT being loaded other than net.lo at boot (which is what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 in the default run level. Can anybody help? It's very frustrating waiting for these interfaces to try and connect before timing out. device initiated services! the topic came up recently. I hated it for a while because it was starting bluetooth for me automatically! there are a couple of things to tweak in /etc/conf.d/rc. Set RC_PLUG_SERVICES=!net.* and set RC_NET_STRICT_CHECKING=lo read the comments for more info! HTH, -- Iain Buchanan iaindb at netspace dot net dot au No act of kindness, no matter how small, is ever wasted. -- Aesop -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.
On Tue, 2007-01-09 at 01:04 +, Neil Bothwick wrote: On Tue, 9 Jan 2007 10:42:37 +1000, Richard Watson wrote: Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem is that although rc-update show indicates all my interfaces are NOT being loaded other than net.lo at boot (which is what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 in the default run level. Can anybody help? It's very frustrating waiting for these interfaces to try and connect before timing out. Add RC_PLUG_SERVICES=!net.* to /etc/conf.d/rc to stop the interfaces coming up at boot. Use udev rules to have the naming as you want. For example, I use hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the bluetooth service is still started automatically (not in any runlevel). thoughts? thanks, -- Iain Buchanan iaindb at netspace dot net dot au A classic is something that everyone wants to have read and nobody wants to read. -- Mark Twain, The Disappearance of Literature -- gentoo-user@gentoo.org mailing list
