Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Christian Pössinger" <poessinger@mixed-mode.de>
To: openembedded-devel@lists.openembedded.org
Subject: Issues with the system startup when the IMAGE_TYPE is squashfs
Date: Thu, 13 Nov 2008 12:19:28 +0100 (CET)	[thread overview]
Message-ID: <49251.80.246.32.33.1226575168.squirrel@intern.netexpress.de> (raw)


Hello,

I'm currently building a rootfs that will be stored in a squashfs
container. The file is properly created by OpenEmbedded, but I noticed
some issues:

First of all, when I boot an OE generated rootfs for the first time, a
file called /etc/volatile.cache will be generated. As of the fact that
squashfs is read-only this file can't be created.

The second issue comes with the kernel modules. Again, the first system
startup will create the modules.dep file inside the /lib/modules/$(uname
-a) directory. But as stated before, this is not possible on a read-only
filesystem.

Is there any way within OpenEmbedded to create those files before the
actual rootfs image is packed?


Best regards,

Christian Pössinger
Software Development

Mixed Mode GmbH
Lochhamer Schlag 17
D-82166 Gräfelfing/München
Tel.        +49 / 89 / 89 86 8-200
Fax        +49 / 89 / 89 86 8-222
Mobil        +49 / 172 /
http://www.mixed-mode.de






             reply	other threads:[~2008-11-13 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 11:19 Christian Pössinger [this message]
2008-11-13 11:46 ` Issues with the system startup when the IMAGE_TYPE is squashfs Thomas Kunze
2008-11-13 16:07   ` Otavio Salvador
2008-11-13 19:20     ` Thomas Kunze
2008-11-13 20:22       ` Otavio Salvador
2008-11-17  8:48         ` Christian Pössinger
2008-11-17 16:31 ` Marcin Juszkiewicz
2008-11-17 16:44   ` Tom Rini
2008-11-17 17:10   ` Koen Kooi

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=49251.80.246.32.33.1226575168.squirrel@intern.netexpress.de \
    --to=poessinger@mixed-mode.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /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