From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Sun, 28 Feb 2021 16:12:38 +0000 (+0100)
Subject: man: move motivational explanation to footnote
X-Git-Tag: v248-rc3~92^2~8
X-Git-Url: http://git-history.diyao.me/?a=commitdiff_plain;h=9273d8e6c9363f82ce4f8120879a021b0176fb30;p=systemd%2F.git

man: move motivational explanation to footnote
---

diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 0ff2b4e855..e6bfdf938b 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -246,13 +246,13 @@
       has failed, as absolute, while other names would be resolved in opposite order. The
       <varname>ndots</varname> option in <filename>/etc/resolv.conf</filename> was used to control how many
       dots the name needs to have to be resolved as relative first. This stub resolver does not implement
-      this at all: multi-label names are only resolved as FQDNs. (There are currently more than 1500
-      top-level domain names defined, and new ones are added regularly, often using "attractive" names that
-      are also likely to be used locally. Not looking up multi-label names in this fashion avoids fragility
-      in both directions: a valid global name could be obscured by a local name, and resolution of a relative
-      local name could suddenly break when a new top-level domain is created, or when a new subdomain of a
-      top-level domain in registered. Resolving any given name as either relative or absolute avoids this
-      ambiguity.)</para></listitem>
+      this at all: multi-label names are only resolved as FQDNs.<footnote><para>There are currently more than
+      1500 top-level domain names defined, and new ones are added regularly, often using "attractive" names
+      that are also likely to be used locally. Not looking up multi-label names in this fashion avoids
+      fragility in both directions: a valid global name could be obscured by a local name, and resolution of
+      a relative local name could suddenly break when a new top-level domain is created, or when a new
+      subdomain of a top-level domain in registered. Resolving any given name as either relative or absolute
+      avoids this ambiguity.)</para></footnote></para></listitem>
 
       <listitem><para>This resolver has a notion of the special <literal>.local</literal> domain used for
       MulticastDNS, and will not route queries with that suffix to unicast DNS servers unless explicitly