Guys:
I'm using Busybox as constructed by buildroot-2011.05. According to my dotconfig, that makes it busybox-1.18.x. I'm running on an ARM926EJ-S platform (Cogent CSB737). Generally speaking, everything about the buildroot output looks fine (I'm using the root directory it created as an initramfs). The only problem I'm seeing right now is that Busybox's mount utility doesn't want to mount a ubifs partition: # ubinfo UBI version: 1 Count of UBI devices: 1 UBI control device major/minor: 10:63 Present UBI devices: ubi0 # ubinfo -d 0 ubi0 Volumes count: 1 Logical eraseblock size: 253952 bytes, 248.0 KiB Total amount of logical eraseblocks: 4084 (1037139968 bytes, 989.1 MiB) Amount of available logical eraseblocks: 0 (0 bytes) Maximum count of volumes 128 Count of bad physical eraseblocks: 12 Count of reserved physical eraseblocks: 40 Current maximum erase counter value: 1 Minimum input/output unit size: 4096 bytes Character device major/minor: 252:0 Present volumes: 0 # cat /proc/filesystems | grep ubi nodev ubifs # mount -t ubifs ubi0:nand0 /mnt mount: unknown filesystem type 'ubifs' If I boot the same kernel with parameters that allow the kernel to find the UBIFS partition on its own, the kernel is able to do so. So I don't think this is a kernel problem. Any ideas? I'm thinking that either the error message coming back from mount is wrong, and/or the Busybox version of mount doesn't like the fact that the UBIFS volume was created with Debian's mtd-utils rather than Busybox itself. I'm investigating both of these now, but I'm just wondering if anyone else is seeing similar issues--- or is having any success in mounting UBIFS volumes from within Busybox. Thanks! b.g. -- Bill Gatliff [email protected] _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
