Change:
When downloading the aarch64 sdcard image, the provided there imports , which imports , which (among others) enables the nixos manual on tty8, force-enables the documentation, disabes sudo and udisks, disables sshd on bootup and enables automatic login as root without password. We probably want to provide a different in not importing installer-related things (or at least make it easy to disable them). Download the aarch64 sdcard image flash it to a raspberry pi3 edit (add for example) call wonder why it's not started cc
The idea here is that a using that would be identical from the first generation, since it's expected that a system is installed in-place. The end-user should as one would from the installation media. Though, I guess that shipping no configuration might be better in that optic; would not make it likely that users consider that line as being needed for their system to work. Probably, also, the motd should better explain that is already installed, merely disabled by default. That would be an improvement for the installer iso too. Thoughts?
I agree not shipping the configuration in that case might be better, if is sufficient. Is it for aarch64 already, and generates all the magic options properly, like extlinux etc.? Motd can be a bit more helpful, yeah. Also, we should probably add the information about the manual on tty8, if we don't already do.
. The just as . Looks like we're not far off :).

Discussion:
creating the image in the first place. As a result it allows users to edit and rebuild the live-system. </para> <ins> <para> On images where the installation media also becomes an installation target, copying over <literal>configuration.nix</literal> should be disabled by setting <literal>installer.cloneConfig</literal> to <literal>false</literal>. This is already done in <literal>sd-image.nix</literal>. </para> </ins> </section>

<title>Installation Device</title> <para> <del> Provides a basic configuration for installation devices like CDs. This means enabling hardware scans, using the <link linkend="sec-profile-clone-config"> Clone Config profile</link> to guarantee <filename>/etc/nixos/configuration.nix</filename> exists (for <command>nixos-rebuild</command> to work), a copy of the Nixpkgs channel snapshot used to create the install media. </del> <ins> Provides a basic configuration for installation devices like CDs. This enables redistributable firmware, includes the <link linkend="sec-profile-clone-config">Clone Config profile</link> and a copy of the Nixpkgs channel, so <command>nixos-install</command> works out of the box. </ins> </para> <para> <del> Additionally, documentation for <link linkend="opt-documentation.enable"> Nixpkgs</link> and <link linkend="opt-documentation.nixos.enable">NixOS </link> are forcefully enabled (to override the </del> <ins> Documentation for <link linkend="opt-documentation.enable">Nixpkgs</link> and <link linkend="opt-documentation.nixos.enable">NixOS</link> are forcefully enabled (to override the </ins> <link linkend="sec-profile-minimal">Minimal profile</link> preference); the <del> NixOS manual is shown automatically on TTY 8, sudo and udisks are disabled. Autologin is enabled as root. </del> <ins> NixOS manual is shown automatically on TTY 8, udisks is disabled. Autologin is enabled as <literal>nixos</literal> user, while passwordless login as both <literal>root</literal> and <literal>nixos</literal> is possible. Passwordless <command>sudo</command> is enabled too. <link linkend="opt-networking.wireless.enable">wpa_supplicant</link> is enabled, but configured to not autostart. </ins> </para> <para> <del> A message is shown to the user to start a display manager if needed, ssh with <xref linkend="opt-services.openssh.permitRootLogin"/> are enabled (but doesn't autostart). WPA Supplicant is also enabled without autostart. </del> <ins> It is explained how to login, start the ssh server, and if available, how to start the display manager. </ins> </para> <para> <del> Finally, vim is installed, root is set to not have a password, the kernel is made more silent for remote public IP installs, and several settings are tweaked so that the installer has a better chance of succeeding under low-memory environments. </del> <ins> Several settings are tweaked so that the installer has a better chance of succeeding under low-memory environments. </ins> </para> </section>

rm -f /nix-path-registration fi ''; <ins> # the installation media is also the installation target, # so we don't want to provide the installation configuration.nix. installer.cloneConfig = false; </ins> }; }

services.mingetty.autologinUser = "nixos"; # Some more help text. <del> services.mingetty.helpLine = '' The "nixos" and "root" account have empty passwords.  ${ optionalString config.services.xserver.enable "Type `sudo systemctl start display-manager' tonstart the graphical user interface."} ''; </del> <ins> services.mingetty.helpLine = '' The "nixos" and "root" accounts have empty passwords. Type `sudo systemctl start sshd` to start the SSH daemon. You then must set a password for either "root" or "nixos" with `passwd` to be able to login. '' + optionalString config.services.xserver.enable '' Type `sudo systemctl start display-manager' to start the graphical user interface. ''; </ins> # Allow sshd to be started manually through "systemctl start sshd". services.openssh = {