summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2023-06-17remove documentary comments from partviAndrew Cady
2023-06-17"fix" efi booting with disgusting hack and out-of-repo binaryAndrew Cady
it turns out all that we need to do to make EFI booting work is to replace the BOOTX64.EFI file that is produced by GRUB's "grub-install" command with the version of that file from Ventoy's upstream source of the same file: <https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk/>. Ventoy claims that to be their source here: <https://github.com/ventoy/Ventoy/blob/master/DOC/BuildVentoyFromSource.txt> """ 5.10 UEFIinSecureBoot https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk/releases Super-UEFIinSecureBoot-Disk_minimal_v3.zip unzip it and get Super-UEFIinSecureBoot-Disk_minimal.img, extract the img by 7zip. INSTALL/EFI/BOOT/BOOTX64.EFI --> EFI/BOOT/BOOTX64.EFI SHA-256: 475552c7476ad45e42344eee8b30d44c264d200ac2468428aa86fc8795fb6e34 """ That SHA-256 matches what we have downloaded and are using. I have created a separate repo containing the code that pulls down the .zip file and extract the BOOTX64.EFI file from it. That code verifies the SHA-256 hash. It can be added as a sami.git submodule. This code is not usable without that file generated by that code. This commit should be amended with a git submodule added with that code too.
2023-06-14fixup! experimental grub simplificationAndrew Cady
2023-06-13experimental grub simplificationSteven
2022-01-10switch to C ficlonerange instead of PythonAndrew Cady
2022-01-10partvi: show grub-install runtimeu
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-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-02simplify samizdat-eject.shAndrew Cady
2021-03-02mkinitramfs-samizdat: use standard location for initrd by defaultAndrew 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: 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: menu-select: robustnessAndrew Cady
Try to make menu-select slightly more robust to being run a second time after a failed run.
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-28ignore "btrfs device ready" failureAndrew Cady
2021-02-28initrd fixes: calls to "btrfs device ready"Andrew Cady
2021-02-27partvi: move all functions to topAndrew Cady
2021-02-27partvi: avoid hard-coded "_build"Andrew Cady
2021-02-27partvi: check that $GPG_INPUT_DIR is a directoryAndrew Cady
2021-02-25fixup! partvi: clarify codeAndrew Cady
2021-02-25partvi: clarify codeAndrew Cady
2021-02-25partvi: eliminate code duplicationAndrew Cady
2021-02-25use sfdisk default instead of calculating "last-lba"Andrew Cady
2021-02-25Ignore failures from grub-install EFI runAndrew Cady
The second call to grub-install, which installs an EFI bootloader, fails on this machine. No need to fail the whole process for that, since I am not using EFI.
2021-02-25partvi: fixes related to key-only modeAndrew Cady
fixed race condition in kpartx fix for sfdisk kernel reload ptable failure cleaned up some code duplication created make keymu target amended make clean target
2021-02-23key-only mode for partvi; integrated partviAndrew Cady
These commands are available in sami: make upgrade make emu make key They use partvi.
2021-02-23partvi: create key.img when $1=="key"Andrew Cady
2021-02-23make key: qemu will use curses modeAndrew Cady
2021-02-23boot menu: add shutdown optionAndrew Cady
2021-02-23mkinitramfs-samizdat: exit after fatal errorAndrew Cady
2021-02-23mkinitramfs-samizdat: correct /vmlinuz symlinkAndrew Cady
2021-01-21remove selfstrap from this archive, which should be installed from fsmgrAndrew Cady
2021-01-19eatmydata for speedAndrew Cady
2021-01-19implement more of the discoverable partition specificationAndrew Cady
2021-01-18hybrid mbr verified bootsAndrew Cady
2021-01-18hybrid mbrAndrew Cady
2021-01-18ficlonerange.pyAndrew Cady
2021-01-18loads linux kernel, panics unpacking initrdAndrew Cady
2021-01-18yes moreAndrew Cady
2021-01-18now it be really ficksedAndrew Cady
2021-01-18workingAndrew Cady
2021-01-18this is the fixAndrew Cady
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-09 22:07:19 +0000