summary refs log tree commit diff
path: root/nixos/doc
diff options
context:
space:
mode:
authorjakobrs <jakobrs100@gmail.com>2020-12-26 10:55:40 +0100
committerjakobrs <jakobrs100@gmail.com>2021-07-03 09:53:16 +0200
commit2e4849b84104b20a275c1ac6cba150c679bc3992 (patch)
tree501c16f48276d80efcd9fda9c76f5feb2d224e6f /nixos/doc
parentfa1d0259f47732c45438893d46c70964b592572e (diff)
downloadnixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.tar
nixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.tar.gz
nixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.tar.bz2
nixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.tar.lz
nixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.tar.xz
nixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.tar.zst
nixpkgs-2e4849b84104b20a275c1ac6cba150c679bc3992.zip
installation-cd-base.nix: Add 'live.nixos.passwd' boot option
For interactive SSH access to a system without a (working)
keyboard and monitor, without rebuilding the image itself.
Diffstat (limited to 'nixos/doc')
-rw-r--r--nixos/doc/manual/administration/boot-problems.section.md6
-rw-r--r--nixos/doc/manual/from_md/administration/boot-problems.section.xml17
2 files changed, 23 insertions, 0 deletions
diff --git a/nixos/doc/manual/administration/boot-problems.section.md b/nixos/doc/manual/administration/boot-problems.section.md
index eb9209602a3..dee83e7ec22 100644
--- a/nixos/doc/manual/administration/boot-problems.section.md
+++ b/nixos/doc/manual/administration/boot-problems.section.md
@@ -30,6 +30,12 @@ If NixOS fails to boot, there are a number of kernel command line parameters tha
 
 : Make systemd very verbose and send log messages to the console instead of the journal. For more parameters recognised by systemd, see systemd(1).
 
+In addition, these arguments are recognised by the live image only:
+
+`live.nixos.passwd=password`
+
+: Set the password for the `nixos` live user. This can be used for SSH access if there are issues using the terminal.
+
 Notice that for `boot.shell_on_fail`, `boot.debug1`, `boot.debug1devices`, and `boot.debug1mounts`, if you did **not** select "start the new shell as pid 1", and you `exit` from the new shell, boot will proceed normally from the point where it failed, as if you'd chosen "ignore the error and continue".
 
 If no login prompts or X11 login screens appear (e.g. due to hanging dependencies), you can press Alt+ArrowUp. If you’re lucky, this will start rescue mode (described above). (Also note that since most units have a 90-second timeout before systemd gives up on them, the `agetty` login prompts should appear eventually unless something is very wrong.)
diff --git a/nixos/doc/manual/from_md/administration/boot-problems.section.xml b/nixos/doc/manual/from_md/administration/boot-problems.section.xml
index b484d075818..4ea01e78f32 100644
--- a/nixos/doc/manual/from_md/administration/boot-problems.section.xml
+++ b/nixos/doc/manual/from_md/administration/boot-problems.section.xml
@@ -107,6 +107,23 @@
     </varlistentry>
   </variablelist>
   <para>
+    In addition, these arguments are recognised by the live image only:
+  </para>
+  <variablelist>
+    <varlistentry>
+      <term>
+        <literal>live.nixos.passwd=password</literal>
+      </term>
+      <listitem>
+        <para>
+          Set the password for the <literal>nixos</literal> live user.
+          This can be used for SSH access if there are issues using the
+          terminal.
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  <para>
     Notice that for <literal>boot.shell_on_fail</literal>,
     <literal>boot.debug1</literal>,
     <literal>boot.debug1devices</literal>, and