Re: [alpine-devel] [PATCH 3/3] init: setup loopback interface
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.
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.
> 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
> +# 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
Received on Mon Nov 28 2016 - 17:33:52 GMT