| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | treewide: use new procd sysupgrade $UPGRADE_BACKUP variable | Rafał Miłecki | 2019-09-05 | 1 | -1/+1 |
| | | | | | | | | | | | It's a variable set by procd that should replace hardcoded /tmp/sysupgrade.tgz. This change requires the most recent procd with the commit 0f3c136 ("sysupgrade: set UPGRADE_BACKUP env variable"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> | ||||
| * | treewide: when copying a backup file always specify dest name | Rafał Miłecki | 2019-09-05 | 1 | -1/+1 |
| | | | | | | | | $CONF_TAR shouldn't be assumed to always point to the sysupgrade.tgz. This change makes code more generic and allows refactoring $CONF_TAR. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> | ||||
| * | treewide: don't hardcode "sysupgrade.tgz" file name | Rafał Miłecki | 2019-09-05 | 1 | -2/+2 |
| | | | | | | | | | 1) Add BACKUP_FILE and use it when copying an archive to be restored after sysupgrade (on the next preinit). 2) Use CONF_TAR for copying backup prepared by the /sbin/sysupgrade Signed-off-by: Rafał Miłecki <rafal@milecki.pl> | ||||
| * | treewide: sysupgrade: pass "save_partitions" option to the "sysupgrade" method | Rafał Miłecki | 2019-08-22 | 1 | -1/+1 |
| | | | | | | | | This explicitly lets stage2 know if partitions should be preserved. No more "touch /tmp/sysupgrade.always.overwrite.bootdisk.partmap" hack. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> | ||||
| * | base-files: improve lib/upgrade/common.sh | Klaus Kudielka | 2019-05-11 | 2 | -5/+4 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recently, upgrade device autodetection has been added to the mvebu target. This exposes some shortcomings of the generic export_bootdevice function, e.g. on the Turris Omnia: export_bootdevice silently reports the root partition to be the boot device. This makes the sysupgrade process fail at several places. Fix this by clearly distinguishing between /proc/cmdline arguments which specify the boot disk, and those which specify the root partition. Only in the latter case, strip off the partition, and do it consistently. root=PARTUUID=<pseudo PARTUUID for MBR> (any partition) and root=/dev/* (any partition) are accepted. The root of the problem is that the *existing* export_bootdevice in /lib/upgrade/common.sh behaves differently, if the kernel is booted with root=/dev/..., or if it is booted with root=PARTUUID=... In the former case, it reports back major/minor of the root partition, in the latter case it reports back major/minor of the complete boot disk. Targets, which boot with root=/dev/... *and* use export_bootdevice / export_partdevice, have added workarounds to this behaviour, by specifying *negative* increments to the export_partdevice function. Consequently, those targets have to be adapted to use positive increments, otherwise they are broken by the change to export_bootdevice. Fixes: 4e8345ff68 ("mvebu: base-files: autodetect upgrade device") Signed-off-by: Klaus Kudielka <klaus.kudielka@gmail.com> Tested-by: Tomasz Maciej Nowak <tomek_n@o2.pl> | ||||
| * | omap: add sysupgrade support | Lucian Cristian | 2018-07-30 | 2 | -0/+109 |
| add sysupgrade missing script files Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com> | |||||
 |
index : openwrt/upstream | |
| upstream openwrt | James |
| aboutsummaryrefslogtreecommitdiffstats |