Mail archive
alpine-devel

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

From: Natanael Copa <ncopa_at_alpinelinux.org>
Date: Mon, 28 Nov 2016 17:33:52 -0200

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


> ---
> initramfs-init.in | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/initramfs-init.in b/initramfs-init.in
> index 9aa1d3f..b8ce2f1 100755
> --- a/initramfs-init.in
> +++ b/initramfs-init.in
> _at_@ -313,6 +313,9 @@ if [ "$KOPT_dma" = no ]; then
> modprobe libata dma=0
> fi
>
> +# setup loopback interface
> +ip_set lo 127.0.0.1 255.0.0.0
> +
> # The following values are supported:
> # alpine_repo=auto -- default, search for .boot_repository
> # alpine_repo=http://... -- network repository



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