From 60e36dda6e14ffff0897fb8fac7852d2e7d1a537 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=B6rg=20Behrmann?= Date: Thu, 18 Sep 2025 10:38:07 +0200 Subject: [PATCH] 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 --- man/hwdb.xml | 2 +- man/kernel-install.xml | 4 ++-- man/systemd.dnssd.xml | 2 +- man/systemd.link.xml | 4 ++-- man/systemd.network.xml | 4 ++-- man/systemd.resource-control.xml | 2 +- man/udev.xml | 2 +- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/man/hwdb.xml b/man/hwdb.xml index 6dd72c67b40..fc8aa92ea64 100644 --- a/man/hwdb.xml +++ b/man/hwdb.xml @@ -29,7 +29,7 @@ The hwdb files are read from the files located in the system hwdb directory /usr/lib/udev/hwdb.d and the local administration directory /etc/udev/hwdb.d. - 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 /etc/ have the highest priority and take precedence over files with the same diff --git a/man/kernel-install.xml b/man/kernel-install.xml index 118b152ee4e..0603292c3ef 100644 --- a/man/kernel-install.xml +++ b/man/kernel-install.xml @@ -70,7 +70,7 @@ kernel-install will run the executable files ("plugins") located in the directory /usr/lib/kernel/install.d/ and the local administration directory - /etc/kernel/install.d/. All files are collectively sorted and executed in lexical + /etc/kernel/install.d/. 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 /etc/kernel/install.d/ take precedence over files with the same name in /usr/lib/kernel/install.d/. This can be used to override a @@ -82,7 +82,7 @@ An executable placed in these directories should return 0 on success. It may also return 77 to cause the whole operation to terminate (executables later in - lexical order will be skipped). + lexicographic order will be skipped). diff --git a/man/systemd.dnssd.xml b/man/systemd.dnssd.xml index a2641e85168..aacc00dd483 100644 --- a/man/systemd.dnssd.xml +++ b/man/systemd.dnssd.xml @@ -41,7 +41,7 @@ /usr/local/lib/systemd/dnssd, the volatile runtime network directory /run/systemd/dnssd and the local administration network directory /etc/systemd/dnssd. 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 /etc/ have the highest priority, files in /run/ take precedence over files with the same name in /usr/lib/. This can be used to override a system-supplied configuration file with a diff --git a/man/systemd.link.xml b/man/systemd.link.xml index 8abab49f5bd..e4a655adbc1 100644 --- a/man/systemd.link.xml +++ b/man/systemd.link.xml @@ -72,9 +72,9 @@ 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 99-default.link is shipped by the system. Any user-supplied - .link should hence have a lexically earlier name to be considered at all. + .link should hence have a lexicographically earlier name to be considered at all. See udevadm8 for diagnosing problems with .link files. diff --git a/man/systemd.network.xml b/man/systemd.network.xml index f1becd46274..eefaa5572c2 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -1530,7 +1530,7 @@ DuplicateAddressDetection=none and the per-interface configuration with systemd-networkd once the interfaces appear later. Currently this feature is only implemented for SELinux. - The option expects a single NetLabel label. The label must conform to lexical restrictions of + 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 NetLabel @@ -1589,7 +1589,7 @@ allow my_server_t localnet_peer_t:peer recv; prefix or ifindex), NFT address family (one of arp, bridge, inet, ip, ip6, or netdev), 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 (address, prefix or ifindex) and address type (IPv4 or IPv6) as shown in the table below. diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index 07c2f617ca6..73b6734ddd6 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -1039,7 +1039,7 @@ RestrictNetworkInterfaces=~eth1 user or group), NFT address family (one of arp, bridge, inet, ip, ip6, or netdev), 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 (cgroup, user or group) 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 diff --git a/man/udev.xml b/man/udev.xml index cd3d42133a8..9a76db1ecce 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -51,7 +51,7 @@ /usr/lib/udev/rules.d and /usr/local/lib/udev/rules.d, the volatile runtime directory /run/udev/rules.d and the local administration directory /etc/udev/rules.d. 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 /etc/ have the highest priority, files in /run/ take precedence over files with the same name under /usr/. This can be used to override a system-supplied rules file with a local -- 2.47.3