Re: [gentoo-user] net.eth0 net.eth1 net.eth2 persist in trying to come up even though not in any run level.

[Iain Buchanan <iaindb@netspace.net.au>]

On Tue, 2007-01-09 at 01:04 +0000, 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