summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-core/os-release
AgeCommit message (Collapse)AuthorFilesLines
2019-01-22Add OPENBMC_TARGET_MACHINE to /etc/os-releaseJoseph Reynolds1-1/+5
This adds a new OS identification parameter (OPENBMC_TARGET_MACHINE) to the /etc/os-release file in the generated OpenBMC image to indicate the kind of device the OpenBMC image is targeted to control. This is needed to be able to track the image back to its source code: the distro and version indicate the exact source code that was used, and the target machine says which Bitbake layer configuration within that source was used. Note the target machine name is typically set in the openbmc/meta-*/meta-MACHINE/conf/local.conf.sample file. (This is where TEMPLATECONF points to.) The "uname" command options -m (machine) and -i (hardware platform) will continue to refer to the BMC and not its target machine. Tested: On the build system, `cat $IMAGE_ROOTFS/etc/os-release` shows the correct value. (From meta-phosphor rev: e9319a8c4b7bc9b737fbb6e5359f878d5ab13e7a) Change-Id: I29483ef4a72ae80c30399c795177ed446456740d Signed-off-by: Joseph Reynolds <jrey@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-06meta-phosphor: Move layer content from common/Brad Bishop1-0/+35
Adopt a more conventional directory hierarchy. meta-phosphor is still a _long_ way from suitable for hosting on yoctoproject.org but things like this don't help. (From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b) Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>