Page History

...

• 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 specific branches as tags. So, I didn't want to alter those. Perhaps we should tag them?
• In order to attempt to start where Eric left off, I went into his buildroot directories and found the diffs (using git) in the site-top directories and applied them to mine (but I checked out the "-dev" variants I created, not to disturb the originals while working on this).

• Questions/Notes 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.
    • Finally, I diff'd Eric's 2016-11-2 directory with my 2016-11.1 directory. Here's what I found:
      • 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 (not 11.1 but just 11). This means ALOT of things differed slightly here and there (mostly with the versions of packages that were used), but, interestingly:
        • The top-level .config file changed (using what?) such that how a password (user and root alike) is hashed is different (using sha-256 instead of md5), and this, in turn gets into (how?) ../output/buildroot-config/auto.conf (and autoconf.h).
        • The .config file for busybox also changed (again, using what?) such that telnet was removed from it as well as telling it to use CRYPT_SHA (what does that mean?).

• Questions/Notes from 2019-08:
  • All of the same issues for what I built after applying Eric's buildroot-site changes that I found with 2016-11.1 apply to 2019-08, namely:
    • The password didn't come out as the common one.
    • The telnet service was still running.
    • And, of course, chrt didn't work.
  • But, by exploring Eric's 2016-11-2 non-site directories, we found out why the password didn't come out right and why telnet wasn't working.
  • Since Eric did have chrt  working at one point, I'm exploring his other 2019-08 directories to see if I can glean anything from those.