selinux and file system check
Daniel J Walsh
dwalsh at redhat.com
Mon Nov 1 14:41:14 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
On 11/01/2010 03:04 AM, cornel panceac wrote:
> 2010/11/1 cornel panceac <cpanceac at gmail.com>
>> 2010/10/29 Daniel J Walsh <dwalsh at redhat.com>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> On 10/29/2010 02:48 AM, cornel panceac wrote:
>>>> why is the selinux relabel required when the "Superblock last
>>> mount/write is
>>>> in the future" error is fixed?
>>> No clue. Who says it is? Do you have a bugzilla reference?
> oops, sorry :)
>> it's enough to just mount the system rw in rescue mode, after reboot, and
>> after the file system fix, relabel occurs.
All that is happening is the init scripts notice that SELinux is
disabled and the touch /.autorelabel. If the / is writable this file
will be created. I guess if you are sure that you did not create
anything on the filesystem, you could remove /.autorelabel and the
system will not relabel the next time it boots with SELinux enabled.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the test