Date: Wed May 18 2016 09:57:47 GMT+0200 (CEST)
On 05/17/2016 05:27 PM, Laurent Bigonville wrote:
From: Laurent Bigonville <bigon@xxxxxxxx>
---
policycoreutils/semodule/semodule.8 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/policycoreutils/semodule/semodule.8 b/policycoreutils/semodule/semodule.8
index 68e95ab..7b07c45 100644
--- a/policycoreutils/semodule/semodule.8
+++ b/policycoreutils/semodule/semodule.8
@@ -116,7 +116,7 @@ $ semodule \-d alsa
# Install a module at a specific priority.
$ semodule \-X 100 \-i alsa.pp
# List all modules.
-$ semodule \-l full
+$ semodule \-\-list-modules=full
It works without " " before full:
$ semodule -lfull
What about:
policycoreutils/semodule/semodule.8:
.TP
-.B \-l,\-\-list-modules=[KIND]
+.B \-l[KIND],\-\-list-modules[=KIND]
display list of installed modules (other than base)
# List all modules.
-$ semodule \-l full
+$ semodule \-lfull
Wouldn't it be more natural to use 'all' instead of 'full' to
express listing of all modules? I would expect 'full' as an option
to some kind of formatting, like displaying full details.
# Set an alternate path for the policy root
policycoreutils/semodule/semodule.c:
printf(" -r,--remove=MODULE_NAME remove existing module\n");
- printf(" -l,--list-modules=[KIND] display list of installed
modules\n");
+ printf(" -l[KIND],--list-modules[=KIND] display list of
installed modules\n");
printf(" KIND: standard list highest priority, enabled
modules\n");
_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
|
_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
