From: Joshua Haase <hahj87@gmail.com>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
Cc: =?utf-8?Q?C=C3=A1g?= <ca6c@bitmessage.ch>,
 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.
In-Reply-To: <20180410115640.QHDo8%steffen@sdaoden.eu>
References: <CAEQMig3N95AM=GY1OXFFVt4Le9cc+62H_p=nQ5SDC-icJ3mESg@mail.gmail.com> <20180409135338.GB14670@alpine.my.domain> <87r2nng2z1.fsf@riseup.net> <20180410115640.QHDo8%steffen@sdaoden.eu>
Date: Tue, 10 Apr 2018 12:58:13 -0500
Message-ID: <878t9v9c5m.fsf@riseup.net>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain

Steffen Nurpmeso (2018-04-10 13:56):

| Joshua Haase <hahj87@gmail.com> wrote:
|
|  |From a newbie perspective, you can think of it as a way to mount files
|  |as if they were disks.
|
| There was or is TinyCoreLinux, where packages are not unpacked and
| installed, but kept as balls and the simply mounted in via modloop.

I think that is done using unionfs over loop devices (at least i think
that's how slax did it). But the analogy still applies.

Hope this clarifies some things for Timur.


---
Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
Help:         alpine-user+help@lists.alpinelinux.org
---