On 4/29/21 6:16 PM, Ed Greshko wrote:
On 30/04/2021 04:17, Robert McBroom via users wrote:
> On 4/26/21 12:23 AM, Robert McBroom via users wrote:
>> On 4/25/21 7:23 PM, Ed Greshko wrote:
>>> I have never tried using a tar file to restore. However using tar
>>> (both creating and restoring) without
>>> using the --selinux parameter won't preserve selinux context.
>>>
>>> Have you tried booting after adding "selinux=0" to the linux line
>>> in grub?
>>>
>> "selinux=0" works I'll do the .autorelabel
>
> .autorelabel doesn't get everything apparently. From a texmode boot
> as user, startx for the graphical desktop fails saying it can't find
> a screen. The ati 5450 has on a minimal xinitrc with no screen
> paragraphs. However, from root it works.
>
> Put selinux=0 in the kernal command in grub allows user to dos startx
> but there are I/O problems with the mouse.
>
> All the permissions look as expected
>
Well, in this case I'd then use the "ausearch" command to find the AVC
which happened at the time of failure.
You can use the --start and --end parameters to narrow down the time
frame of the search. Check the man
page for the format of that parameter.
https://access.redhat.com/articles/2191331
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/...
Could be of value in searching for the problem.
Didn't look too promising. Started over with the --selinux option on
tar and all is well. Have to look for the the discussion of --selinux
on the tar documents, hadn't seen it and the traditional use of tar for
system backup would be useless without it.