Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Strange behaviour with cramfs
Date: Wed, 27 Apr 2011 23:13:56 +0200	[thread overview]
Message-ID: <87zknbwg6j.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4DA2B71A.3090407@michaelburghart.de> (Michael Burghart's message of "Mon, 11 Apr 2011 10:08:58 +0200")

>>>>> "Michael" == Michael Burghart <mb@michaelburghart.de> writes:

 Michael> Hi,

 Michael> as I need to be able to replace the rootfs regularly I decided
 Michael> to build it as a cramfs (if there is a better option, please
 Michael> let me know).

I would strongly suggest you had a look at squashfs instead. It is
conceptually the same as cramfs, but with better compression and without
some of the limitations of cramfs.

It's more than 5 years ago since I last used cramfs, but it should work
as well though.

 Michael> Unfortunately it does not work. The cramfs gets loaded and the kernel
 Michael> tells me:

 Michael> [    2.883952] VFS: Mounted root (cramfs filesystem) readonly on device
 Michael> 1:0.

 Michael> which is ok.
 Michael> But then:

 Michael> can't open /dev/proc: No such file or directory

/dev/proc? that sounds odd.

 Michael> and so on on end.. what did I forget to include?! Anybody experienced
 Michael> this before?

Could you post your buildroot .config (or even better defconfig which
you get by running make savedefconfig). Do you have the possibility for
boot over nfs? If so, you could try the same build (use the tarball
output format) though nfs.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-04-27 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  8:08 [Buildroot] Strange behaviour with cramfs Michael Burghart
2011-04-27 21:13 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-11  8:01 Michael Burghart

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=87zknbwg6j.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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