public/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

nixos/manual: Document boot.debug1mounts and clarify what exit does with shell_on_fail (#89365)

Browse Source 
* nixos/manual: document boot.debug1mounts

* nixos/manual: clarify what `exit` does with shell_on_fail
This commit is contained in:
jakobrs 2020-06-17 13:36:06 +00:00 committed by GitHub
parent dda2dd1283
commit 2ee84ca8e2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 28 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
nixos/doc/manual/administration/boot-problems.xml
View File

@ -19,9 +19,9 @@
</term> </term>
<listitem> <listitem>
<para> <para>
Start a root shell if something goes wrong in stage 1 of the boot process Allows the user to start a root shell if something goes wrong in stage 1
(the initial ramdisk). This is disabled by default because there is no of the boot process (the initial ramdisk). This is disabled by default
authentication for the root shell. because there is no authentication for the root shell.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -49,6 +49,22 @@
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry>
<term>
<literal>boot.debug1mounts</literal>
</term>
<listitem>
<para>
Like <literal>boot.debug1</literal> or
<literal>boot.debug1devices</literal>, but runs stage1 until all
filesystems that are mounted during initrd are mounted (see
<option><link linkend="opt-fileSystems._name__.neededForBoot">neededForBoot</link></option>
). As a motivating example, this could be useful if you've forgotten to set
<option><link linkend="opt-fileSystems._name__.neededForBoot">neededForBoot</link></option>
on a file system.
</para>
</listitem>
</varlistentry>
<varlistentry> <varlistentry>
<term> <term>
<literal>boot.trace</literal> <literal>boot.trace</literal>
@ -90,6 +106,15 @@
<manvolnum>1</manvolnum></citerefentry>. <manvolnum>1</manvolnum></citerefentry>.
</para> </para>
<para>
Notice that for <literal>boot.shell_on_fail</literal>,
<literal>boot.debug1</literal>, <literal>boot.debug1devices</literal>, and
<literal>boot.debug1mounts</literal>, if you did <emphasis>not</emphasis>
select "start the new shell as pid 1", and you <literal>exit</literal> from
the new shell, boot will proceed normally from the point where it failed, as
if you'd chosen "ignore the error and continue".
</para>
<para> <para>
If no login prompts or X11 login screens appear (e.g. due to hanging 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 dependencies), you can press Alt+ArrowUp. If you’re lucky, this will start