mirror of
https://github.com/systemd/systemd
synced 2025-10-06 00:13:24 +02:00
man: change lexical to lexicographic
This changes the instances of lexical to lexicographic, thus making it easier to grep for instances of lexicographic order, since there's only one variant of the word to consider. Lexicographic is chosen since there are slightly fewer instances of lexical and lexicographic seems a better fit than lexical after checking a few dictionaries. The words lexical, lexicographic, and lexicographical are synonyms in computing, meaning an alphabetical order. Both the Oxford dictionary and Merriam-Webster make no distinction between lexicographic and lexicographical, with only Wiktionary adding a more precise meaning of Meeting lexicographical standards or requirements; worthy of being included in a dictionary. [1] Since, outside of computing, lexicographic(al) has the more specific meaning pertaining to lexicography, i.e. the editing or making of dictionaries [2], and lexical only has this as a secondary meaning after its linguistic meaning [3], lexicographic fits the meaning of including and ordering entries better. [1] https://en.wiktionary.org/wiki/lexicographical#English [2] https://www.merriam-webster.com/dictionary/lexicographic [3] https://www.oed.com/dictionary/lexical_adj
This commit is contained in:
committed by
Luca Boccassi
parent
0c25f8fd0b
commit
60e36dda6e
@@ -29,7 +29,7 @@
|
||||
<para>The hwdb files are read from the files located in the
|
||||
system hwdb directory <filename>/usr/lib/udev/hwdb.d</filename> and
|
||||
the local administration directory <filename>/etc/udev/hwdb.d</filename>.
|
||||
All hwdb files are collectively sorted and processed in lexical order,
|
||||
All hwdb files are collectively sorted and processed in lexicographic order,
|
||||
regardless of the directories in which they live. However, files with
|
||||
identical filenames replace each other. Files in <filename>/etc/</filename>
|
||||
have the highest priority and take precedence over files with the same
|
||||
|
@@ -70,7 +70,7 @@
|
||||
|
||||
<para><command>kernel-install</command> will run the executable files ("plugins") located in the
|
||||
directory <filename>/usr/lib/kernel/install.d/</filename> and the local administration directory
|
||||
<filename>/etc/kernel/install.d/</filename>. All files are collectively sorted and executed in lexical
|
||||
<filename>/etc/kernel/install.d/</filename>. All files are collectively sorted and executed in lexicographic
|
||||
order, regardless of the directory in which they live. However, files with identical filenames replace
|
||||
each other. Files in <filename>/etc/kernel/install.d/</filename> take precedence over files with the
|
||||
same name in <filename>/usr/lib/kernel/install.d/</filename>. This can be used to override a
|
||||
@@ -82,7 +82,7 @@
|
||||
|
||||
<para>An executable placed in these directories should return <constant>0</constant> on success. It may
|
||||
also return <constant>77</constant> to cause the whole operation to terminate (executables later in
|
||||
lexical order will be skipped).</para>
|
||||
lexicographic order will be skipped).</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
|
@@ -41,7 +41,7 @@
|
||||
<filename>/usr/local/lib/systemd/dnssd</filename>, the volatile runtime network directory
|
||||
<filename>/run/systemd/dnssd</filename> and the local administration network directory
|
||||
<filename>/etc/systemd/dnssd</filename>. All configuration files are collectively sorted and processed in
|
||||
lexical order, regardless of the directories in which they live. However, files with identical filenames
|
||||
lexicographic order, regardless of the directories in which they live. However, files with identical filenames
|
||||
replace each other. Files in <filename>/etc/</filename> have the highest priority, files in
|
||||
<filename>/run/</filename> take precedence over files with the same name in
|
||||
<filename>/usr/lib/</filename>. This can be used to override a system-supplied configuration file with a
|
||||
|
@@ -72,9 +72,9 @@
|
||||
|
||||
<para>The link file contains a [Match] section, which determines if a given link file may be applied to a
|
||||
given device, as well as a [Link] section specifying how the device should be configured. The first (in
|
||||
lexical order) of the link files that matches a given device is applied. Note that a default file
|
||||
lexicographic order) of the link files that matches a given device is applied. Note that a default file
|
||||
<filename>99-default.link</filename> is shipped by the system. Any user-supplied
|
||||
<filename>.link</filename> should hence have a lexically earlier name to be considered at all.</para>
|
||||
<filename>.link</filename> should hence have a lexicographically earlier name to be considered at all.</para>
|
||||
|
||||
<para>See <citerefentry><refentrytitle>udevadm</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
|
||||
diagnosing problems with <filename>.link</filename> files.</para>
|
||||
|
@@ -1530,7 +1530,7 @@ DuplicateAddressDetection=none</programlisting></para>
|
||||
and the per-interface configuration with <command>systemd-networkd</command> once the interfaces
|
||||
appear later. Currently this feature is only implemented for SELinux.</para>
|
||||
|
||||
<para>The option expects a single NetLabel label. The label must conform to lexical restrictions of
|
||||
<para>The option expects a single NetLabel label. The label must conform to lexicographic restrictions of
|
||||
LSM labels. When an interface is configured with IP addresses, the addresses and subnetwork masks
|
||||
will be appended to the <ulink
|
||||
url="https://github.com/SELinuxProject/selinux-notebook/blob/main/src/network_support.md">NetLabel
|
||||
@@ -1589,7 +1589,7 @@ allow my_server_t localnet_peer_t:peer recv;</programlisting>
|
||||
<literal>prefix</literal> or <literal>ifindex</literal>), NFT address family (one of
|
||||
<literal>arp</literal>, <literal>bridge</literal>, <literal>inet</literal>, <literal>ip</literal>,
|
||||
<literal>ip6</literal>, or <literal>netdev</literal>), table name and set name. The names of tables
|
||||
and sets must conform to lexical restrictions of NFT table names. The type of the element used in
|
||||
and sets must conform to lexicographic restrictions of NFT table names. The type of the element used in
|
||||
the NFT filter must match the type implied by the directive (<literal>address</literal>,
|
||||
<literal>prefix</literal> or <literal>ifindex</literal>) and address type (IPv4 or IPv6) as shown
|
||||
in the table below.</para>
|
||||
|
@@ -1039,7 +1039,7 @@ RestrictNetworkInterfaces=~eth1</programlisting>
|
||||
<literal>user</literal> or <literal>group</literal>), NFT address family (one of
|
||||
<literal>arp</literal>, <literal>bridge</literal>, <literal>inet</literal>, <literal>ip</literal>,
|
||||
<literal>ip6</literal>, or <literal>netdev</literal>), table name and set name. The names of tables
|
||||
and sets must conform to lexical restrictions of NFT table names. The type of the element used in
|
||||
and sets must conform to lexicographic restrictions of NFT table names. The type of the element used in
|
||||
the NFT filter must match the type implied by the directive (<literal>cgroup</literal>,
|
||||
<literal>user</literal> or <literal>group</literal>) as shown in the table below. When a control
|
||||
group or a unit is realized, the corresponding ID will be appended to the NFT sets and it will be
|
||||
|
@@ -51,7 +51,7 @@
|
||||
<filename>/usr/lib/udev/rules.d</filename> and <filename>/usr/local/lib/udev/rules.d</filename>, the
|
||||
volatile runtime directory <filename>/run/udev/rules.d</filename> and the local administration
|
||||
directory <filename>/etc/udev/rules.d</filename>. All rules files are collectively sorted and
|
||||
processed in lexical order, regardless of the directories in which they live. However, files with
|
||||
processed in lexicographic order, regardless of the directories in which they live. However, files with
|
||||
identical filenames replace each other. Files in <filename>/etc/</filename> have the highest priority,
|
||||
files in <filename>/run/</filename> take precedence over files with the same name under
|
||||
<filename>/usr/</filename>. This can be used to override a system-supplied rules file with a local
|
||||
|
Reference in New Issue
Block a user