summaryrefslogtreecommitdiff
path: root/src/initrd/grok-block
AgeCommit message (Collapse)Author
2023-11-17Removal of functionality that depended on gpgAndrew Cady
This material wasn't removed in the original commit removing gpg, because it seemed to have documentary value. This commit serves as the documentation index. Some of this functionality should be reimplemented.
2023-11-17remove gpgAndrew Cady
2021-03-11calling umount slightly sooner is more correctAndrew Cady
2021-03-02initrd: do not autoboot again if first autoboot failedAndrew Cady
2021-02-28initrd fixes: calls to "btrfs device ready"Andrew Cady
2020-10-11Installed and successfully ran btrfs dev rem.Andrew Cady
Ran it in the VM with the command: make install; sudo ./src/mkinitramfs-samizdat ; sudo bash ./src/parted-usb.sh Didn't use the .patch.btrfs here yet.
2020-10-10about to reboot and try this shitAndrew Cady
2020-10-10mostly old uncommitted changesAndrew Cady
committing everything without discretion rebase -i from me
2020-08-27make set -x less noisywip-2020-09-15Andrew Cady
2017-03-28verify that we can decrypt rootfs before offering it as menu itemAndrew Cady
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-28Wait for nbd-client before using /dev/nbd0Andrew Cady
For explanation, see: https://lists.freedesktop.org/archives/systemd-devel/2014-March/018053.html But for the proper solution, see: https://lists.freedesktop.org/archives/systemd-devel/2014-March/018054.html Another option would just be to use a partitioned nbd device. The nbd device _partitions_ do not have this issue at all.
2017-03-28use mountpoint /plaintext for samizdat-plaintext partitionAndrew Cady
2017-03-26Implement booting already-installed native installAndrew Cady
This option is only available if the partitions have been renamed to indicate finalization of the install. The code that finalizes the install by renaming the partitions is available, but not yet run after the install.
2017-03-26create and boot the encrypted root filesystemAndrew Cady
2017-03-25Initial support for installing to an empty disk deviceAndrew Cady
Right now, this just installs a new GPT partition table on the disk, with the partitions samizdat needs. Then nothing happens because nothing else is implemented. It will only allow a disk to be wiped like this if there are no partitions on the disk (or if the only partitions on the disk are partially-installed samizdat partitions).
2016-05-03fix the rest of the bugsAndrew Cady
2016-05-01netbooting, with unique keys, WORKSAndrew Cady
2016-05-01avoid waiting for cdrom in more placesAndrew Cady
2016-05-01don't wait for the cdrom when all we need is the gpg homedirAndrew Cady
2016-04-29fix paths (in progress)Andrew Cady
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-02 04:55:42 +0000