Been struggling about to achieve this on BBB! Can't find too much information about it. Any help would be appreciated! I'm surely missing something!
- Been doing what i believe would help (does this make sense?)
Installed f2fs-tools, added f2fs modules to initramfs/modules and updated it
[After these steps i could actually create another partition (p3) format it as f2fs and mount it/use it]
Edited fstab to mount f2fs partition on boot and it was succesfully mounted on boot too.
- Been around the init-eMMC-flasher-v3.sh:
Cant really understand the partition behaviour of the script. As i understand there are 2 ways of flashing - 1partition setup and 2partition setup.
I believe my flashing procedure is doing the 2 partition setup - i see mmcblk0p1 (fat) and mmcblk0p2 (ext4). However if i mount the p1 i dont see any uEnv in there:
App Drivers LICENSE.txt README.md System Volume Information nfs-uEnv.txt
Docs ID.txt README.htm START.htm autorun.inf scripts
Isn't the uEnv.txt supposed to be in that partition? I just find it at /boot/
Is it possible to implement the process of creating rootfs as f2fs in this script?
- As i was looking around the scripts i found the beaglebone-black-eMMC-flasher.sh
which seems to have a behaviour much closer to what i want (mounts boot partition as /boot ) however if i try to run it i get "system unrecognized"
- Can anyone point any direction on how to put the rootfs on f2fs keeping the /boot on fat/ext4?