Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration

[darren kirby <bulliver@badcomputer.org>]

[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]

quoth the Teresa and Dale:
> darren kirby wrote:
> >Hello all,
> >
> >Does anyone know why my eth0 (wired) and eth1 (wireless) interfaces are
> >getting started and autoconfigured at boot despite not being present at
> > any runlevel in rc-update?
> >
> >They are getting configured with the settings in conf.d/net, whether or
> > not eth0 has a cable plugged in, and whether or not the firmware is
> > loaded for eth1 (it is a PCMCIA device). Obviously, these settings are
> > bunk...
> >
> >I am not sure what info I should put here to diagnose this:
> >gentoo-sources-2.6.14-r5
> >baselayout-1.12.0_pre16-r3
> >
> >Again, net.eth0 and net.eth1 are not shown at _any_ runlevel when I run
> >'rc-update -s'.
> >
> >thanks,
> >-d
>
> Is it possible that you are running something that needs net and that is
> starting it?  I know some things, like ivman and such, will start other
> services if they must be running for them to work.

I don't think so...

The only network related script in the default runlevel is 'net.lo'. syslog-ng 
doesn't need network does it? 

Could this be from hotplug or udev? I really don't see why they would start?!

> Just a thought.  Is strange though.
>
> Dale
>
> :D :D :D

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]