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 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 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 from the 2016-11.1 (to 11.1-N where N is currently 3 but we're working towards 4):
  • 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.
  • 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.