Issue description
After I was not able to install NixOS directly (#49511), I tried to install ubuntu and lustrate to NixOS from there following the Documentation.
The Documentation gives a good idea on the process but does not really work as given.
I needed to use the following commands:
# this part is pretty direct from the documentation:
curl https://nixos.org/nix/install | sh
. $HOME/.nix-profile/etc/profile.d/nix.sh
nix-channel --add https://nixos.org/channels/nixos-18.09 nixpkgs
nix-channel --update
nix-env -iE "_: with import <nixpkgs/nixos> { configuration = {}; }; with config.system.build; [ nixos-generate-config nixos-install nixos-enter manual.manpages ]"
sudo `which nixos-generate-config` --root /
sudo sed -i '16i\ \ users.users.root.initialHashedPassword = "";' /etc/nixos/configuration.nix
nix-env -p /nix/var/nix/profiles/system -f '<nixpkgs/nixos>' -I nixos-config=/etc/nixos/configuration.nix -iA system
sudo chown -R 0.0 /nix
sudo touch /etc/NIXOS /etc/NIXOS_LUSTRATE
echo etc/nixos | sudo tee -a /etc/NIXOS_LUSTRATE
# This part is pretty much missing
sudo mv -v /boot /boot.bak
sudo mkdir /boot/
sudo umount /boot.bak/efi
sudo mount /dev/nvme0n1p1 /boot
sudo mv /boot/EFI /boot.bak/efi/
sudo NIXOS_INSTALL_BOOTLOADER=1 /nix/var/nix/profiles/system/bin/switch-to-configuration boot
The steps in the documentation configure systemd-boot, but do not install it.
Also moving /boot also moves the mount point, which is probably not intended.
Both issues are fixed in the commands above.
Unfortunately this still seems not to work properly as the boot scripts currently will not find the existing init. (See #49519)
Issue description
After I was not able to install NixOS directly (#49511), I tried to install ubuntu and lustrate to NixOS from there following the Documentation.
The Documentation gives a good idea on the process but does not really work as given.
I needed to use the following commands:
The steps in the documentation configure systemd-boot, but do not install it.
Also moving
/bootalso moves the mount point, which is probably not intended.Both issues are fixed in the commands above.
Unfortunately this still seems not to work properly as the boot scripts currently will not find the existing init. (See #49519)