After I started a fedup update to F20, it burned up a lot of time relabeling the entire filesystem, then rebooted again. On the second reboot there were a couple of "failed to mount update media" errors; however it looks like the update rpm transaction is running. We'll see.
I have selinux turned off, I don't need it. The update script is turning it on, and relabeling everything. I'm just going to turn it off again, when the update finishes.
Is there any way to avoid wasting all this time. And what's with those error messages.
add selinux=0 on all of the kernel lines in grub.conf...I believe this disables it completely...and cannot be turned back on without removing that line and rebooting...obviously if you want to enable it and got back and use it again relabeling would need to be done.
On Sun, Dec 22, 2013 at 8:55 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
After I started a fedup update to F20, it burned up a lot of time relabeling the entire filesystem, then rebooted again. On the second reboot there were a couple of "failed to mount update media" errors; however it looks like the update rpm transaction is running. We'll see.
I have selinux turned off, I don't need it. The update script is turning it on, and relabeling everything. I'm just going to turn it off again, when the update finishes.
Is there any way to avoid wasting all this time. And what's with those error messages.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
If you want if off temporarily, till the next reboot or till you turn it on, this:
sudo setenforce 0
should also work, correct?
1 in place of 0 switches it back on, no?
Unless I am not understanding the question.
Many thanks, Ranjan
On Sun, 22 Dec 2013 09:01:50 -0600 Roger Heflin rogerheflin@gmail.com wrote:
add selinux=0 on all of the kernel lines in grub.conf...I believe this disables it completely...and cannot be turned back on without removing that line and rebooting...obviously if you want to enable it and got back and use it again relabeling would need to be done.
On Sun, Dec 22, 2013 at 8:55 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
After I started a fedup update to F20, it burned up a lot of time relabeling the entire filesystem, then rebooted again. On the second reboot there were a couple of "failed to mount update media" errors; however it looks like the update rpm transaction is running. We'll see.
I have selinux turned off, I don't need it. The update script is turning it on, and relabeling everything. I'm just going to turn it off again, when the update finishes.
Is there any way to avoid wasting all this time. And what's with those error messages.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
With all the NSA building in back doors into everything maybe SElinux should be pulled from the Fedora distros permanently. Just a thought.
On Sun, Dec 22, 2013 at 6:55 AM, Sam Varshavchik mrsam@courier-mta.com wrote:
After I started a fedup update to F20, it burned up a lot of time relabeling the entire filesystem, then rebooted again. On the second reboot there were a couple of "failed to mount update media" errors; however it looks like the update rpm transaction is running. We'll see.
I have selinux turned off, I don't need it. The update script is turning it on, and relabeling everything. I'm just going to turn it off again, when the update finishes.
Is there any way to avoid wasting all this time. And what's with those error messages. --
On Sun, 22 Dec 2013 09:55:20 -0500 Sam Varshavchik mrsam@courier-mta.com wrote:
I have selinux turned off, I don't need it. The update script is turning it on, and relabeling everything. I'm just going to turn it off again, when the update finishes.
Is there any way to avoid wasting all this time.
The relabeling during the update is being done because you kept selinux turned off on your old installation. Since F20 turns selinux on by default, it requires a relabeling of the filesystem.
The way to avoid this is to keep selinux in permissive mode, as opposed to disabled. That way labels will be kept updated throughout the life of the release, and the filesystem will not need to be relabeled (hopefully) when you decide to upgrade from F20 to F21, in the future.
And what's with those error messages.
Don't know that one...
HTH, :-) Marko
-
Keith -
Marko Vojinovic -
Ranjan Maitra -
Roger Heflin -
Sam Varshavchik