buildroot-siteTodo
- 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:
- root has a password and it's the common one
- all of the images now have the following user accounts and IDs:
- acctf/acctest -> 11846/2459
- flaci/facet -> 11121/2376
- laci/lcls -> 8412/2211
- spear/qb -> 7753/1080
- /etc/SLACproperties exists and its contents are HAVE_ROOT_PASSWORD=1
- telnet is refused
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)
...
- Questions from the 2016-11.1 (to 11.1-N where N is currently 3, as built by Eric, but we're working towards 4, collaboratively):
- The root password didn't come out as the common one when I built it (even though the /etc/shadow and /etc/passwd files match the ones that Eric built).
- The telnet service is still running when I build it (when Eric builds it, /usr/sbin/telnetd doesn't exist in the file system but /usr/bin/telnet does; when I build it, /usr/sbin/telnetd does exist in the file system and gets invoked on startup).
- Since I had already built everything once, after applying Eric's changes, I just did 'make`; do we need to do
make clean first? - Are there changes not captured in the site-top directory? If so, how do we capture those?
- Note to self: Since I'm editing on a Mac, mounting the FS directly on it, changes made to the fs_skeleton directory get touched by the Mac FS (create "*_" meta-data files). We can .gitignore these so that they don't get checked in. But creating there RFS should ignore them, as well.
- Other notes:
- I did a
make clean and a make after that but telnet was still running when I booted it. - Also, the password for root wasn't the common one.
- So, for these cases, the incremental build worked the same.
- For what's worth
chrt didn't ask for a password when changing the priority of a root thread; but it also didn't actually change the priority. - I diff'd Eric's 2016-11-2 directory with my 2016-11.1 directory and:
- From what I understood, we should have been starting with 2016-11.1 to make 2016-11.1-2 but Eric started with 2016-11. This means ALOT of things differed slightly here and there.
