| 1 |
On Mon, Jul 16, 2012 at 3:30 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
| 2 |
> Thinking in that direction does stimulate yet another idea, tho. What |
| 3 |
> about a squashfs root? AFAIK squashfs is read-only at use time, thus |
| 4 |
> enforcing actually mounting something else to write anything, eliminating |
| 5 |
> many of the down sides of sticking with the initial ramfs root, but it |
| 6 |
> would allow the same flexibility in terms of sticking whatever into it at |
| 7 |
> create-time, while only taking the memory necessary for what's actually |
| 8 |
> stuck in it at create-time. |
| 9 |
|
| 10 |
It is possible, see: |
| 11 |
https://github.com/mkdesu/liberte/blob/master/src/root/initrd/init |
| 12 |
https://github.com/mkdesu/liberte/blob/master/src/etc/fstab |
| 13 |
|
| 14 |
The setup above is somewhat different from what you have in mind |
| 15 |
(SquashFS image is located on disk, and contains the complete live |
| 16 |
filesystem, not just a skeleton), so mounting read-writable branches |
| 17 |
can be deferred to the regular post-initramfs services (such as |
| 18 |
localmount) — on the other hand, maybe you want to do the same (mount |
| 19 |
branches read-only in initramfs, and remount them read-write in an |
| 20 |
init.d service). |
| 21 |
|
| 22 |
-- |
| 23 |
Maxim Kammerer |
| 24 |
Liberté Linux: http://dee.su/liberte |
Archives