Buildroot Archive on 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:31:16 +0200	[thread overview]
Message-ID: <51001054.1000901@petroprogram.com> (raw)
In-Reply-To: <20130123171848.370ef451@skate>

23.1.2013 18:18, Thomas Petazzoni kirjoitti:
> Dear Stefan Fr?berg,
>
> On Wed, 23 Jan 2013 18:05:54 +0200, Stefan Fr?berg wrote:
>
>> 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.
> Ok. But then if Buildroot has a bug, let's fix the bug instead of
> trying to work-around it, no?

Sure. But like I said I haven't (yet) done that whole root squashfs so I
can only guess work
what could be wrong with it. (too old squashfs-utils, wrong kernle
version, maybe missing kernel option?)

>> 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
> Indeed. You could still boot the root filesystem from squashfs, and
> then mount a tmpfs and do the unionfs thing. There's no real need to
> split usr/ in a squashfs in order to achieve this, I think.
>
> Best regards,
>
> Thomas

Can I write to /usr with buildroot squashfs ?

Stefan

  reply	other threads:[~2013-01-23 16:31 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
2013-01-23 16:18             ` Thomas Petazzoni
2013-01-23 16:31               ` Stefan Fröberg [this message]
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=51001054.1000901@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox