Date: Mon, 9 Apr 2018 13:53:39 +0000
From: =?iso-8859-1?B?Q+Fn?= <ca6c@bitmessage.ch>
To: alpine-user@lists.alpinelinux.org
Subject: Re: [alpine-user] Lack of a minimal documentation on Alpine's
 overall architecture, run-from-RAM feature, mkinitfs, modloop etc.
Message-ID: <20180409135338.GB14670@alpine.my.domain>
References: <CAEQMig3N95AM=GY1OXFFVt4Le9cc+62H_p=nQ5SDC-icJ3mESg@mail.gmail.com>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <CAEQMig3N95AM=GY1OXFFVt4Le9cc+62H_p=nQ5SDC-icJ3mESg@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)


Hi,

Sorry for the late reply.


Timur Fayzrakhmanov wrote:
=20
> There are other things in question:
> - Alpine overall architecture;

What do you mean by that? The base of Alpine is BusyBox/musl/apk.

> - What is modloop!?

Modloop is a kernel module for loop devices.

> - Booting process description;
> - How kernel, initramfs (its init script) and init (OpenRC) are
> related to each other;

OpenRC is not init on Alpine, it's a service manager. /sbin/init is
a link to /bin/busybox. The openrc package also provides init scripts.
/etc/inittab describes the boot process, which is:

/sbin/init -> /sbin/openrc sysinit -> /sbin/openrc boot ->
	/sbin/openrc default -> ttys are spawned

initramfs is caught by the kernel and the bootloader, only after it is
started /sbin/init is being executed. Read more about the Linux booting
process and initramfs on Wikipedia or elsewhere, I myself never use it.

> (you can doubt it but Alpine tends to adopt things in its own way and
> I think it should be covered somehow)

It doesn't really.=20

--
ca=F3c



---
Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
Help:         alpine-user+help@lists.alpinelinux.org
---