public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Teresa and Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration
Date: Fri, 14 Apr 2006 18:58:19 -0500	[thread overview]
Message-ID: <4440371B.3040404@vista-express.com> (raw)
In-Reply-To: <200604141536.27666.bulliver@badcomputer.org>

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.

Just a thought.  Is strange though.

Dale

:D :D :D
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-04-15  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 22:35 [gentoo-user] eth0 and eth1 unwanted autoconfiguration darren kirby
2006-04-14 23:58 ` Teresa and Dale [this message]
2006-04-15  2:17   ` darren kirby
2006-04-15  2:37     ` Renat Golubchyk
2006-04-15  3:02     ` Richard Fish
2006-04-15  4:19       ` [gentoo-user] eth0 and eth1 unwanted autoconfiguration *Resolved* I think darren kirby
2006-04-15  4:32         ` Richard Fish

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=4440371B.3040404@vista-express.com \
    --to=teendale@vista-express.com \
    --cc=gentoo-user@lists.gentoo.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