various fixes

infrastructure/graduated/arch/README.md

@@ -159,7 +159,7 @@ finish the install.
 26. `echo 'en_US.UTF-8 UTF-8' > /etc/locale.gen`
 27. `echo 'KEYMAP=us' > /etc/vconsole.conf`
 28. `echo 'hostname' > /etc/hostname`
-29. `pacman -S sudo vim dhclient dhcpcd bash-completion btrfs-progs plymouth`
+29. `pacman -S sudo vim dhclient dhcpcd bash-completion btrfs-progs plymouth fwupd`
 
     - dhclient/dhcpcd provides dhcp for network
     - bash-completion provides tab complete
@@ -329,6 +329,32 @@ mkdir ~/AUR
 # When you find a project, the basic installation looks like this:
 git clone <git repo from aur>
 cd <folder name>
+```
+
+PAUSE!
+
+Read through the PKGBUILD. Specifically check:
+
+1. `depends=`: Do these make sense? Is there anything you wouldn't install?
+2. `source=`: This should be a link to **an official repository**. If it links to
+   <https://joes-back-door.git> don't install it.
+3. `sha256sums=`: Make sure this matches the package! If you have to - wget <https://link-to-deb>
+   and `sha256sum something.deb`
+4. `package() {`: This is the script for installing the package. Does everything look right? Is
+   there something going on you don't understand? Are we `curl`ing or `wget`ing things we shouldn't be?
+5. Also look through the remaining fields and check for oddities. Remember, anyone can slip anything
+   into these PKGBUILD files, but if the info looks kosher you're good to go. Basically there won't
+   be any surprises since the PKGBUILD defines everything related to the install/build process.
+
+If you've already installed a few packages and keep them in a folder, you can run a quick and dirty
+check with:
+
+```bash
+# Find all PKGBUILD files in the current tree and grep for `https` so we can find potentially unwanted web downloads.
+find . -name "PKGBUILD" -exec grep --color -Hni "https://" {} \;
+```
+
+```bash
 makepkg -si
 ```
 
@@ -531,7 +557,7 @@ Then create a snapshot service
 Description=Runs btrbk with config file at /etc/btrbk/snapshots.conf
 
 [Service]
-ExecStart=/usr/bin/btrbk -c /etc/btrbk/snapshots.conf -v run
+ExecStart=/usr/bin/btrbk -c /etc/btrbk/snapshots.conf --progress run
 ```
 
 Then create a timer for the service