mirror of
https://github.com/systemd/systemd.git
synced 2025-01-21 22:04:01 +03:00
man: typo fixes
https://bugs.freedesktop.org/show_bug.cgi?id=55890 Fixed typos, serial comma, and removed "either" as there were more than two options. Also did an extra rename of "system-shutdown" to "systemd-shutdown" that was forgotten in commit 8bd3b8620c80d0f2383f2fb04315411fc8077ca1
This commit is contained in:
Thomas Hindoe Paaboel Andersen
parent
5b4d50efe8
commit
bb31a4ac19
@ -403,7 +403,7 @@
|
||||
paths in the <filename>/sys</filename>
|
||||
file system. To create a new seat
|
||||
attach at least one graphics card to a
|
||||
previously unused seat name. seat
|
||||
previously unused seat name. Seat
|
||||
names may consist only of a-z, A-Z,
|
||||
0-9, "-" and "_" and must be prefixed
|
||||
with "seat". To drop assignment of a
|
||||
|
||||
@ -77,7 +77,7 @@
|
||||
|
||||
<para><function>sd_id128_from_string()</function>
|
||||
implements the reverse operation: it takes a 33
|
||||
character array with 32 hexadecimial digits
|
||||
character array with 32 hexadecimal digits
|
||||
(terminated by NUL) and parses them back into an
|
||||
128 bit ID returned in
|
||||
<parameter>ret</parameter>.</para>
|
||||
@ -89,7 +89,7 @@
|
||||
<para>When formatting a 128 bit ID into a string it is
|
||||
often easier to use a format string for
|
||||
<citerefentry><refentrytitle>printf</refentrytitle><manvolnum>3</manvolnum></citerefentry>. This
|
||||
is easly done using the
|
||||
is easily done using the
|
||||
<function>SD_ID128_FORMAT_STR</function> and
|
||||
<function>SD_ID128_FORMAT_VAL()</function> macros. For
|
||||
more information see
|
||||
|
||||
@ -107,7 +107,7 @@
|
||||
|
||||
<para><function>sd_is_socket()</function> may be
|
||||
called to check whether the specified file descriptor
|
||||
refers to a socket. It the
|
||||
refers to a socket. If the
|
||||
<parameter>family</parameter> parameter is not
|
||||
AF_UNSPEC it is checked whether the socket is of the
|
||||
specified family (AF_UNIX, AF_INET, ...). If the
|
||||
@ -129,7 +129,7 @@
|
||||
optionally checks the IPv4 or IPv6 port number the
|
||||
socket is bound to, unless <parameter>port</parameter>
|
||||
is zero. For this call <parameter>family</parameter>
|
||||
must be passed as either AF_UNSPEC, AF_INET or
|
||||
must be passed as either AF_UNSPEC, AF_INET, or
|
||||
AF_INET6.</para>
|
||||
|
||||
<para><function>sd_is_socket_unix()</function> is
|
||||
|
||||
@ -122,7 +122,7 @@
|
||||
again.</para>
|
||||
|
||||
<para>Note that filtering via matches only applies to
|
||||
way the journal is read, it has no effect on storage
|
||||
the way the journal is read, it has no effect on storage
|
||||
on disk.</para>
|
||||
</refsect1>
|
||||
|
||||
|
||||
@ -81,7 +81,7 @@
|
||||
|
||||
<para><function>sd_journal_get_fd()</function> returns
|
||||
a file descriptor that may be asynchronously polled in
|
||||
an external event loop and is signalled readable as
|
||||
an external event loop and is signaled readable as
|
||||
soon as the journal changes, for example because new
|
||||
entries were added. The file descriptor is suitable
|
||||
for usage in
|
||||
|
||||
@ -128,7 +128,7 @@
|
||||
as a wrapper around
|
||||
<citerefentry><refentrytitle>sd_journal_seek_head</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||
and <function>sd_journal_next()</function> in order to
|
||||
make iteratring through the journal easier. See below
|
||||
make iterating through the journal easier. See below
|
||||
for an example. Similar,
|
||||
<function>SD_JOURNAL_FOREACH_BACKWARDS()</function>
|
||||
may be used for iterating the journal in reverse
|
||||
|
||||
@ -80,7 +80,7 @@
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
|
||||
<para><function>sd_journal_open()</function> opens the
|
||||
<para><function>sd_journal_open()</function> opens
|
||||
the log journal for reading. It will find all journal
|
||||
files automatically and interleave them automatically
|
||||
when reading. As first argument it takes a pointer to
|
||||
@ -120,7 +120,7 @@
|
||||
<para>See
|
||||
<citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||
for an example how to iterate through the journal
|
||||
after opening it it with
|
||||
after opening it with
|
||||
<function>sd_journal_open()</function>.</para>
|
||||
|
||||
<para>A journal context object returned by
|
||||
|
||||
@ -194,7 +194,7 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid(
|
||||
<filename>sd-journal.h</filename>.</para>
|
||||
|
||||
<para><citerefentry><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||
and and <function>sd_journal_print()</function> may
|
||||
and <function>sd_journal_print()</function> may
|
||||
largely be used interchangeably
|
||||
functionality-wise. However, note that log messages
|
||||
logged via the former take a different path to the
|
||||
|
||||
@ -108,7 +108,7 @@
|
||||
<para><function>sd_journal_seek_realtime_usec()</function>
|
||||
seeks to the entry with the specified realtime
|
||||
(wallclock) timestamp, i.e. CLOCK_REALTIME. Note that
|
||||
the realtime clock is not necessary monotonic. If a
|
||||
the realtime clock is not necessarily monotonic. If a
|
||||
realtime timestamp is ambiguous it is not defined
|
||||
which position is sought to.</para>
|
||||
|
||||
|
||||
@ -96,7 +96,7 @@
|
||||
for more information.</para>
|
||||
|
||||
<para>It is recommended that applications log UTF-8
|
||||
mesages only with this API, but this is not
|
||||
messages only with this API, but this is not
|
||||
enforced.</para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
@ -83,20 +83,20 @@
|
||||
<title>Description</title>
|
||||
|
||||
<para><function>sd_login_monitor_new()</function> may
|
||||
be used to monitor login session, users and seats. Via
|
||||
be used to monitor login sessions, users and seats. Via
|
||||
a monitor object a file descriptor can be integrated
|
||||
into an application defined event loop which is woken
|
||||
up each time a user logs in, logs out or a seat is
|
||||
added or removed, or a session, user, or seat changes
|
||||
state otherwise. The first parameter takes a string
|
||||
which can be either <literal>seat</literal> (to get
|
||||
which can be <literal>seat</literal> (to get
|
||||
only notifications about seats being added, removed or
|
||||
changed), <literal>session</literal> (to get only
|
||||
notifications about sessions being created or removed
|
||||
or changed) or <literal>uid</literal> (to get only
|
||||
notifications when a user changes state in respect to
|
||||
logins). If notifications shall be generated in all
|
||||
these conditions, NULL may be passed. Note that in
|
||||
these conditions, NULL may be passed. Note that in the
|
||||
future additional categories may be defined. The
|
||||
second parameter returns a monitor object and needs to
|
||||
be freed with the
|
||||
|
||||
@ -87,7 +87,7 @@
|
||||
processes.</para>
|
||||
|
||||
<para>The <parameter>state</parameter> parameter
|
||||
should contain an newline-separated list of variable
|
||||
should contain a newline-separated list of variable
|
||||
assignments, similar in style to an environment
|
||||
block. A trailing newline is implied if none is
|
||||
specified. The string may contain any kind of variable
|
||||
@ -104,7 +104,7 @@
|
||||
definition file has Type=notify
|
||||
set. The passed argument is a boolean
|
||||
"1" or "0". Since there is little
|
||||
value in signalling non-readiness, the
|
||||
value in signaling non-readiness, the
|
||||
only value daemons should send is
|
||||
"READY=1".</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
@ -114,7 +114,7 @@
|
||||
and not being a shared process of a user this function
|
||||
will fail.</para>
|
||||
|
||||
<para>If the <literal>pid</literal> paramater of any
|
||||
<para>If the <literal>pid</literal> parameter of any
|
||||
of these functions is passed as 0 the operation is
|
||||
executed for the calling process.</para>
|
||||
</refsect1>
|
||||
|
||||
@ -140,8 +140,8 @@
|
||||
<title>Return Value</title>
|
||||
|
||||
<para> On success
|
||||
<function>sd_seat_get_active()</function> return
|
||||
return 0 or a positive integer. On success
|
||||
<function>sd_seat_get_active()</function>
|
||||
returns 0 or a positive integer. On success
|
||||
<function>sd_seat_get_sessions()</function> returns
|
||||
the number of entries in the session identifier
|
||||
array. If the test succeeds
|
||||
|
||||
@ -120,7 +120,7 @@
|
||||
|
||||
<para><function>sd_uid_get_sessions()</function> may
|
||||
be used to determine the current sessions of the
|
||||
specified user. Acceptes a Unix user identifier as
|
||||
specified user. Accepts a Unix user identifier as
|
||||
parameter. The <parameter>require_active</parameter>
|
||||
parameter controls whether the returned list shall
|
||||
consist of only those sessions where the user is
|
||||
|
||||
@ -178,7 +178,7 @@
|
||||
execute it immediately. If passed no
|
||||
required units of the unit passed will
|
||||
be pulled in, and no ordering
|
||||
dependencies will be honoured. This is
|
||||
dependencies will be honored. This is
|
||||
mostly a debugging and rescue tool for
|
||||
the administrator and should not be
|
||||
used by
|
||||
@ -766,7 +766,7 @@
|
||||
configuration after completing the
|
||||
disabling of the units. Note that this
|
||||
command does not implicitly stop the
|
||||
units that is being disabled. If this
|
||||
units that are being disabled. If this
|
||||
is desired an additional
|
||||
<command>stop</command> command should
|
||||
be executed afterwards.</para>
|
||||
@ -789,7 +789,7 @@
|
||||
<term><command>is-enabled [NAME...]</command></term>
|
||||
|
||||
<listitem><para>Checks whether any of
|
||||
the specified unit files is enabled
|
||||
the specified unit files are enabled
|
||||
(as with
|
||||
<command>enable</command>). Returns an
|
||||
exit code of 0 if at least one is
|
||||
|
||||
@ -90,7 +90,7 @@
|
||||
url="http://www.freedesktop.org/wiki/Software/systemd/PasswordAgents">systemd
|
||||
Password Agent Specification</ulink>.</para>
|
||||
|
||||
<para>If a password is queried on a tty the user may
|
||||
<para>If a password is queried on a TTY the user may
|
||||
press TAB to hide the asterisks normally shown for
|
||||
each character typed. Pressing Backspace as first key
|
||||
achieves the same effect.</para>
|
||||
|
||||
@ -70,7 +70,7 @@
|
||||
to. Otherwise the full systemd control group hierarchy
|
||||
is shown.</para>
|
||||
|
||||
<para>By default empty control cgroups are not
|
||||
<para>By default empty control groups are not
|
||||
shown.</para>
|
||||
</refsect1>
|
||||
|
||||
@ -107,7 +107,7 @@
|
||||
|
||||
<listitem><para>Don't hide empty
|
||||
control groups in the
|
||||
outpout.</para></listitem>
|
||||
output.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
|
||||
@ -83,9 +83,9 @@
|
||||
<literal>no</literal> disables the
|
||||
generator
|
||||
entirely. <varname>rd.luks=</varname>
|
||||
is honoured only be initial RAM disk
|
||||
is honored only by initial RAM disk
|
||||
(initrd) while
|
||||
<varname>luks=</varname> is honoured
|
||||
<varname>luks=</varname> is honored
|
||||
by both the main system and the
|
||||
initrd. </para></listitem>
|
||||
</varlistentry>
|
||||
@ -104,10 +104,10 @@
|
||||
(<varname>luks.uuid=</varname> will
|
||||
still work
|
||||
however). <varname>rd.luks.crypttab=</varname>
|
||||
is honoured only be initial RAM disk
|
||||
is honored only by initial RAM disk
|
||||
(initrd) while
|
||||
<varname>luks.crypttab=</varname> is
|
||||
honoured by both the main system and
|
||||
honored by both the main system and
|
||||
the initrd. </para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
@ -124,10 +124,10 @@
|
||||
option may be specified more than once
|
||||
in order to set up multiple
|
||||
devices. <varname>rd.luks.uuid=</varname>
|
||||
is honoured only be initial RAM disk
|
||||
is honored only by initial RAM disk
|
||||
(initrd) while
|
||||
<varname>luks.uuid=</varname> is
|
||||
honoured by both the main system and
|
||||
honored by both the main system and
|
||||
the initrd.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
@ -109,7 +109,7 @@
|
||||
comma-separated list of desired
|
||||
difference types.</para>
|
||||
|
||||
<para>Recognised types are:
|
||||
<para>Recognized types are:
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
|
||||
@ -58,7 +58,7 @@
|
||||
|
||||
<para><command>systemd-detect-virt</command> detects
|
||||
execution in a virtualized environment. It identifies
|
||||
the virtualization technology and can distuingish full
|
||||
the virtualization technology and can distinguish full
|
||||
VM virtualization from container
|
||||
virtualization.</para>
|
||||
|
||||
|
||||
@ -59,7 +59,7 @@
|
||||
for details) into native systemd units early at boot
|
||||
and when configuration of the system manager is
|
||||
reloaded. This will instantiate mount and swap units
|
||||
units as necessary.</para>
|
||||
as necessary.</para>
|
||||
|
||||
<para>See
|
||||
<citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||||
@ -94,10 +94,10 @@
|
||||
generator to ignore any mounts or swaps
|
||||
configured in
|
||||
<filename>/etc/fstab</filename>. <varname>rd.fstab=</varname>
|
||||
is honoured only be initial RAM disk
|
||||
is honored only by initial RAM disk
|
||||
(initrd) while
|
||||
<varname>luks.fstab=</varname> is
|
||||
honoured by both the main system and
|
||||
honored by both the main system and
|
||||
the initrd. </para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@ -85,7 +85,7 @@
|
||||
|
||||
<para>Immediately before executing the actual system
|
||||
halt/poweroff/reboot/kexec
|
||||
<filename>system-shutdown</filename> will run all
|
||||
<filename>systemd-shutdown</filename> will run all
|
||||
executables in
|
||||
<filename>/usr/lib/systemd/system-shutdown/</filename>
|
||||
and pass one arguments to them: either
|
||||
|
||||
@ -160,7 +160,7 @@
|
||||
may be specified in
|
||||
<citerefentry><refentrytitle>systemd-logind.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Note
|
||||
that <literal>delay</literal> is only
|
||||
available or <literal>sleep</literal>
|
||||
available for <literal>sleep</literal>
|
||||
and
|
||||
<literal>shutdown</literal>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
@ -134,7 +134,7 @@
|
||||
<title>Kernel Command Line</title>
|
||||
|
||||
<para>A few configuration parameters from
|
||||
<filename>journald.conf</filename> may be overriden on
|
||||
<filename>journald.conf</filename> may be overridden on
|
||||
the kernel command line:</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
@ -220,7 +220,7 @@
|
||||
list of capability names, see
|
||||
<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
||||
for more information. Note that the
|
||||
the following capabilities will be
|
||||
following capabilities will be
|
||||
granted in any way: CAP_CHOWN,
|
||||
CAP_DAC_OVERRIDE, CAP_DAC_READ_SEARCH,
|
||||
CAP_FOWNER, CAP_FSETID, CAP_IPC_OWNER,
|
||||
|
||||
@ -64,7 +64,7 @@
|
||||
for the actual system suspend. Similar,
|
||||
<filename>systemd-hibernate.service</filename> is
|
||||
pulled in by <filename>hibernate.target</filename> to
|
||||
executed the actual hibernation.</para>
|
||||
execute the actual hibernation.</para>
|
||||
|
||||
<para>Immediately before entering system suspend and
|
||||
hibernation
|
||||
|
||||
@ -83,7 +83,7 @@
|
||||
<term><option>--exec-delay=</option></term>
|
||||
<listitem>
|
||||
|
||||
<para>Delay the execution of RUN intruction by the given
|
||||
<para>Delay the execution of RUN instruction by the given
|
||||
number of seconds. This option might be useful when
|
||||
debugging system crashes during coldplug caused by loading
|
||||
non-working kernel modules.</para>
|
||||
@ -148,7 +148,7 @@
|
||||
<term><varname>udev.exec-delay=</varname></term>
|
||||
<term><varname>rd.udev.exec-delay=</varname></term>
|
||||
<listitem>
|
||||
<para>Delay the execution of RUN intruction by the given
|
||||
<para>Delay the execution of RUN instruction by the given
|
||||
number of seconds. This option might be useful when
|
||||
debugging system crashes during coldplug caused by loading
|
||||
non-working kernel modules.</para>
|
||||
|
||||
@ -73,7 +73,7 @@
|
||||
<title>Kernel Command Line</title>
|
||||
|
||||
<para>A few configuration parameters from
|
||||
<filename>vconsole.conf</filename> may be overriden on
|
||||
<filename>vconsole.conf</filename> may be overridden on
|
||||
the kernel command line:</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
@ -130,7 +130,7 @@
|
||||
<listitem><para>Takes an absolute path
|
||||
of a directory of the automount
|
||||
point. If the automount point is not
|
||||
existing at time of the automount
|
||||
existing at time that the automount
|
||||
point is installed it is created. This
|
||||
string must be reflected in the unit
|
||||
file name. (See above.) This option is
|
||||
|
||||
@ -201,7 +201,7 @@
|
||||
capabilities will be included, the
|
||||
effect of the assignment
|
||||
inverted. Note that this option also
|
||||
effects the respective capabilities in
|
||||
affects the respective capabilities in
|
||||
the effective, permitted and
|
||||
inheritable capability sets. The
|
||||
capability bounding set may also be
|
||||
@ -220,7 +220,7 @@
|
||||
<listitem><para>Sets the timer slack
|
||||
in nanoseconds for PID 1 which is then
|
||||
inherited to all executed processes,
|
||||
unless overriden individually, for
|
||||
unless overridden individually, for
|
||||
example with the
|
||||
<varname>TimerSlackNSec=</varname>
|
||||
setting in service units (for details
|
||||
@ -264,7 +264,7 @@
|
||||
<varname>infinity</varname> to
|
||||
configure no limit on a specific
|
||||
resource. These settings may be
|
||||
overriden in individual units
|
||||
overridden in individual units
|
||||
using the corresponding LimitXXX=
|
||||
directives. Note that these resource
|
||||
limits are only defaults for units,
|
||||
|
||||
@ -215,7 +215,7 @@
|
||||
<term><varname>_SYSTEMD_OWNER_UID=</varname></term>
|
||||
|
||||
<listitem>
|
||||
<para>The contol group path in
|
||||
<para>The control group path in
|
||||
the systemd hierarchy, the
|
||||
systemd session ID (if any),
|
||||
the systemd unit name (if any)
|
||||
|
||||
@ -100,7 +100,7 @@
|
||||
script. This is useful for compatibility with
|
||||
SysV. Note that this compatibility is quite
|
||||
comprehensive but not 100%. For details about the
|
||||
incomptibilities see the <ulink
|
||||
incompatibilities see the <ulink
|
||||
url="http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities">Incompatibilities
|
||||
with SysV</ulink> document.
|
||||
</para>
|
||||
@ -219,7 +219,7 @@
|
||||
<para>Behavior of
|
||||
<option>idle</option> is very similar
|
||||
to <option>simple</option>, however
|
||||
actual execution of a the service
|
||||
actual execution of the service
|
||||
binary is delayed until all jobs are
|
||||
dispatched. This may be used to avoid
|
||||
interleaving of output of shell
|
||||
@ -245,7 +245,7 @@
|
||||
<listitem><para>Takes a boolean value
|
||||
that specifies whether systemd should
|
||||
try to guess the main PID of a service
|
||||
should if it cannot be determined
|
||||
if it cannot be determined
|
||||
reliably. This option is ignored
|
||||
unless <option>Type=forking</option>
|
||||
is set and <option>PIDFile=</option>
|
||||
@ -283,7 +283,7 @@
|
||||
<term><varname>BusName=</varname></term>
|
||||
|
||||
<listitem><para>Takes a D-Bus bus
|
||||
name, where this service is reachable
|
||||
name, that this service is reachable
|
||||
as. This option is mandatory for
|
||||
services where
|
||||
<varname>Type=</varname> is set to
|
||||
@ -341,7 +341,7 @@
|
||||
variable substitution is
|
||||
supported. Use
|
||||
<literal>${FOO}</literal> as part of a
|
||||
word, or as word of its own on the
|
||||
word, or as a word of its own on the
|
||||
command line, in which case it will be
|
||||
replaced by the value of the
|
||||
environment variable including all
|
||||
@ -578,7 +578,7 @@
|
||||
0. If set to
|
||||
<option>on-failure</option> it will be
|
||||
restarted only when it exited with an
|
||||
exit code not equalling 0, when
|
||||
exit code not equaling 0, when
|
||||
terminated by a signal (including on
|
||||
core dump), when an operation (such as
|
||||
service reload) times out or when the
|
||||
|
||||
@ -75,7 +75,7 @@
|
||||
inspired by Microsoft Windows
|
||||
<filename>.ini</filename> files.</para>
|
||||
|
||||
<para>This man pages lists the common configuration
|
||||
<para>This man page lists the common configuration
|
||||
options of all the unit types. These options need to
|
||||
be configured in the [Unit] or [Install]
|
||||
sections of the unit files.</para>
|
||||
|
||||
@ -1002,7 +1002,7 @@
|
||||
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
||||
for details about these units. The
|
||||
option prefixed with
|
||||
<literal>rd.</literal> is honoured
|
||||
<literal>rd.</literal> is honored
|
||||
only in the initial RAM disk (initrd),
|
||||
while the one that isn't prefixed only
|
||||
in the main system.</para></listitem>
|
||||
@ -1101,7 +1101,7 @@
|
||||
process and all its children at boot
|
||||
time. May be used more than once to
|
||||
set multiple variables. If the equal
|
||||
sign and variable are missing unsets
|
||||
sign and variable are missing it unsets
|
||||
an environment variable which might be
|
||||
passed in from the initial ram
|
||||
disk.</para></listitem>
|
||||
|
||||
@ -161,7 +161,7 @@ L /tmp/foobar - - - - /dev/null</programlisting>
|
||||
effect of r or R lines. Lines
|
||||
of this type accept
|
||||
shell-style globs in place of
|
||||
of normal path
|
||||
normal path
|
||||
names.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@ -94,7 +94,7 @@
|
||||
extensions are ignored.</para>
|
||||
|
||||
<para>Every line in the rules file contains at least one key-value pair.
|
||||
There are two kind of keys: match and assignment.
|
||||
There are two kinds of keys: match and assignment.
|
||||
If all match keys are matching against its value, the rule gets applied and the
|
||||
assignment keys get the specified value assigned.</para>
|
||||
|
||||
@ -327,7 +327,7 @@
|
||||
<term><option>NAME</option></term>
|
||||
<listitem>
|
||||
<para>The name to use for a network interface. The name of a device node
|
||||
can not be changed by udev, only additional symlinks can be created.</para>
|
||||
cannot be changed by udev, only additional symlinks can be created.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@ -61,7 +61,7 @@
|
||||
|
||||
<para>The basic file format of the
|
||||
<filename>vconsole.conf</filename> is a
|
||||
newline-separated list environment-like
|
||||
newline-separated list of environment-like
|
||||
shell-compatible variable assignments. It is possible
|
||||
to source the configuration from shell scripts,
|
||||
however, beyond mere variable assignments no shell
|
||||
@ -100,7 +100,7 @@
|
||||
defaults to <literal>us</literal> if
|
||||
not set. The
|
||||
<varname>KEYMAP_TOGGLE=</varname> can
|
||||
be used to configured a second toggle
|
||||
be used to configure a second toggle
|
||||
keymap and is by default
|
||||
unset.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user