On Sat, Aug 29 2009, Martin Orr wrote:
> With policycoreutils 2.0.71, "restorecon /dev/stdin" fails if stdin is a pipe:
> martin@caligula:~$ echo hi | sudo restorecon /dev/stdin
> realpath(/dev/stdin) failed No such file or directory
>
> Why would you want to do this?
> The Debian udev init script does
> ln -s /proc/self/fd/0 /dev/stdin
> restorecon /dev/stdin
> I am not sure why stdin is a pipe here but it is some consequence of the
> boot process.
>
> The intention here (and what happened with policycoreutils 2.0.69) is to
> relabel the symbolic link. But the recent realpath patch changed this, and
> I don't think there is a way now to ask restorecon to relabel an individual
> symlink.
There are consequences to this change not mentioned above: when
booting with policycoreutils 2.0.71 /dev/pts (and several other device
nodes) are not created which causes all sorts of trouble.
This is a consequence of the realpath changes in restorecon, because
when /lib/udev/create_static_nodes does
ln -s /proc/self/fd/0 /dev/stdin
restorecon /dev/stdin
it now fails with the error
realpath(/dev/stdin) failed No such file or directory
This causes create_static_nodes to exit (due to set -e) before creating
/dev/pts.
I am planning on reverting the removal of special treatment of
symlinks from the debian unstable version until this is resolved.
manoj
--
Manoj Srivastava <srivasta@xxxxxxx> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
