Commit 18cf1a1b authored by Michal Schmidt's avatar Michal Schmidt

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
parent 682cfdff
...@@ -182,7 +182,7 @@ ...@@ -182,7 +182,7 @@
</varlistentry> </varlistentry>
<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 <listitem><para>Set up the encrypted
block device in read-only block device in read-only
......
...@@ -111,7 +111,7 @@ static int parse_one_option(const char *option) { ...@@ -111,7 +111,7 @@ static int parse_one_option(const char *option) {
return 0; return 0;
} }
} else if (streq(option, "readonly")) } else if (streq(option, "readonly") || streq(option, "read-only"))
opt_readonly = true; opt_readonly = true;
else if (streq(option, "verify")) else if (streq(option, "verify"))
opt_verify = true; opt_verify = true;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment