I have enhanced the source to detect 'f2fs'.
Updated source, 'guess_fs-20130215.tar.gz' in my sources repo:
New PET (7K):
Unfortunately, 'guess_fstype' doesn't work at all in an ARM system. Don't know why, yet.
Comments:Posted on 16 Feb 2013, 5:45 by technosaurus
Re: arm guess_fstype
guess_fstype uses some macros to "correct" endianness using bit-shifting like:
~ ... << ... |... >> ... & 0x00ff000 ^ etc...
to get character values from integers and vice versa
most of these macros will have names with be or le and may need to be #ifdef'd according to platform
I suspect that has something to do with it, arm can use the somewhat slower blkid in busybox (if configured) to get the same info (btw, I think busybox-master has f2fs)
Posted on 16 Feb 2013, 8:56 by BarryK
guess_fstype now works ARM
I booted up my Mele A1000 ARM board this morning, and now 'guess_fstype' works.
I think the problem is the Ubuntu 10.04 installation is not completely compatible with the hardware. Something is odd with the USB interface.
So, I have put the static 'guess_fstype' into the ARM initrd in Woof, also created an armv6 PET.
I will have to upgrade to latest busybox from git -- f2fs support for 'blkid' was added recently. Hopefully for 'mount' also.
Posted on 16 Feb 2013, 18:00 by technosaurus
re: busybox mount
mount uses the mount syscall and will either try to mount the specified file system, if not specified, mount just goes through /proc/filesystems trying to mount it as one of the supported filesystems (modules would have to be loaded if applicable)
Posted on 12 Mar 2013, 13:46 by 01micko
GParted f2fs patches
I have found some patches for f2fs/gparted, work too!
I have released a PHATSlacko (see derivatives section on forum) , with k3.8.2 f2fs enabled, all support pets added and just compiled GParted 14.1 with patches added. I made a usb stick with a boot partition holding all the read only files and the other partition is f2fs for the save file, works well, using grub4dos as the bootloader.