Dan Walsh wrote:
> You should not need either.
> selinux=0
> Disables SELinux. The boot system leaves a flag around telling the
> system that SELinux has been disabled. The next time you enable it
> (booting without the selinux=0 flag) the system forces a relable. Which
> means every file/dir/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/22/2010 08:12 PM, jackson byers wrote:
> Daniel J Walsh wrote
>
>> You can boot with selinux=0 or enforcing=0. enforcing=0 means that
>> SELinux will block nothing, but maintain the labeling.
>
> 1) selinux=0 worked; booted up into my backup
In short, selinux=0 turns off selinux. enforcing=0 disables it.
Meaning if these are your current parameters you are not using it.
jackson byers wrote:
>Daniel J Walsh wrote
>
>> You can boot with selinux=0 or enforcing=0. enforcing=0 means that
>> SELinux will block nothing, but maintain the
Daniel J Walsh wrote
> You can boot with selinux=0 or enforcing=0. enforcing=0 means that
> SELinux will block nothing, but maintain the labeling.
1) selinux=0 worked; booted up into my backup f12, looks good.
2) next tried rebooting with enforcing=0
This was more difficult; the boot proc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/21/2010 02:56 PM, jackson byers wrote:
> [by...@f12 ~]$ uname -r
> 2.6.32.11-99.fc12.i686.PAE
>
> login SElinux error trying to boot my backup copy of f12.
> Main f12 on external usb at /media/rootusb7, ext4.
> Backup f12copy on external usb at
[by...@f12 ~]$ uname -r
2.6.32.11-99.fc12.i686.PAE
login SElinux error trying to boot my backup copy of f12.
Main f12 on external usb at /media/rootusb7, ext4.
Backup f12copy on external usb at /media/rootusb8, ext3.
Both use same /boot on internal hdisk, sdb8.
I think i got the changes correct,
