David Quiqley responded
> It looks like your backup didn't backup the security labels. How did
> you make the back up? The way to get labels set back properly would be
> to book the kernel in permissive by adding enforcing=0 to the kernel
> command line. Note that this is different from selinux=0 w
On Mon, 12 Dec 2011, Daniel J Walsh wrote:
> > Suppose one makes a backup using rsync. What is the proper way to
> > back up the security labels along with the data?
> >
> > I tried using rsync's -X option, which is supposed to preserve
> > extended attributes. All that happened was I got a hu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/2011 12:38 PM, Alan Stern wrote:
> On Mon, 12 Dec 2011, David Quigley wrote:
>
>> It looks like your backup didn't backup the security labels. How
>> did you make the back up?
>
> Suppose one makes a backup using rsync. What is the proper w
On Mon, 12 Dec 2011, David Quigley wrote:
> It looks like your backup didn't backup the security labels. How did
> you make the back up?
Suppose one makes a backup using rsync. What is the proper way to
back up the security labels along with the data?
I tried using rsync's -X option, which is
It looks like your backup didn't backup the security labels. How did
you make the back up? The way to get labels set back properly would be
to book the kernel in permissive by adding enforcing=0 to the kernel
command line. Note that this is different from selinux=0 which disables
selinux comple
A new thread, was "F14 login fails on backup copy; gdm error?"
Symptoms still same:
I have a working F14 [call it F14usb8] on sda8 on my external usb.
I made a backup copy onto my 2nd scsi disk, seen as sdc7 [call it F14sdc7]
This was preparation for using it for preupgrade to F16.
Booting F14s
