alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity

nixos: use only URI fragment in manual options links

Browse source
This commit is contained in:
Bobby Rong 2021-07-04 08:56:20 +08:00
parent 9f7f6d2256
commit b69b26c1a1
4 changed files with 9 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
nixos/doc/manual/administration/boot-problems.section.md
View file

@ -16,7 +16,7 @@ If NixOS fails to boot, there are a number of kernel command line parameters tha
`boot.debug1mounts`
: Like `boot.debug1` or `boot.debug1devices`, but runs stage1 until all filesystems that are mounted during initrd are mounted (see [neededForBoot](#opt-fileSystems._name_.neededForBoot)). As a motivating example, this could be useful if you've forgotten to set [neededForBoot](options.html#opt-fileSystems._name_.neededForBoot) on a file system.
: Like `boot.debug1` or `boot.debug1devices`, but runs stage1 until all filesystems that are mounted during initrd are mounted (see [neededForBoot](#opt-fileSystems._name_.neededForBoot)). As a motivating example, this could be useful if you've forgotten to set [neededForBoot](#opt-fileSystems._name_.neededForBoot) on a file system.
`boot.trace`

6
nixos/doc/manual/administration/service-mgmt.chapter.md
View file

@ -96,13 +96,11 @@ the service on boot.
*User* systemd services on the other hand, should be treated
differently. Given a package that has a systemd unit file at
`#pkg-out#/lib/systemd/user/`, using
[`systemd.packages`](options.html#opt-systemd.packages) will
`#pkg-out#/lib/systemd/user/`, using [](#opt-systemd.packages) will
make you able to start the service via `systemctl --user start`, but it
won\'t start automatically on login. However, You can imperatively
enable it by adding the package\'s attribute to
[`systemd.packages`](options.html#opt-systemd.packages)
and then do this (e.g):
[](#opt-systemd.packages) and then do this (e.g):
```ShellSession
$ mkdir -p ~/.config/systemd/user/default.target.wants

2
nixos/doc/manual/from_md/administration/boot-problems.section.xml
View file

@ -61,7 +61,7 @@
<link linkend="opt-fileSystems._name_.neededForBoot">neededForBoot</link>).
As a motivating example, this could be useful if you’ve
forgotten to set
<link xlink:href="options.html#opt-fileSystems._name_.neededForBoot">neededForBoot</link>
<link linkend="opt-fileSystems._name_.neededForBoot">neededForBoot</link>
on a file system.
</para>
</listitem>

12
nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml
View file

@ -109,13 +109,11 @@ systemd.packages = [ pkgs.packagekit ];
<emphasis>User</emphasis> systemd services on the other hand,
should be treated differently. Given a package that has a systemd
unit file at <literal>#pkg-out#/lib/systemd/user/</literal>, using
<link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link>
will make you able to start the service via
<literal>systemctl --user start</literal>, but it won't start
automatically on login. However, You can imperatively enable it by
adding the package's attribute to
<link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link>
and then do this (e.g):
<xref linkend="opt-systemd.packages" /> will make you able to
start the service via <literal>systemctl --user start</literal>,
but it won't start automatically on login. However, You can
imperatively enable it by adding the package's attribute to
<xref linkend="opt-systemd.packages" /> and then do this (e.g):
</para>
<programlisting>
$ mkdir -p ~/.config/systemd/user/default.target.wants