On Mon, Feb 18, 2013 at 12:08:19PM -0800, Steve deRosier wrote: > OK, this is driving me crazy, I can't figure out how to get a cramfs > file to mount via loopback on my Coldfire target. I'm sure I'm missing > something simple, but I'm not seeing it. Can anyone help? > > * cramfs is enabled in my kernel > * loopback is enabled in my kernel > * using busybox's mount command > * busybox's losetup is enabled > > I'm able to create an ext2 filesystem and mount that in my target via > loopback using (so seems loopback support works OK): > # losetup /dev/loop0 /tmp/mye2fs.img > # mount -t ext2 /dev/loop0 /mnt > > Trying the same with cramfs: > # losetup /dev/loop0 /tmp/mycramfs.img > # mount -t cramfs /dev/loop0 /mnt > mount: mounting /dev/loop0 on /mnt failed: Invalid argument > > Same result if I give `mount -t cramfs -o loop /dev/loop0 /mnt`. I get > "Block device required" if I don't use losetup and try: > # mount -t cramfs -o loop=/dev/loop0 mycramfs.img /mnt
The syntax from what I recall is: mount -t cramfs -o loop /path/imagefile /mountpoint > I've built the cramfs with both big and little endian (just to try). > If I build it with little, I get the following message in dmesg: > cramfs: bad root offset 1048576 > > No messages what so ever if I build big endian. > > If I try building the stand-alone mount, that fails with a missing > header <gnu/types.h>. By a few searches, looks like that mount is no > longer maintained? > > Is there a problem where busyboxes mount doesn't support cramfs? > > Ideas? Not really. I haven't used cramfs for years. I use cpio archives these days with initramfs's tmpfs. Not quite the same thing though in terms of memory usage though. -- Len Sorensen _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
