All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: "SE-Linux" <selinux@tycho.nsa.gov>
Subject: what is the point of semodule -u?
Date: Wed, 23 Jul 2008 10:17:28 +1000	[thread overview]
Message-ID: <200807231017.30237.russell@coker.com.au> (raw)

semodule supports options "-i" for install and "-u" for upgrade.  It seems 
that "semodule -i" will upgrade a module, so what is the point 
of "semodule -u"?  Are we assuming that a user or script that calls semodule 
doesn't know what it is doing and relies on the "-u" option refusing to 
install the same (or an older) version for correct results?

If so then I doubt that it will work well as I don't think that versions can 
be tracked accurately with the way the code is developed (EG a new release 
from a distribution vendor might have a higher version number than your local 
customisation even though your local changes are more relevant for your 
environment).

-- 
russell@coker.com.au
http://etbe.coker.com.au/          My Blog

http://www.coker.com.au/sponsorship.html Sponsoring Free Software development

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

             reply	other threads:[~2008-07-23  0:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  0:17 Russell Coker [this message]
2008-07-23  2:11 ` what is the point of semodule -u? Stephen Smalley
2008-07-23  2:42   ` Russell Coker
2008-07-25  2:08     ` Policy loading: initramfs vs. patched /sbin/init Stephen Smalley
2008-07-25  3:35       ` Russell Coker
2008-07-25 13:38         ` Stephen Smalley
2008-07-25 21:33           ` Russell Coker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200807231017.30237.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.