...
- In buildroot1 in git, create a minimal Makefile
- We need a high-level make that builds three buildroot images: LinuxRT 2019 64-bit and 32-bit and LinuxRT 2016 64-bit
- Fetch 2019 buildroot tarball and get it to actually build (did this for 64-bit, need to build 32-bit and try it)
- Fetch 2016 buildroot tarball and get it to actually build (and try it)
- We need to get Eric Gumtow's changes (i.e., encourage Eric to check the changes he made in)
- Incorporate/use Eric's changes to confirm that it works in the same way the RC3s he did worked (bug-per-bug)
- Figure out what broke between RC1 and RC3 (with respect to
chrt ) - Add unit tests for all of the new ("security patch") functionality
From Marcio's e-mail:
* Make chrt work passwordless for laci, flaci, acctf, and spear users in LinuxRT 2019.08, 2016.11.1 (14h)
* Add sudo to CentOS 7 Lite and make "sudo chrt" work passwordless for laci, flaci, acctf, and spear users (2h)
* "iocConsole -t" must work passwordless in: LinuxRT 2019.08, 2016.11.1, CentOs (11h)
* "systemctl reboot" must operate passwordless for laci, flaci, acctf, and spear users in CentOS 7 Lite (2h)
* Add the configuration files for Buildroot in a Git repo (9h)
* Study a way to operate chrt using the same command for both LinuxRT and CentOS so we could use the same bash script for both (8h)
* Automated testing script (9h)
Mike's notes/questions:
- Following the instructions Eric outlined here under "Setting up", I did the following:
- I created a directory on rhel-dev7 in /scratch with my username (jmpdude). In there, I created a buildroot directory, as Eric discusses.
- Inside /scratch/buildroot I created two directories:
- buildroot-2016.11
- buildroot-2019.08
- Because I just wanted to build the originals as is first without any changes, I didn't create the "-2" directories that Eric talks about.
- Following Eric's instructions, I was able to build and boot buildroot-2016.11.1-x86_64 as well as buildroot-2019.08-x86_64 and buildroot-2019-08-i686.
- The buildroot-2016.11.1-x86_64 build didn't work as-is. It failed while trying to contract the RFS. It was attempting to use git to create the contents of text file and git no longer operated in that way. So, it exited with an error, stopping the process.
- Since Eric's changes are on aird-b50-srv01, I was able to look in his corresponding directory to see how he got around that problem (he commented out the offending lines).
- Eric's instructions involve grabbing the buildroot-site repo on SLAC's GitHub area, slaclab, and checking out a particular branch; for buildroot-2019-08 it's br2019.08 and for buildroot-2016.11.1 it's br2016.11. I did that originally because I didn't want to change anything. These branches get checked out as "site-top" in their respective buildroot directories.
- Once I wanted to go in to start making changes, I created two new branches in buildroot-site named br2019.08-dev and br2016.11-dev.
- Question: At the moment, it appears that buildroot-site is essentially using the specific branches as tags. So, I didn't want to alter those. Perhaps we should tag them?
- In order to attempt to start off where Eric left off, I went into his buildroot directories and found the diffs (using git) in the site-top and applied them to mine (but I checked out the "-dev" variants I created, not to disturb the originals while working on this).
