All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Squashfs boot
Date: Wed, 23 Jan 2013 18:05:54 +0200	[thread overview]
Message-ID: <51000A62.9090309@petroprogram.com> (raw)
In-Reply-To: <20130123165719.2d62382c@skate>

23.1.2013 17:57, Thomas Petazzoni kirjoitti:
> Dear Stefan Fr?berg,
>
> On Tue, 22 Jan 2013 19:49:35 +0200, Stefan Fr?berg wrote:
>> It's true that you can use squashfs to compress whole system but even
>> in that case you have to
>> make your own init script that will take care of all the magic of
>> mounting. And because squashfs is read-only filesystem then it get's
>> more trickier because you have to take care
>> of yourself of all those /tmp and /var/log etc.. directories that need
>> to store temporarily stuff.
> Huh? Mounting a squashfs filesystem as the root filesystem is very
> easy. Just use root=/dev/<whereyourrootfsis> and that's it.
>
> Buildroot already mounts a tmpfs in /tmp and has several symlinks
> from /var/<something> to /tmp.
>
> So, with the basic default Buildroot configuration, there is absolutely
> nothing complicated in having the entire root filesystem read-only
> inside SquashFS. On several projects, I've generated a system with
> Buildroot where the entire filesystem is read-only mounted. No problem
> at all.
>
> I think your solution is much more complex than just having the entire
> root filesystem read-only.
>
> Best regards,
>
> Thomas

No.
What I meant was, that if he is going to make it *without* buildroot
(that is, if he can't get buildroot generated squashfs root to boot).
*Then* he has to make his own init stuff to mount those /tmp and /var/log.

And my own solution is overly complex because I want the ability to
write to squashfs, even if just temporarily.
That's why I use initramfs + squashfs + unionfs


Regards
Stefan

  reply	other threads:[~2013-01-23 16:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN_xxrWTp21-a-jD7x11yJa6ghM=C=ON2h_bx_is1iFhEkE0bQ@mail.gmail.com>
2013-01-22  1:25 ` [Buildroot] Squashfs boot Stephen Turner
2013-01-22 12:41   ` Stefan Fröberg
     [not found]     ` <CAN_xxrVD=Tq=ekME-jdHKRzyUwXk0PMocQX9mrxxcgjZQ8SYqA@mail.gmail.com>
2013-01-22 17:49       ` Stefan Fröberg
     [not found]         ` <CAN_xxrXZWmhECAH1JfgvHk+U_wksdZ0ZyxpcaSea8KsEYy04mw@mail.gmail.com>
2013-01-22 19:39           ` Stefan Fröberg
2013-01-22 20:20         ` Peter Korsgaard
2013-01-23 15:57         ` Thomas Petazzoni
2013-01-23 16:05           ` Stefan Fröberg [this message]
2013-01-23 16:18             ` Thomas Petazzoni
2013-01-23 16:31               ` Stefan Fröberg
2013-01-24 17:42     ` Arnout Vandecappelle
2013-01-24 19:29       ` Stephen Turner
2013-01-24 22:40         ` Stefan Fröberg
     [not found]           ` <CAN_xxrXsvvupyo61cqZhCR4JyLwtCsm1NRAh9JCy_uVHRqGO4A@mail.gmail.com>
2013-01-25 21:55             ` Stefan Fröberg
2013-01-26 22:38               ` Arnout Vandecappelle
2013-01-26 23:04                 ` Stefan Fröberg
2013-01-27  7:13                 ` Stephen Turner
2013-01-24 22:42       ` Stefan Fröberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51000A62.9090309@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.