summaryrefslogtreecommitdiff
path: root/initramfs-tools/scripts/samizdat
AgeCommit message (Collapse)Author
2019-10-16avoid initrd race conditionAndrew Cady
2019-10-11fix spuriously disabled outputAndrew Cady
2019-10-06initrd: visible output when waiting to find a networkAndrew Cady
2019-06-19initramfs: make sure we get $ROOTSERVER propagatedAndrew Cady
2019-06-19write /etc/resolv.conf on rootfs before bootingAndrew Cady
2019-06-18avoid hard-coded IP address for nbd serverAndrew Cady
2018-06-13Update for newer versions of nbd-clientAndrew Cady
The kernel commandline syntax for `nbdroot=...` changed.
2017-03-28Use pxelinux "ipappend" option to choose rootfs sourceAndrew Cady
This fixes the issue described in the first 'netkeys' commit, where the network would need to be available even when it was not used. The "ipappend" option results in a $BOOTIF variable in the initrd environment. This variable is now used to determine whether to wait on the network for a rootfs & keys, or to wait on the boot device becoming available to determine whether it has the keys. That is, there may or may not be a boot device which may or may not have keys and/or rootfs, but we will always know for sure whether it does, therefore there are no races and no waiting on the network unnecessarily. The qemu.sh script was updated to provide the BOOTIF variable when PXE boot is emulated.
2017-03-28change some log locationsAndrew Cady
2017-03-28fix apparently-racy orderingAndrew Cady
2017-03-28Implement boot parameter "netkeys"Andrew Cady
This allows the keys to be loaded from the boot medium even when the root filesystem is loaded over the network. I.e., specifying nbdroot= no longer implies that the keys will be loaded over the network. The ISO images generated by xorriso-usb.sh will not specify 'netkeys' so the keys on the USB stick will be used. The idea is that after install, the network should not be needed at all; but that requires using a new mechanism instead of the nbdroot= parameter, to determine dynamically whether to use a network root fs device. Currently, the network is still needed to boot a device that has its root fs on the local disk and the keys on the boot medium, even though no data is fetched from the NBD server. You can force the machine to boot by going to the initramfs shell and running: for n in $(seq 1 20); do killall ipconfig; done Otherwise it blocks waiting for the network.
2016-05-01run an extra grok-block since nbd0 wasn't mountable otherwiseAndrew Cady
2016-05-01avoid waiting for cdrom in more placesAndrew Cady
2016-05-01hide tftp error messagesAndrew Cady
2016-05-01Download gnupghome.tar when net-bootingAndrew Cady
This contains a keyring that is generated on the server for each client that netboots.
2016-04-27fix: only remove root's password on new installAndrew Cady
2016-04-25read samizdat.iso from network block device (nbd)Andrew Cady
2016-04-22add some scripts into root's homedirAndrew Cady
2016-04-19implement menu select option for booting with ramdisk rootAndrew Cady
2016-04-19remove debug output that's now unreadable anywayAndrew Cady
2016-04-19make sure real openvt (not busybox) is available and usedAndrew Cady
this fixes recovery after menu selection (menu is relaunched)
2016-04-19make the samizdat boot menu show upAndrew Cady
2016-04-19cause the grok-block hooks to runAndrew Cady
2016-04-19ensure that root can log inAndrew Cady
2016-04-19minimal, dumb mountroot()Andrew Cady
2016-04-19switch to mkinitramfs-based methodAndrew Cady