should i expect trying to mount a cramfs fs to give me a segmentation fault?

[Robert P. J. Day]

  again, just following along here:

http://wiki.barebox.org/doku.php?id=user:first_steps

i created a small cramfs filesystem image:

$ ls -l crypto.cramfs
-rw-rw-r-- 1 rpjday rpjday 24576 Dec  1 11:19 crypto.cramfs
$ file crypto.cramfs
crypto.cramfs: Linux Compressed ROM File System data, little endian size 24576 version #2 sorted_dirs CRC 0x969356bc, edition 0, 24
blocks, 13 files
$

started barebox:

$ ./barebox -i crypto.cramfs
add file crypto.cramfs()


barebox 2012.11.0-00305-g159109f #1 Sat Dec 1 07:46:38 EST 2012


Board: sandbox
could not get tap device: Operation not permitted
tap tap0: probe failed: Operation not permitted
malloc space: 0x7f0f1cb3c010 -> 0x7f0f1d33c00f (size  8 MB)
Open /dev/env0 No such file or directory
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...
set parameter: No such device
set parameter: No such device
set parameter: No such device
set parameter: No such device
set parameter: No such device
barebox:/

  then tried to mount it as that page suggests:

barebox:/ mkdir mnt
barebox:/ mount /dev/fd0 cramfs /mnt
Segmentation fault (core dumped)
rpjday at oneiric:~/OE/dist/barebox/git$

  i also tried the variation:

barebox> mount -t cramfs /dev/fd0 /mnt

same result.  help?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================