linux/poky.git/meta/recipes-core/volatile-binds, branch uninative-1.4

volatile-binds: correct path of command umount

2015-07-23T07:48:39+00:00

It calls /sbin/umount to stop service var-volatile-lib. But umount is installed into directory /bin. Correct it. (From OE-Core rev: 55851c6f389cb027496c96f6e0609c8892032e4d) Signed-off-by: Kai Kang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

volatile-binds: Set S to prevent QA warning

2015-07-07T23:01:18+00:00

Also need to correct the path to COPYING.MIT. (From OE-Core rev: 4c46a6813772d8d35dd1432dbc59f9ff4b3bd074) (From OE-Core rev: 82661c1cbc619956bb71fc2ee0f10b4048435414) Signed-off-by: Thomas Perrot Signed-off-by: Richard Purdie

volatile-binds: use ${PN} for SYSTEMD_SERVICE

2014-09-29T11:12:44+00:00

As this recipe inherits allarch, it makes no real difference whether we are using ${PN} or 'volatile-binds'. But using ${PN} would keep the same style with the other recipes in OE. (From OE-Core rev: 708cc039b6cc891e466e89d2b10fcdea6c19287c) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

volatile-binds: add recipe

2014-08-02T08:26:14+00:00

This recipe is designed to play a key role in a read-only rootfs of systemd based systems. It generates service files from a template, volatile-binds.service.in and the VOLATILE_BINDS variable. By default, VOLATILE_BINDS takes the value of "/var/volatile/lib /var/lib\n", which leads to the generation of volatile-var-lib.service file. This file doesn't have any effect in a read-write system, as it has "ConditionPathIsReadWrite = !/var/lib" in the [Unit] section. In other words, this file only has effect in a read-only rootfs. (From OE-Core rev: ed7d30dc0cdb6d6c56c50ac7a3440c4ed0ee70d3) Signed-off-by: Chen Qi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie