-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/21/2013 04:37 PM, Matthew Miller wrote:
On Sun, Jul 21, 2013 at 06:43:02AM -0400, Daniel J Walsh wrote:
at the end of my kickstart %post. That ain't staying, but it did fix the problem.
That is actually supposed to be done in the post at least in livecd-creator.
Huh. Well, we sure weren't with the cloud images using appliance-creator. If we use an anaconda-in-a-vm type of image creation, this wouldn't be necessary, right?
I would figure not if anaconda is doing the work. If you do the equivalent of setup followed by yum install into a chroot, then you probably need to relabel the content that was created in the setup phase.
Also if you do not use a separate kernel during your install then SELinux should probably be "disabled" from the chroot point of view, so no apps attempt to "load_policy". Since we would not policy loaded from a chrooted build on say F20 happening on a F18 build system.