ccgx:root_access
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
ccgx:root_access [2019-12-23 16:30] – [Hooks to install/run own code at boot] mvader | ccgx:root_access [2020-05-28 15:49] – [Available disk space] mvader | ||
---|---|---|---|
Line 26: | Line 26: | ||
https:// | https:// | ||
- | ==== Available | + | ==== Partitions and available |
- | See https:// | + | |
- | And see ''/ | + | On a GX Device, there are three partitions that matter: |
+ | |||
+ | * rootfs partition one | ||
+ | * rootfs partition two | ||
+ | * the data partition | ||
+ | |||
+ | Only one of the two rootfs partitions will be in use. When doing a firmware update, it will be installed on the other, and the subsequent reboot will reboot the device onto that other partition. | ||
+ | |||
+ | The data partition is not touched during a firmware update, except maybe some migration scripts that run at boot. | ||
+ | |||
+ | When doing modifications, | ||
+ | |||
+ | With regards to the size of the data partition, thats easy to check using the '' | ||
+ | |||
+ | After logging into a GX device, and checking the free disk space on the rootfs(! thats not the data partition), you might get a bit disappointed at first. Don't worry too much, by design there will always be only 5% of free space. | ||
+ | |||
+ | The reason behind is that a firmware update replaces the full filesystem on the rootfs (as an image). | ||
+ | |||
+ | To see the full space, run ''/ | ||
+ | |||
+ | For actual available diskspace on our GX Devices, see https:// | ||
+ | |||
+ | To see what resize2fs.sh | ||
+ | |||
+ | Note that a firmware update will replace all of the rootfs, as also explained above. Which implies that you'll need to run resize2fs.sh again after doing a firmware update. | ||
==== 1. Set access level to Superuser ==== | ==== 1. Set access level to Superuser ==== |
ccgx/root_access.txt · Last modified: 2024-02-09 17:06 by dfaber