shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-03-06 12:58:22 +03:00
Code

tree-wide: fix typo

Browse Source
This commit is contained in:
Yu Watanabe 2020-11-25 13:50:58 +09:00 committed by Lennart Poettering
parent 2824aa0796
commit 48e0abb535
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
NEWS
View File

@ -102,16 +102,16 @@ CHANGES WITH 247 in spe:
but do not handle the "change" action. If a device matching those but do not handle the "change" action. If a device matching those
rules is retriggered with the "change" action (as is intended here) rules is retriggered with the "change" action (as is intended here)
it would suddenly lose the relevant properties. This always has been it would suddenly lose the relevant properties. This always has been
a problematic, but as soon as all udev devices are triggered on problematic, but as soon as all udev devices are triggered on relevant
relevant package upgrades this will become particularly so. It is package upgrades this will become particularly so. It is strongly
strongly recommended to fix offending rules so that they can handle a recommended to fix offending rules so that they can handle a "change"
"change" action at any time, and acquire all necessary udev action at any time, and acquire all necessary udev properties even
properties even then. Or in other words: the header guard mentioned then. Or in other words: the header guard mentioned above
above (ACTION=="remove",GOTO="xyz_end") is the correct approach to (ACTION=="remove",GOTO="xyz_end") is the correct approach to handle
handle this, as it makes sure rules are rerun on "change" correctly, this, as it makes sure rules are rerun on "change" correctly, and
and acccumulate the correct and complete set of udev properties. udev accumulate the correct and complete set of udev properties. udev rule
rule definitions that cannot handle "change" events being triggered definitions that cannot handle "change" events being triggered at
at arbitrary times should be considered buggy. arbitrary times should be considered buggy.
* The MountAPIVFS= service file setting now defaults to on if * The MountAPIVFS= service file setting now defaults to on if
RootImage= and RootDirectory= are used, which means that with those RootImage= and RootDirectory= are used, which means that with those

2
man/bootctl.xml
View File

@ -112,7 +112,7 @@
These special IDs are primarily useful as a quick way to persistently make the currently booted boot loader These special IDs are primarily useful as a quick way to persistently make the currently booted boot loader
entry the default choice, or to upgrade the default boot loader entry for the next boot to the default boot entry the default choice, or to upgrade the default boot loader entry for the next boot to the default boot
loader entry for all future boots, but may be used for other operations too. loader entry for all future boots, but may be used for other operations too.
When an emptry string ("") is specified as an ID, then the corresponding EFI variable will be unset. When an empty string ("") is specified as an ID, then the corresponding EFI variable will be unset.
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>

2
src/basic/escape.h
View File

@ -16,7 +16,7 @@
/* Those that can be escaped or double-quoted. /* Those that can be escaped or double-quoted.
* *
* Stricly speaking, ! does not need to be escaped, except in interactive * Strictly speaking, ! does not need to be escaped, except in interactive
* mode, but let's be extra nice to the user and quote ! in case this * mode, but let's be extra nice to the user and quote ! in case this
* output is ever used in interactive mode. */ * output is ever used in interactive mode. */
#define SHELL_NEED_QUOTES SHELL_NEED_ESCAPE GLOB_CHARS "'()<>|&;!" #define SHELL_NEED_QUOTES SHELL_NEED_ESCAPE GLOB_CHARS "'()<>|&;!"