ar71xx: Fix sysupgrades for Allnet and OpenMesh devices
authorjuhosg <juhosg@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Sun, 20 Oct 2013 15:59:05 +0000 (15:59 +0000)
committerjuhosg <juhosg@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Sun, 20 Oct 2013 15:59:05 +0000 (15:59 +0000)
commit8e482b7c2606ec52f2afdc9a2e5a5f3fdd8328e1
tree0e1f61025a25bbc0e4fb0731d81f5b65e8d0a704
parent8d143568ab933367021c5d14c558c2d1488fbaf5
ar71xx: Fix sysupgrades for Allnet and OpenMesh devices

Both Allnet and OpenMesh sysupgrade uses fw_setenv from uboot-envtools to
change different settings in the uboot environment. uboot-envtools version
2013.01 introduced a filesystem lock "/var/lock/fw_printenv.lock" to guarantee
mutually exclusive access to the uboot environment. But the path /var doesn't
exist on the sysupgrade ramfs.

An upgrade on these devices fails since r36033 ("[package] uboot-envtools:
upgrade to version 2013.01.01") with following messages:

 Error opening lock file /var/lock/fw_printenv.lock
 failed to update U-Boot environment

Creating the "/var/lock" path before running fw_setenv is therefore a
requirement unless the locking functionality in fw_setenv is removed or
replaced with optional locking.

Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38483 3c298f89-4303-0410-b956-a3cf2f4a3e73
target/linux/ar71xx/base-files/lib/upgrade/allnet.sh
target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh