Ken Mays kindly suggested using fuse from SFE and/or ntfs-3G. Fuse didn't work because of what looks like a bug in /sbin/mount:
# mount -F fuse-ext2 /dev/dsk/c2t0d0p7 /mnt mount: FSType fuse-ext2 exceeds 8 characters "fuse-ext2", the name of the fuse module for ext2 is indeed 9 characters long. Why /sbin/mount should have a problem with that is another matter. The mount(1M) manual page, which has a recent date but doesn't look quite like the usual illumos/openindiana man pages, gives no clue, but it mentions the man page mnttab(4). The mnttab(4) man page also provides no insight, but refers to /usr/include/sys/mntio.h. With appropriate packages installed, /usr/include/sys/mntio.h shows character array mtl_fstype sized _ST_FSTYPSZ. _ST_FSTYPSZ is defined in /usr/include/sys/stat.h as 16. /sbin/mount has a compiled-in string "%s: FSType %s exceeds %d characters". So if mount is using something less than _ST_FSTYPSZ-1, what is it using (evidently something that evaluates to 8) and why? This is apparently an old issue; it also shows up on a system running oi_151a9. ntfs-3G might or might not have a more recent fuse driver, but no ext2 support per se, so wouldn't help with this problem. This, incidentally, is on a triple-boot laptop which also has NetBSD 7.0 and openSUSE 13.1 Linux installed (both with native ext2 support) and both mounting 5 ext2 data partitions in peaceful coexistence. _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
