mirror of
https://github.com/systemd/systemd.git
synced 2025-03-25 18:50:18 +03:00
cryptsetup: accept both "read-only" and "readonly" spellings
Mukund Sivaraman pointed out that cryptsetup(5) mentions the "read-only" option, while the code understands "readonly". We could just fix the manpage, but for consistency in naming of multi-word options it would be prettier to have "read-only". So let's accept both spellings. BZ: https://bugzilla.redhat.com/show_bug.cgi?id=903463
This commit is contained in:
parent
682cfdff69
commit
18cf1a1be5
@ -182,7 +182,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><varname>read-only</varname></term>
|
||||
<term><varname>read-only</varname></term><term><varname>readonly</varname></term>
|
||||
|
||||
<listitem><para>Set up the encrypted
|
||||
block device in read-only
|
||||
|
@ -111,7 +111,7 @@ static int parse_one_option(const char *option) {
|
||||
return 0;
|
||||
}
|
||||
|
||||
} else if (streq(option, "readonly"))
|
||||
} else if (streq(option, "readonly") || streq(option, "read-only"))
|
||||
opt_readonly = true;
|
||||
else if (streq(option, "verify"))
|
||||
opt_verify = true;
|
||||
|
Loading…
x
Reference in New Issue
Block a user