DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=wl98Px5Bwhxz8VTq+Ik5CZrp/PyuIDInjhTCv2MpMaJRjcCfSx1WAVR+f0m1f2y7gv
         XM2HpsghNwdi2nmt9pKcug/okiLi8h07AOhG16iJhK8bZAd5JbXf8HzfDCwDajc9igT/
         75j02bHjAkPokmiHHjvOo0yQ/j4qSIfp2ZOow=
Precedence: list
MIME-Version: 1.0
In-Reply-To: <AANLkTikbcgrKEfjCvnFx5yMlDeDQKP34trnm8DIqnGKD@mail.gmail.com>
References: <AANLkTikbcgrKEfjCvnFx5yMlDeDQKP34trnm8DIqnGKD@mail.gmail.com>
Date: Thu, 22 Jul 2010 17:02:27 +0200
Message-ID: <AANLkTilT9hNKi9cK_EvSXAeqePi53qiqhEIdd6_vjuwG@mail.gmail.com>
Subject: [alpine-devel] Re: [RFC] replace network config with dhcpcd
From: Natanael Copa <natanael.copa@gmail.com>
To: Alpine Developers <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jul 22, 2010 at 4:45 PM, Natanael Copa <natanael.copa@gmail.com> wrote:
> Hi,
>
> Here is a crazy idea: let dhcpcd handle all network config.

I forgot to say, the biggest benefit would probably be that networking
would probably be alot more reliable.

Some options we have to configure loopback interface if we go for full
dhcpcd - since dhcpcd does not handle looopback interfaces at all:
* keep 'iface lo inet loopback' in  /etc/network/interfaces and start
'networking' service in addition to 'dhcpcd' service. (I dot this on
my lappy now - i'm not too happy with it)
* create a separate /etc/init.d/loopback service that only brings up
the lo interface.
* add a config option to /etc/conf.d/dhcpcd: enable_loopback=yes and
have the dhcpcd init.d script to configure it together with starting
dhcpcd.

I think I prefer the third option, but i woudl be ok with the separate
loopback service too (and have dhcpcd depend on it).

-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---