various: fix typos
This commit is contained in:
@@ -14264,7 +14264,7 @@ CHANGES WITH 235:
|
||||
the "utmp" group already, and it appears to be generally understood
|
||||
that members of "utmp" can modify/flush the utmp/wtmp/lastlog/btmp
|
||||
databases. Previously this was implemented correctly for all these
|
||||
databases excepts btmp, which has been opened up like this now
|
||||
databases except btmp, which has been opened up like this now
|
||||
too. Note that while the other databases are world-readable
|
||||
(i.e. 0644), btmp is not and remains more restrictive.
|
||||
|
||||
|
||||
+1
-1
@@ -189,7 +189,7 @@ static int parse_argv(int argc, char *argv[]) {
|
||||
|
||||
if (optind + 1 != argc)
|
||||
return log_error_errno(SYNTHETIC_ERRNO(EINVAL),
|
||||
"%s excepts exactly one argument (the mount point).",
|
||||
"%s expects exactly one argument (the mount point).",
|
||||
program_invocation_short_name);
|
||||
|
||||
arg_target = argv[optind];
|
||||
|
||||
@@ -67,7 +67,7 @@ Priority=202
|
||||
Table=22
|
||||
|
||||
# The four routing policy rules below intentionally have the same config
|
||||
# excepts for their To= addresses. See issue #35874.
|
||||
# except for their To= addresses. See issue #35874.
|
||||
[RoutingPolicyRule]
|
||||
To=192.0.2.0/26
|
||||
Table=1001
|
||||
|
||||
Reference in New Issue
Block a user