Precedence: list
MIME-Version: 1.0
From: Magicloud Magiclouds <magicloud.magiclouds@gmail.com>
Date: Sat, 30 Mar 2019 02:17:09 +0800
Message-ID: <CABErt4fDszANifHVMxHn6WSKQnoD1ukFU+H1CLYSpk-wqGDn5A@mail.gmail.com>
Subject: [alpine-devel] Some questions about initramfs-init.
To: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I'd like to propose a rewrite of the initrd `init` script. Because I
think it is quite mixed up of booting logic, and missing some
customization possibilities.

But before that, I need to get some questions clear. In following
discussion, "stage 1" means the initrd system (before switch_root),
"stage 2" means the actual system end user uses (after switch_root).

1. Why there is a keymap setup? I cannot see the necessity of it
except for fallback/single shell.
2. Why networking is after nlplug-findfs? Can I bring up network (if
needed) before nlplug-findfs?
3. Since nlplug-findfs already output a repofile, why there is a
find_boot_repositories soon after to overwrite repofile?
4. Since apk works without /etc/apk/arch, why overwrite it with `apk
--print-arch`, instead of just removing it?
5. The script contains two ways of using repofile. One is using it
directly as "--repositories-file", the other is joining its content
with "--repository". What is the difference?

Thanks.

--=20
=E7=AB=B9=E5=AF=86=E5=B2=82=E5=A6=A8=E6=B5=81=E6=B0=B4=E8=BF=87
=E5=B1=B1=E9=AB=98=E5=93=AA=E9=98=BB=E9=87=8E=E4=BA=91=E9=A3=9E


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---