diff options
author | Christian Lamparter <chunkeey@gmail.com> | 2018-03-27 19:42:18 +0200 |
---|---|---|
committer | John Crispin <john@phrozen.org> | 2018-05-18 09:17:49 +0200 |
commit | 707b6c815bba34e9783d2695020bb17385fdcf1d (patch) | |
tree | 91b7ef0546f040bbeee3b2d9f73435abfba21ed3 /target/linux/generic | |
parent | 8f9baf5e1a9300fe66ff90486182a1fd2e645d9e (diff) | |
download | upstream-707b6c815bba34e9783d2695020bb17385fdcf1d.tar.gz upstream-707b6c815bba34e9783d2695020bb17385fdcf1d.tar.bz2 upstream-707b6c815bba34e9783d2695020bb17385fdcf1d.zip |
brcm2708: add squashfs rootfs image
This patch adds a image with squashfs as the root filesystem.
A rootfs_data partition will be generated on the first boot
and placed inside the rootfs partition (just after the squashfs
image).
advantages:
- it is possible to migrate from an existing -ext4
installation and back via sysupgrade.
- existing partition layout will not be lost.
- slightly smaller image size.
- support for attendedsysupgrade
disadvantages:
- needs f2fs + tools as well. This is because fs-tools decides on the
blocksize of the sdcard. So either f2fs or ext4 can get choosen as
the rootfs_data filesystem (depends on the size of the root partition).
- rootfs_data is placed into the rootfs partition. This makes
it difficult for tools that expect a /dev/mmc0pX device.
It also makes it difficult for data recovery tools since they
might not expect to find a embedded partition or will be
confused.
For people with existing build configurations: make sure to include mkf2fs
and f2fsck package into the image... Otherwise the new -squashfs image will
boot of a ram-overlay and won't keep the configurations after a reboot.
Cc: Álvaro Fernández Rojas <noltari@gmail.com>
Cc: Paul Spooren <spooren@informatik.uni-leipzig.de>
Cc: Daniel Golle <daniel@makrotopia.org>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Acked-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'target/linux/generic')
0 files changed, 0 insertions, 0 deletions