whitespace

[automated-distro-installer] / README

diff --git a/README b/README
index 60c6e6f4c690b958c00cbfc0a3b3ce05b53e7b27..07b54a803af60796ebb4ef67e6a316532c3ea54b 100644 (file)
--- a/README
+++ b/README
@@ -12,22 +12,22 @@ Utilizes multiple disks, with scripts to automatically decrypt on
 intentional reboots, but not after shutdown or power loss.
 
 Normal install mode for fai is using pxe, but on a libreboot system,
-there is no pxe. The pxe in a normal computer is nonfree firmware. What
-I've done instead:
+there is no pxe. The pxe in a normal computer is nonfree
+firmware. Alternatives to normal pxe that I've tried:
+
+* libreboot + seabios + ipxe
 
 * Use a live cd to call pxe-kexec, this is described later in this file.
 
 * Use the fai autodiscover iso. This is more automated, so nicer.
 
 * Use an install method above to setup a gnu/linux disk partition that
-  acts like a pxe boot using kexec, but it takes a bit longer. This is
+  coordinates with libreboot grub to acts like a pxe boot using
+  kexec. The boot process takes a bit longer than normal pxe. This is
   the bootstrap partition in my scripts.
 
 Things I haven't tried:
 
-* There is iPXE, which requires standard bios functions, which can be
-  provided by seabios, which can be a libreboot payload.
-
 * The bios chip has enough room for an initrd. This could be setup to
   work like the partition I use to kexec, but it would be faster, and
   not require installing to disk.
@@ -70,18 +70,20 @@ All scripts meant to be used directly are listed here:
 
 # Scripts to setup the environment for the install
 
+sudo fai-cd -g grub.cfg.autodiscover -f -A $BASEFILE_DIR/autodiscover.iso # create autodiscover cd
+mymk-basefile # Create basefiles for various distros
 arch-pxe # Setup arch pxe boot server from an arch base image
 fai-redep # Deploy fai configuration to host "faiserver"
-faiserver-revm # using pxe & preseed, create a vm which is a fai server
 faiserver-uninstall # uninstall fai-server
 faiserver-setup # install fai-server on the current machine
 myfai-chboot # setup fai tftp and nfs. useful for doing pxe-kexec
 pxe-server # disable/enable pxe dhcp, tfp, and nfs. calls myfai-chboot
-wrt-setup-remote  # setup my router in general: dhcp, dns, etc.
+wrt-setup  # setup my router in general: dhcp, dns, etc.
 
 
 # Script to do a distro install
 
+faiserver-revm # using pxe & preseed, create a vm which is a fai server
 dsfull # install & post-install a new fai distro
 arch-init-remote # install arch after it's been booted into it's setup env
 fai-kexec # Kexec this or a remote machine using host faiserver
@@ -126,31 +128,13 @@ exit
 reboot
 
 
-# dirinstall
-
-host=kw
-distro=trisquel
-t=/dev/shm/t
-myfai-chboot default
-sudo sed -i 's/^LOGUSER=/#LOGUSER=/' /etc/fai/fai.conf
-# config umount required after a failed run, proc umount always required
-sudo umount /var/lib/fai/config ||: ; sudo umount -R $t/proc ||:
-fai-redep faiserver $distro
-sudo rm -rf $t ; mkdir $t; time sudo LANG= fai -N -u $host dirinstall $t
-
-# cleanup:
-sudo sed -i 's/^#LOGUSER=/LOGUSER=/' /etc/fai/fai.conf
-sudo umount -R $t/proc
-
+# Expected output in fai logs
 
-# Turning a dirinstall into a basefile. taken from mk-basefile
+For flidas, when installing systemd, this error happens, and it's
+a superflous upstream bug based on reading the post install script:
 
-sudo chroot $t apt-get clean
-sudo rm -f $t/etc/hostname $t/etc/resolv.conf \
-      $t/var/lib/apt/lists/*_* $t/usr/bin/qemu-*-static \
-      $t/etc/udev/rules.d/70-persistent-net.rules
-echo | sudo dd of=$t/etc/machine-id
-sudo tar --one-file-system -C $t -cf - . | gzip > /a/bin/fai-basefiles/basefiles/FLIDAS64X.tar.gz
+addgroup: The group `systemd-journal' already exists as a system group. Exiting.
+Operation failed: No such file or directory