Filesystem for custom app usage
- This topic has 3 replies, 2 voices, and was last updated 5 years ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You cannot reply to this topic.
Home › Forums › Conduit: AEP Model › Filesystem for custom app usage
I want to store a small sqlite db to use in my custom app. Which filesystems are available for me to do so? Which would not be wiped at boot and/or firmware upgrade?
I can use /var/config, but I see there is much more space in some of the others, I just don’t know if they are appropriate for this use.
Filesystem Size Used Available Use% Mounted on
/dev/root 232.0M 176.3M 55.7M 76% /
devtmpfs 115.2M 8.0K 115.2M 0% /dev
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
debugfs 0 0 0 0% /sys/kernel/debug
tmpfs 123.3M 784.0K 122.6M 1% /run
tmpfs 123.3M 3.7M 119.6M 3% /var/volatile
configfs 0 0 0 0% /sys/kernel/config
/dev/mtdblock6 8.0M 3.5M 4.5M 44% /var/config
/dev/mtdblock7 8.0M 512.0K 7.5M 6% /var/oem
cgroup 0 0 0 0% /sys/fs/cgroup
devpts 0 0 0 0% /dev/pts
Thanks,
EG
How much space do you need?
The /var/oem partition is 8MB and survives reboot and firmware upgrades.
It is only used if you back-up settings to be used as custom factory default settings.
Only /var/config/ and /var/oem will survive a firmware upgrade.
Hmmm. I just tried to create a directory on /var/oem both with and without sudo and it said it’s a read-only filesystem. I could change /var/oem, but then I worry about it reverting in a firmware upgrade.
/dev/mtdblock6 on /var/config type jffs2 (rw,relatime)
/dev/mtdblock7 on /var/oem type jffs2 (ro,relatime)
Only /var/config/ and /var/oem will survive a firmware upgrade.
You will need to test if either will work for your requirements.