X-Original-To: alpine-devel@lists.alpinelinux.org Received: from hydrogenium.shiz.me (hydrogenium.shiz.me [62.210.12.63]) by lists.alpinelinux.org (Postfix) with ESMTP id 927135C446A for ; Mon, 28 Nov 2016 20:17:22 +0000 (GMT) Received: from ion.lan (::ffff:80.112.172.223 [IPv6:::ffff:80.112.172.223]) by hydrogenium.shiz.me (OpenSMTPD) with ESMTPSA id b278da7e TLS protoversion=TLSv1.2 ciphersuite=ECDHE-RSA-AES256-GCM-SHA384 verify=NO; Mon, 28 Nov 2016 20:16:54 +0000 (UTC) Content-Type: text/plain; charset=utf-8 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: [alpine-devel] [PATCH 3/3] init: setup loopback interface From: Shiz In-Reply-To: <20161128173352.7608d9e8@ncopa-macbook.copa.dup.pw> Date: Mon, 28 Nov 2016 21:17:15 +0100 Cc: alpine-devel@lists.alpinelinux.org Content-Transfer-Encoding: quoted-printable Message-Id: <8601B258-776A-4510-B972-DF5A42B5E341@shiz.me> References: <20161117015252.27549-1-hi@shiz.me> <20161117015252.27549-3-hi@shiz.me> <20161128173352.7608d9e8@ncopa-macbook.copa.dup.pw> To: Natanael Copa X-Mailer: Apple Mail (2.3251) > On 28 Nov 2016, at 20:33, Natanael Copa wrote: >=20 > On Thu, 17 Nov 2016 02:52:52 +0100 > Shiz wrote: >=20 >> This fixes various issues in later boot procedures if relying on = localhost >> to work properly and if no further networking configuration is done. >=20 > Hi, >=20 > I'm just curious what those issues are? >=20 > 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) >=20 > 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. >=20 > So I wonder if this is the correct place to fix it. >=20 > -nc Hi, You=E2=80=99re 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=E2=80=99t been = an issue until now, no reason to further dig into it. - Shiz= --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---