Mail archive
alpine-devel

Re: [alpine-devel] [PATCH 3/3] init: setup loopback interface

From: Shiz <hi_at_shiz.me>
Date: Mon, 28 Nov 2016 21:17:15 +0100

> On 28 Nov 2016, at 20:33, Natanael Copa <ncopa_at_alpinelinux.org> wrote:
>
> On Thu, 17 Nov 2016 02:52:52 +0100
> Shiz <hi_at_shiz.me> wrote:
>
>> This fixes various issues in later boot procedures if relying on localhost
>> to work properly and if no further networking configuration is done.
>
> Hi,
>
> I'm just curious what those issues are?
>
> I know that if you for example use /etc/init.d/dhcpcd instead
> of /etc/init.d/networking then you'll have your lo interface
> unconfigured. (which I work around by having lo only in networking and
> enable both services)
>
> I also think that you may have the same issues in LXC for example,
> unless you explicitly configure lo during boot. and LXC does not use
> initramfs at all.
>
> So I wonder if this is the correct place to fix it.
>
> -nc

Hi,

You’re probably correct - I was lead to that approach perhaps more
because the initramfs already does configure the eth0 interface correctly.
Adding /etc/network/interfaces and the networking service is probably
the better approach, yes. Feel free to disregard this patch.

I do wonder to what extent applications rely on lo to work without
explicitly needing networking as such, but if that hasn’t been an issue
until now, no reason to further dig into it.

- Shiz

---
Unsubscribe:  alpine-devel+unsubscribe_at_lists.alpinelinux.org
Help:         alpine-devel+help_at_lists.alpinelinux.org
---
Received on Mon Nov 28 2016 - 21:17:15 GMT