All of lore.kernel.org
 help / color / mirror / Atom feed
From: mgrepl@redhat.com (Miroslav Grepl)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] how to best deal with the move from bin to /usr/sbin
Date: Mon, 10 Sep 2012 13:32:20 +0200	[thread overview]
Message-ID: <504DCFC4.6040003@redhat.com> (raw)
In-Reply-To: <1347275071.2915.3.camel@d30.localdomain>

On 09/10/2012 01:04 PM, Dominick Grift wrote:
> Many distributions want to get rid of /bin and /sbin and use /usr/bin
> and usr/sbin/ respectively instead.
>
> how to best deal with that?
>
> do we add a file_contexts.subs_dist entry or edit all /bin /sbin entries
> with (usr/)?
>
> How does Fedora deal with this?
>
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
Dan added a lot of fixes to *.fc files. Basically you can check them on 
fedorahosted repo.

# git log master

and search "sbin", "bin" strings

----

commit de8b29a88b8151af675a2c8f6777be3be7dcb216
Author: Dan Walsh <dwalsh@redhat.com>
Date:   Tue Dec 6 19:20:22 2011 -0500

     Fedora is moving all files in /lib, /lib64, /sbin, /bin into 
/usr/lib, /usr/lib64, /usr/sbin and /usr/bin

     This update will fix the labeling for all these files

commit a03e14710e91870e05f3a52294ea5523477dc3db
Author: Dan Walsh <dwalsh@redhat.com>
Date:   Tue Dec 6 12:13:42 2011 -0500

     More fixes for the move from /lib, /bin, /sbin, to /usr directory

  parent reply	other threads:[~2012-09-10 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 11:04 [refpolicy] how to best deal with the move from bin to /usr/sbin Dominick Grift
     [not found] ` <CAPzO=NwM5TDgBYU7Z5hS-hsw4MHjDUDpiSO3t88zY7RQMKMqbw@mail.gmail.com>
     [not found]   ` <CAPzO=NxsJpFciPpBhG0TShvtfor5-voH4cSewggKSMYdT8_A=w@mail.gmail.com>
2012-09-10 11:13     ` Sven Vermeulen
2012-09-10 11:32 ` Miroslav Grepl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-12  7:02 Guido Trentalancia

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=504DCFC4.6040003@redhat.com \
    --to=mgrepl@redhat.com \
    --cc=refpolicy@oss.tresys.com \
    /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.