From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: why a manual dhcpcd eth0 is needed?
Date: Sat, 22 Oct 2011 20:18:37 +0200 [thread overview]
Message-ID: <20111022201837.6dd31fc1@rohan.example.com> (raw)
In-Reply-To: <4EA2CFA1.9000609@gmail.com>
On Sat, 22 Oct 2011 10:13:53 -0400
Valmor de Almeida <val.gentoo@gmail.com> wrote:
> On 10/22/2011 02:18 AM, Nikos Chantziaras wrote:
> > On 10/22/2011 08:08 AM, Valmor de Almeida wrote:
> >>
> >> Hello,
> >>
> >> On a recent gentoo install using wicd for network configuration, no
> >> connection is established during boot. After logging in, I need to
> >> issue
> >>
> >> dhcpcd eth0
> >>
> >> to obtain an IP address and access the internet via ethernet. I
> >> thought wicd would take care of that. I did not emerge dhcpcd, it
> >> was emerged as a dependency of wicd.
> >>
> >> What am I missing? I have wicd starting during the boot runlevel.
> >
> > You probably don't have a correct /etc/conf.d/net file. Try:
> >
> > modules="dhcpcd"
> > config_eth0="dhcp"
> >
> >
> I have other gentoo laptops/machines and I typically leave this file
> empty. They all work with wicd in wired and wireless mode.
Correct.
wicd does not use /etc/conf.d/net at all, it has it's own mechanisms.
/etc/conf.d/net is used by the Gentoo network scripts, an entirely
different thing from wicd
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2011-10-22 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 5:08 [gentoo-user] why a manual dhcpcd eth0 is needed? Valmor de Almeida
2011-10-22 6:18 ` [gentoo-user] " Nikos Chantziaras
2011-10-22 14:13 ` Valmor de Almeida
2011-10-22 18:18 ` Alan McKinnon [this message]
2011-10-22 21:51 ` Valmor de Almeida
2011-10-23 19:21 ` Neil Bothwick
2011-10-23 20:01 ` Valmor de Almeida
2011-10-23 21:19 ` Mick
2011-10-23 21:35 ` Valmor de Almeida
2011-10-23 22:45 ` Neil Bothwick
2011-10-24 2:10 ` Valmor de Almeida
2011-10-24 7:50 ` Neil Bothwick
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=20111022201837.6dd31fc1@rohan.example.com \
--to=alan.mckinnon@gmail.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