[Buildroot] Strange behaviour with cramfs

[Buildroot] Strange behaviour with cramfs

[Michael Burghart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

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

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

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

which is ok.
But then:

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

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

- -- 
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNorVNAAoJEEMkp/gkis19PykIAJHR4AWuJG2qmn8F9pp0kZMV
nkjQtO2LUo/txuCKgFk6q0gxkOOqqajko5Br8Wu0zw6IEDNgvhn/s1CP+w1Ra6oN
1uZITMhZdxkk1yV6jeh34jG3nbhBnHpM370KxFAn7MYb9kh4TlP6/hLzvycSr4Hs
wBntxX+/JoMlVvwQADgyytUmdD4PxVgfWMQFS/KpYSCTpyeEa90T74AnYK0krCG5
/l0QHOu4/Ru/Iug2rNv+2XdGcw24ZsHpm9yhT6UGFiW9SO3AqAzDuxTF/Q0ahnwL
bvufzguE+lJfGfKRnbvIj5GIv858V7Hhav2ZSHaD72P/lnCJngjc6cKXUwkOPfs=
=1b1Q
-----END PGP SIGNATURE-----

[Buildroot] Strange behaviour with cramfs

[Michael Burghart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

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

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

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

which is ok.
But then:

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

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


- -- 
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNorcaAAoJEEMkp/gkis19PHwIAJ3eVahawrAji4laXgcdOdWI
jdgd0fNfnbQeiQcVqwbDWZFeYvT0w2NmwfWpYJWUUwSkYjAP9q/B4/q53ONW47XB
bGLzMbcnEfmou6BizSct/P7WsJVNTajCe+P+gebyNj6/az5lZgDrIiGOaiuR5iZi
6frScszt8lyoVXLkWvec5XDBabGwtPTcHc8qzZZJxNzGIIrDmfNt1JaJJbQCnO3c
cZYi8rq58KNSk3zq/1dYjfn8p+fMlP6eGt0jrlNNNR3cByHUCRGp6XqC/HmpPxIW
/NRLIzL7T7mT1xx2BXO9NrcVcq6ZDOaviO81Ci57FFxVfGaUoD35gYQUUL5JkQ4=
=Xs2k
-----END PGP SIGNATURE-----

[Buildroot] Strange behaviour with cramfs

[Peter Korsgaard]

>>>>> "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