Re: selinux and file system check

2010-11-01 Thread Daniel J Walsh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/01/2010 03:04 AM, cornel panceac wrote: > 2010/11/1 cornel panceac > >> >> >> 2010/10/29 Daniel J Walsh >> >>> -BEGIN PGP SIGNED MESSAGE- >>> >>> Hash: SHA1 >>> >>> On 10/29/2010 02:48 AM, cornel panceac wrote: why is the selinux

Re: selinux and file system check

2010-11-01 Thread Richard Ryniker
>> For the update / selinux relabel issue, if you write to file systems >> with selinux disabled that is going to trigger needing a relabel. > >this happens without any writing (that i know about) occuring. just enter >and exit rescue mode, with the partition(s) mounted rw. If you mount the file s

Re: selinux and file system check

2010-11-01 Thread cornel panceac
2010/10/29 Bruno Wolff III > On Fri, Oct 29, 2010 at 17:35:54 +0300, > cornel panceac wrote: > > > not yet, if possible i'll create a bug tomorrow. the behaviour is like > > this: i boot rescue environment, maybe yum update the system to be > rescued, > > then reboot on the then reboot. ""Super

Re: selinux and file system check

2010-11-01 Thread cornel panceac
2010/11/1 cornel panceac > > > 2010/10/29 Daniel J Walsh > >> -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? >> > >> >

Re: selinux and file system check

2010-11-01 Thread cornel panceac
2010/10/29 Daniel J Walsh > -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 bu

Re: selinux and file system check

2010-10-29 Thread Bruno Wolff III
On Fri, Oct 29, 2010 at 17:35:54 +0300, cornel panceac wrote: > > not yet, if possible i'll create a bug tomorrow. the behaviour is like > this: i boot rescue environment, maybe yum update the system to be rescued, > then reboot on the then reboot. ""Superblock etc" then immediately "file > syst

Re: selinux and file system check

2010-10-29 Thread cornel panceac
2010/10/29 Daniel J Walsh > -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 bu

Re: selinux and file system check

2010-10-29 Thread Daniel J Walsh
-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? -BEGIN PGP SIGNATURE---