as well.
Features people may find useful: installs encrypted trisquel, debian,
-ubuntu, and arch (havne't done recently, probably a bit broken), in a
-multi-boot setup using multiple subvolumes of a single btrfs filesystem.
-Utilizes multiple disks, with scripts to automatically decrypt on
-intentional reboots, but not after shutdown or power loss.
+ubuntu, arch, and parabola (archlike install is likely broken, I've only
+done pxe boots recently), in a multi-boot setup using multiple
+subvolumes of a single btrfs filesystem. 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.
scripts from https://iankelling.org/git, and of course there are some
hostnames that are specific to my network.
+Before doing a fai install, you will need to populate a class file. I
+use one called 5-multi-boot, which you can see example of in
+fai/config/class/50-host-classes.
+
+Before doing a fai install, you will need to populate /q/root/luks and
+/q/root/shadow, see their references.
+
All scripts meant to be used directly are listed here:
# Scripts to setup the environment for the install
-arch-pxe # Setup arch pxe boot server from an arch base image
+sudo fai-cd -g grub.cfg.autodiscover -f -A $BASEFILE_DIR/autodiscover.iso # create autodiscover cd
+mymk-basefile # Create basefiles for various distros
+archlike-pxe # Setup pxe boot server from an archlike 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
pxe-server -S HOST fai
ssh root@HOST
cat >p
+for x in /target/*; do umount $x; done
PASSWORD HERE(ctrl-d ctrl-d)
for d in /dev/disk/by-id/ata*part1; do cryptsetup luksOpen --key-file p $d crypt_dev_${d##*/}; done
# btrfs replace disk # i forget the actual command
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
+For flidas, when installing systemd, this error happens, and it's
+a superflous upstream bug based on reading the post install script:
-# Turning a dirinstall into a basefile. taken from mk-basefile
+addgroup: The group `systemd-journal' already exists as a system group. Exiting.
+Operation failed: No such file or directory
-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
+# TODO
+Change arch to archlike and to support arch and parabola
# License
iankelling.org / git / automated-distro-installer / blobdiff