From: Jason Zaman <jason@perfinion.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: restorecon -r goes up the tree?
Date: Wed, 5 Oct 2016 15:28:34 +0800 [thread overview]
Message-ID: <20161005072834.GA8208@meriadoc> (raw)
Hey all,
There have been a few changes to restorecon just before RC1 and it
appears to not stay in the dir it was pointed at anymore?
meriadoc ~ # mount | grep "/dev"
udev on /dev type devtmpfs (rw,nosuid,relatime,seclabel,size=10240k,nr_inodes=1521608,mode=755)
devpts on /dev/pts type devpts (rw,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime,seclabel)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel)
meriadoc ~ # restorecon -rv /dev/
Warning no default label for /run/sm-notify.pid
Warning no default label for /run/cgmanager/fs
Warning no default label for /run/user/1000/dconf
Warning no default label for /run/user/1000/dconf/user
Warning no default label for /run/user/1000/gvfs
Warning no default label for /run/lightdm.pid
Warning no default label for /run/dbus.pid
^C
I'd already run restorecon so this output isnt as verbose as it was
before (scrollback fell off). But the first time it was also going into
/usr and /lib and many other places that are not /dev. /dev and /run are
also separate mountpoints so its not just that its doing the entire
rootfs or something cuz if that was the case it would stay in /dev.
Also "/dev" vs "/dev/" makes no difference.
-- Jason
next reply other threads:[~2016-10-05 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 7:28 Jason Zaman [this message]
2016-10-05 7:32 ` restorecon -r goes up the tree? Dominick Grift
2016-10-05 14:24 ` Richard Haines
2016-10-05 14:36 ` Stephen Smalley
2016-10-05 15:48 ` Richard Haines
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=20161005072834.GA8208@meriadoc \
--to=jason@perfinion.com \
--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.