On Tue, Feb 19, 2013 at 11:59 AM, Lennart Sorensen <lsore...@csclub.uwaterloo.ca> wrote: > On Tue, Feb 19, 2013 at 10:04:41AM -0800, Steve deRosier wrote: > > Is your busybox built with BB_FEATURE_MOUNT_LOOP enabled? >
No, it wasn't, but since I was manually doing the losetup command, that wouldn't matter. However, I've enabled the config and can now do a loopback mount in one-shot which is nice. Thanks for the suggestion. > Is your mountpoint in a location that permits mounts (apparently you can Yes. Update: I've managed to get it working, kind-of. Since I had a problem with cramfs, but ext2 worked, I decided to try squashfs. This worked for me on the first try. I had to install the tools for squashfs on my dev machine manually, but my client is just going to have another tool requirement. squashfs also gives me better compression, so thats a positive. I don't know what's up with cramfs. If I had to suspect, there's something with the PAGE_SIZE thing. Coldfire uses an 8k page size, and I found a note in cramfs's README that it only works on targets with 4k page sizes. But as I saw that you can manually change the block size via a parameter to mkfs.cramfs, I was hoping that was an old limitation. Seems odd to me that they'd limit a filesystem to be so dependent on certain processors. And if that's the case, the kernel shouldn't let me enable cramfs if it can't be used on my platform. But since I've got squashfs working, it's not my problem anymore. Time to finish up and move on to my next stumbling block. Thanks for helping, - Steve _______________________________________________ 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
