|author||Andrew Geissler <email@example.com>||Fri May 01 14:08:32 2020 -0500|
|committer||Andrew Geissler <firstname.lastname@example.org>||Mon May 04 11:04:12 2020 -0500|
dunfell: sysvinit package needed for /run/lock Upstream systemd made the inclusion of the tmpfiles.d/legacy.conf a feature that is only provided if the sysvinit PACKAGE is set. By default systemd upstream sets this but OpenBMC overrides that in this file. The legacy.conf provides among other things, a creation of the /run/lock directory. Applications like fw_printenv and fw_setenv rely on the /run/lock directory being present. opened systemd/systemd#15668 to see if there could be a more efficient way of getting /run/lock. Tying it to sysvinit and having it in a file called legacy.conf just doesn't make a lot of sense to me. Tested: Verified /run/lock is now present in QEMU boot and that fw_printenv worked. (From meta-phosphor rev: 561141712e568d555de414363b1115f37fe2cfce) Change-Id: I32b3560b30a2743638bfe1402ba3c72203b4ab0b Signed-off-by: Andrew Geissler <email@example.com>
The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \ rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum sudo dnf groupinstall "C Development Tools and Libraries"
git clone firstname.lastname@example.org:openbmc/openbmc.git cd openbmc
Any build requires an environment variable known as
TEMPLATECONF to be set to a hardware target. You can see all of the known targets with
find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
As an example target Romulus
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile
make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
For technical discussions, please see contact info below for IRC and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or IRC.
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: