summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-11-17rootfs: update build-deps.yaml for bullseyeu
2023-11-17partvi: show grub-install runtimeu
2023-11-17Makefile: avoid mv interactive prompt with -fu
2023-11-17install grub-efi instead of grub-pcx
2023-11-17add "cleanmu" make targetx
2023-11-17drop openssh patchAndrew Cady
2023-11-17Makefile: use apt instead of apt-get when availableAndrew Cady
2023-11-17avoid lsb_releaseu
2021-09-15Revert "rootfs: upgrade openssh to 8.4p1-5 and now get its dependencies from ↵Steven
sid" This reverts commit a8710d9fb1e4ed2c12d406b2b7d0f1f6c1ffbc74.
2021-03-22bump fsmgrAndrew Cady
2021-03-13This is obsoleted by (and conflicts with) fsmgr support for apt-update: trueAndrew Cady
2021-03-13initrd: improve messagingAndrew Cady
2021-03-13make cleanerAndrew Cady
2021-03-13samizdat.patchfs.btrfs was missing dependency on samizdat.seed.btrfsAndrew Cady
2021-03-13rootfs: upgrade openssh to 8.4p1-5 and now get its dependencies from sidAndrew Cady
2021-03-13bump fsmgrAndrew Cady
2021-03-13Specify REWRITE_SOURCES_LIST=y for samizdat.btrfsAndrew Cady
This means it is always on, but there is no sid access until "apt-update" is specified true.
2021-03-13Makefile: improve core command-line interface targetsAndrew Cady
2021-03-13also generate .verity file for .patch.btrfs fileAndrew Cady
2021-03-13firstboot: do not attempt to eject samizdat medium when booting to ramAndrew Cady
2021-03-12try to fix efi boot with alternative grub-install commandefi-testAndrew Cady
2021-03-11new make targets: total-destroy and testinitrdAndrew Cady
2021-03-11initrd: umount /mnt/* before bootingAndrew Cady
2021-03-11calling umount slightly sooner is more correctAndrew Cady
2021-03-03automatically make the boot medium ejectableAndrew Cady
2021-03-02Fix to make the btrfs install method work.Andrew Cady
Just figured this out. We must change the fsuid after removing the devices, because btrfs MODIFIES the READ-ONLY SEED DEVICES to mark them unavailable after when remove them from the read-write device. When we reboot with the UNMODIFIED, IMMUTABLE seed image, btrfs cannot handle the duplicate fsuid. We detect this situation (kind of) and call btrfstune -m to change the fsuid of the /dev/mapper/samizdatcrypt single device fs. Now it just works. It would be much better to call this on the booted system on the running rootfs, but btrfs can't, so we instead call it on the initrd mount time. A more proper fix might use the partition table to mark the partition as in need of 'btrfstune -m'.
2021-03-02include btrfstune and sfdisk on initrdAndrew Cady
2021-03-02simplify samizdat-eject.shAndrew Cady
2021-03-02mkinitramfs-samizdat: use standard location for initrd by defaultAndrew Cady
2021-03-02new target: make testinitrdkeyAndrew Cady
2021-03-02make-total-destroy: try to make device unbusyAndrew Cady
2021-03-02initrd: improve console loggingAndrew Cady
2021-03-02Fix dynmenu restart errorAndrew Cady
Thanks https://bbs.archlinux.org/viewtopic.php?id=94780 libncurses should change error string from 'unknown' to '$TERM is unset'!
2021-03-02initrd: improve console loggingAndrew Cady
2021-03-02initrd: do not autoboot again if first autoboot failedAndrew Cady
2021-03-02initrd: improve terminal and error handling for menuAndrew Cady
2021-03-02initrd: improve readability and robustness to recoveryAndrew Cady
The luks.secret is stored per block device, and any existing /dev/mapper/samizdatcrypt is removed before we try to create that device. This makes it more possible to recover from a failed menu-select from the emergency console.
2021-03-02initrd: more responsive/user-friendly boot loggingAndrew Cady
2021-03-02slight refactorAndrew Cady
2021-03-02initrd: menu-select: robustnessAndrew Cady
Try to make menu-select slightly more robust to being run a second time after a failed run.
2021-03-02fixup! emu support for persist.imgAndrew Cady
2021-03-02new target: make testinitrdAndrew Cady
2021-03-02partvi: do not rely on part image file to get sizeAndrew Cady
When partvi writes directly to a boot medium, it shouldn't copy part files, because these involve copying the unused parts of the filesystems. Instead, it should create a new filesystem on the target and copy files into it. This change moves in that direction.
2021-02-28silence qemu warningAndrew Cady
2021-02-28bump fsmgrAndrew Cady
2021-02-28rootfs improvementsAndrew Cady
2021-02-28make total-destroy target to overwrite persist.imgAndrew Cady
2021-02-28various rootfs improvementsAndrew Cady
2021-02-28ignore "btrfs device ready" failureAndrew Cady
2021-02-28bump fsmgr for new featureAndrew Cady