| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We now choose the installed version of linux-image-rt-amd64
This will surely break if linux-image-rt-amd64 is not installed.
|
|
|
|
|
|
line=Inst base-files [9.9+deb9u6] (9.9+deb9u9 Debian:9.9/stable [amd64])
It appears the third arg, the version inside the square brackets, was added.
The code is now compatible with both the old output and the new output.
|
|
This tool is a convenience for testing. Run it in the initrd shell and
it will erase the hard drive so that you can install Samizdat fresh.
|
|
|
|
|
|
Because a non-local shell variable was accidentally overwritten, the
partitions containing a fresh install to an empty disk were never
relabeled to indicate finalization. They would have to be relabeled
manually to boot the installed system.
|
|
If there are mountpoints outside of /root, which `run-init` does not
have in its whitelist, then `run-init` will refuse to boot and will
crash the kernel instead (process 1 will exit).
|
|
|
|
|
|
(The new qemu warns about opening a file as a raw disk image unless
`raw` is specified explicitly.)
|
|
The kernel commandline syntax for `nbdroot=...` changed.
|
|
|
|
|
|
|
|
|
|
create symlink awk -> mawk
use dpkg --extract when '--real-apt' is used
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
This is more useful. The flag might be renamed "--skip-rootfs" or such.
|
|
|
|
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.
|
|
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.
|
|
|
|
This just fails earlier when the wrong GPG key is used.
The correct solution is to avoid the failure by testing for GPG keys
before offering disks to boot.
|
|
|
|
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.
|
