Usually, in my embedded projects I set up the SD card with the following structure:
- boot: FAT32 (not mounted)
- rootfs: ext4 (mounted in ro)
- home: ext4 (mounted in rw)
(The current project uses an RPi 3 - just in case we need to talk somewhat specific.)
The boot and rootfs partitions are kept as small as possible. Instead the home partition occupies all the available space on the SD card (max 32 GB).
The home partition will contain the application specific files (executables, configuration, logs, etc...) along with the user files (i.e. multimedia, icons, or any other file that belong to the user.
To let the user to access his own files I set up a Samba share on specific folders.
Now I have a new request: make the home partition FAT32. In this way (he says) it would be easier to update files even without a network connection, just inserting the SD card in a Windows PC.
- what about using a VFAT partition for the
- as said, that partition contains also the executables and symlink to some configuration files like
/etc/network/interfacesand similar. Any caveats here? I'm afraid the lack of GID/UID support.
- any suggestion about how to manage the user/data partition in an embedded system (headless) allowing the final user to easily access the files?