nixos: use only URI fragment in manual options links

+1 -1
nixos/doc/manual/configuration/ad-hoc-network-config.section.md
···
# Ad-Hoc Configuration {#ad-hoc-network-config}
-
You can use [`networking.localCommands`](options.html#opt-networking.localCommands) to
specify shell commands to be run at the end of `network-setup.service`. This
is useful for doing network configuration not covered by the existing NixOS
modules. For instance, to statically configure an IPv6 address:
···
# Ad-Hoc Configuration {#ad-hoc-network-config}
+
You can use [](#opt-networking.localCommands) to
specify shell commands to be run at the end of `network-setup.service`. This
is useful for doing network configuration not covered by the existing NixOS
modules. For instance, to statically configure an IPv6 address:
+2 -2
nixos/doc/manual/configuration/firewall.section.md
···
Note that TCP port 22 (ssh) is opened automatically if the SSH daemon is
enabled (`services.openssh.enable = true`). UDP ports can be opened through
-
[`networking.firewall.allowedUDPPorts`](options.html#opt-networking.firewall.allowedUDPPorts).
To open ranges of TCP ports:
···
```
Similarly, UDP port ranges can be opened through
-
[`networking.firewall.allowedUDPPortRanges`](options.html#opt-networking.firewall.allowedUDPPortRanges).
···
Note that TCP port 22 (ssh) is opened automatically if the SSH daemon is
enabled (`services.openssh.enable = true`). UDP ports can be opened through
+
[](#opt-networking.firewall.allowedUDPPorts).
To open ranges of TCP ports:
···
```
Similarly, UDP port ranges can be opened through
+
[](#opt-networking.firewall.allowedUDPPortRanges).
+1 -1
nixos/doc/manual/configuration/ipv4-config.section.md
···
configuration is performed by `network-setup.service`.
:::
-
The host name is set using [`networking.hostName`](options.html#opt-networking.hostName):
```nix
networking.hostName = "cartman";
···
configuration is performed by `network-setup.service`.
:::
+
The host name is set using [](#opt-networking.hostName):
```nix
networking.hostName = "cartman";
+2 -2
nixos/doc/manual/configuration/ipv6-config.section.md
···
IPv6 is enabled by default. Stateless address autoconfiguration is used
to automatically assign IPv6 addresses to all interfaces, and Privacy
Extensions (RFC 4946) are enabled by default. You can adjust the default
-
for this by setting [`networking.tempAddresses`](options.html#opt-networking.tempAddresses). This option
may be overridden on a per-interface basis by
-
[`networking.interfaces.<name>.tempAddress`](options.html#opt-networking.interfaces._name_.tempAddress). You can disable
IPv6 support globally by setting:
```nix
···
IPv6 is enabled by default. Stateless address autoconfiguration is used
to automatically assign IPv6 addresses to all interfaces, and Privacy
Extensions (RFC 4946) are enabled by default. You can adjust the default
+
for this by setting [](#opt-networking.tempAddresses). This option
may be overridden on a per-interface basis by
+
[](#opt-networking.interfaces._name_.tempAddress). You can disable
IPv6 support globally by setting:
```nix
+1 -1
nixos/doc/manual/configuration/network-manager.section.md
···
details on their usage. Some desktop environments (GNOME, KDE) have
their own configuration tools for NetworkManager. On XFCE, there is no
configuration tool for NetworkManager by default: by enabling
-
[`programs.nm-applet.enable`](options.html#opt-programs.nm-applet.enable), the graphical applet will be
installed and will launch automatically when the graphical session is
started.
···
details on their usage. Some desktop environments (GNOME, KDE) have
their own configuration tools for NetworkManager. On XFCE, there is no
configuration tool for NetworkManager by default: by enabling
+
[](#opt-programs.nm-applet.enable), the graphical applet will be
installed and will launch automatically when the graphical session is
started.
+1 -1
nixos/doc/manual/configuration/renaming-interfaces.section.md
···
change](https://github.com/systemd/systemd/issues/3715#issue-165347602).
If this is undesirable, for example if you have a single ethernet card,
you can revert to the traditional scheme by setting
-
[`networking.usePredictableInterfaceNames`](options.html#opt-networking.usePredictableInterfaceNames)
to `false`.
## Assigning custom names {#sec-custom-ifnames}
···
change](https://github.com/systemd/systemd/issues/3715#issue-165347602).
If this is undesirable, for example if you have a single ethernet card,
you can revert to the traditional scheme by setting
+
[](#opt-networking.usePredictableInterfaceNames)
to `false`.
## Assigning custom names {#sec-custom-ifnames}
+1 -1
nixos/doc/manual/configuration/ssh.section.md
···
By default, root logins using a password are disallowed. They can be
disabled entirely by setting
-
[`services.openssh.permitRootLogin`](options.html#opt-services.openssh.permitRootLogin) to `"no"`.
You can declaratively specify authorised RSA/DSA public keys for a user
as follows:
···
By default, root logins using a password are disallowed. They can be
disabled entirely by setting
+
[](#opt-services.openssh.permitRootLogin) to `"no"`.
You can declaratively specify authorised RSA/DSA public keys for a user
as follows:
+2 -3
nixos/doc/manual/from_md/configuration/ad-hoc-network-config.section.xml
···
<section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="ad-hoc-network-config">
<title>Ad-Hoc Configuration</title>
<para>
-
You can use
-
<link xlink:href="options.html#opt-networking.localCommands"><literal>networking.localCommands</literal></link>
-
to specify shell commands to be run at the end of
<literal>network-setup.service</literal>. This is useful for doing
network configuration not covered by the existing NixOS modules. For
instance, to statically configure an IPv6 address:
···
<section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="ad-hoc-network-config">
<title>Ad-Hoc Configuration</title>
<para>
+
You can use <xref linkend="opt-networking.localCommands" /> to
+
specify shell commands to be run at the end of
<literal>network-setup.service</literal>. This is useful for doing
network configuration not covered by the existing NixOS modules. For
instance, to statically configure an IPv6 address:
+2 -2
nixos/doc/manual/from_md/configuration/firewall.section.xml
···
daemon is enabled
(<literal>services.openssh.enable = true</literal>). UDP ports can
be opened through
-
<link xlink:href="options.html#opt-networking.firewall.allowedUDPPorts"><literal>networking.firewall.allowedUDPPorts</literal></link>.
</para>
<para>
To open ranges of TCP ports:
···
</programlisting>
<para>
Similarly, UDP port ranges can be opened through
-
<link xlink:href="options.html#opt-networking.firewall.allowedUDPPortRanges"><literal>networking.firewall.allowedUDPPortRanges</literal></link>.
</para>
</section>
···
daemon is enabled
(<literal>services.openssh.enable = true</literal>). UDP ports can
be opened through
+
<xref linkend="opt-networking.firewall.allowedUDPPorts" />.
</para>
<para>
To open ranges of TCP ports:
···
</programlisting>
<para>
Similarly, UDP port ranges can be opened through
+
<xref linkend="opt-networking.firewall.allowedUDPPortRanges" />.
</para>
</section>
+1 -1
nixos/doc/manual/from_md/configuration/ipv4-config.section.xml
···
</note>
<para>
The host name is set using
-
<link xlink:href="options.html#opt-networking.hostName"><literal>networking.hostName</literal></link>:
</para>
<programlisting language="bash">
networking.hostName = &quot;cartman&quot;;
···
</note>
<para>
The host name is set using
+
<xref linkend="opt-networking.hostName" />:
</para>
<programlisting language="bash">
networking.hostName = &quot;cartman&quot;;
+4 -4
nixos/doc/manual/from_md/configuration/ipv6-config.section.xml
···
used to automatically assign IPv6 addresses to all interfaces, and
Privacy Extensions (RFC 4946) are enabled by default. You can adjust
the default for this by setting
-
<link xlink:href="options.html#opt-networking.tempAddresses"><literal>networking.tempAddresses</literal></link>.
-
This option may be overridden on a per-interface basis by
-
<link xlink:href="options.html#opt-networking.interfaces._name_.tempAddress"><literal>networking.interfaces.&lt;name&gt;.tempAddress</literal></link>.
-
You can disable IPv6 support globally by setting:
</para>
<programlisting language="bash">
networking.enableIPv6 = false;
···
used to automatically assign IPv6 addresses to all interfaces, and
Privacy Extensions (RFC 4946) are enabled by default. You can adjust
the default for this by setting
+
<xref linkend="opt-networking.tempAddresses" />. This option may be
+
overridden on a per-interface basis by
+
<xref linkend="opt-networking.interfaces._name_.tempAddress" />. You
+
can disable IPv6 support globally by setting:
</para>
<programlisting language="bash">
networking.enableIPv6 = false;
+3 -3
nixos/doc/manual/from_md/configuration/network-manager.section.xml
···
environments (GNOME, KDE) have their own configuration tools for
NetworkManager. On XFCE, there is no configuration tool for
NetworkManager by default: by enabling
-
<link xlink:href="options.html#opt-programs.nm-applet.enable"><literal>programs.nm-applet.enable</literal></link>,
-
the graphical applet will be installed and will launch automatically
-
when the graphical session is started.
</para>
<note>
<para>
···
environments (GNOME, KDE) have their own configuration tools for
NetworkManager. On XFCE, there is no configuration tool for
NetworkManager by default: by enabling
+
<xref linkend="opt-programs.nm-applet.enable" />, the graphical
+
applet will be installed and will launch automatically when the
+
graphical session is started.
</para>
<note>
<para>
+2 -2
nixos/doc/manual/from_md/configuration/renaming-interfaces.section.xml
···
change</link>. If this is undesirable, for example if you have a
single ethernet card, you can revert to the traditional scheme by
setting
-
<link xlink:href="options.html#opt-networking.usePredictableInterfaceNames"><literal>networking.usePredictableInterfaceNames</literal></link>
-
to <literal>false</literal>.
</para>
<section xml:id="sec-custom-ifnames">
<title>Assigning custom names</title>
···
change</link>. If this is undesirable, for example if you have a
single ethernet card, you can revert to the traditional scheme by
setting
+
<xref linkend="opt-networking.usePredictableInterfaceNames" /> to
+
<literal>false</literal>.
</para>
<section xml:id="sec-custom-ifnames">
<title>Assigning custom names</title>
+2 -2
nixos/doc/manual/from_md/configuration/ssh.section.xml
···
<para>
By default, root logins using a password are disallowed. They can be
disabled entirely by setting
-
<link xlink:href="options.html#opt-services.openssh.permitRootLogin"><literal>services.openssh.permitRootLogin</literal></link>
-
to <literal>&quot;no&quot;</literal>.
</para>
<para>
You can declaratively specify authorised RSA/DSA public keys for a
···
<para>
By default, root logins using a password are disallowed. They can be
disabled entirely by setting
+
<xref linkend="opt-services.openssh.permitRootLogin" /> to
+
<literal>&quot;no&quot;</literal>.
</para>
<para>
You can declaratively specify authorised RSA/DSA public keys for a