diskimage-builder/elements/fedora/finalise.d/11-selinux-fixfiles-restore

#!/bin/bash

set -x

# Without fixing selinux file labels, sshd will run in the kernel_t domain
# instead of the sshd_t domain, making ssh connections fail with
# "Unable to get valid context for <user>" error message
setfiles /etc/selinux/targeted/contexts/files/file_contexts /
FIXFILES_LOG=$(mktemp)
fixfiles -l $FIXFILES_LOG restore
cat $FIXFILES_LOG
rm $FIXFILES_LOG
Trigger SELinux autorelabel on first boot. This adds about 30 seconds to my local boot time. Fixes bug #1179730 Change-Id: I519bb9289236abd43f8eb784768dcab10e2e5754 2013-05-14 00:03:24 +00:00			`#!/bin/bash`

Run fixfiles restore in chroot instead of firstboot. Boot time was 30 seconds shorter in an all-in-one devstack environment. Thanks to Ghe Rivero for a pointer to the solution https://bugzilla.redhat.com/show_bug.cgi?id=208275 Change-Id: I90d0c96d5659326ba67d6119b96d9a4113adf7fe 2013-05-16 02:33:24 +00:00			`set -x`

Trigger SELinux autorelabel on first boot. This adds about 30 seconds to my local boot time. Fixes bug #1179730 Change-Id: I519bb9289236abd43f8eb784768dcab10e2e5754 2013-05-14 00:03:24 +00:00			`# Without fixing selinux file labels, sshd will run in the kernel_t domain`
			`# instead of the sshd_t domain, making ssh connections fail with`
			`# "Unable to get valid context for <user>" error message`
Run fixfiles restore in chroot instead of firstboot. Boot time was 30 seconds shorter in an all-in-one devstack environment. Thanks to Ghe Rivero for a pointer to the solution https://bugzilla.redhat.com/show_bug.cgi?id=208275 Change-Id: I90d0c96d5659326ba67d6119b96d9a4113adf7fe 2013-05-16 02:33:24 +00:00			`setfiles /etc/selinux/targeted/contexts/files/file_contexts /`
			`FIXFILES_LOG=$(mktemp)`
			`fixfiles -l $FIXFILES_LOG restore`
			`cat $FIXFILES_LOG`
			`rm $FIXFILES_LOG`