| Note |
|---|
The documentation for SolidSense software is not maintained by SolidRun and the information herein is not actual with the latest version of the software, please contact our partner SolidSense Connect who is now developing the SolidSense software. |
SolidSense OOB purpose and overview
...
SolidSense gateways are delivered with 8Gb eMMC as hard disk with a specific partitioning to support all features. Here is the disk map implemented by the SolidSense image
Device | Purpose | Size | Mounted as |
|---|---|---|---|
/dev/mmcblk2boot0 | Boot | N/A | |
/dev/mmcblk2rpmb | RPMB | N/A | |
/dev/mmcblk2p1 | ROFS Part a | 1.5GB | /media/rfs/ro* |
/dev/mmcblk2p2 | ROFS Part b | 1.5GB | /media/rfs/ro* |
/dev/mmcblk2p3 | Overlay FS | 64MB | /media/rfs/rw |
/dev/mmcblk2p4 | Data | 4.2GB | /data |
Only one of the ROFS partitions is mounted as a given time. This the active partition containing the running read-only root file system. The partition not mounted is the backup one that can be used by Mender either to:
...
The Data partition is never directly impacted by upgrades and shall contain the stable part of the application. It can also be used to add additional features to the system. The following directories are created (and used by the system)
/data/solidsense | SolidSense configuration files. Can be extended by user |
/data/docker | Docker sub-system files |
/data/mender | Mender files (but not static configuration) |
/data/u-boot | U boot environment |
/data/.var/log | System log files (/var/log) |
Application developers can add any additional directory in /data.