Re: Restored f33 on new drive from a tarball now a problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/1/21 9:59 AM, Robert McBroom via users wrote:
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/html/using_selinux/troubleshooting-problems-related-to-selinux_using-selinux

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.
_______________________________________________

To happy to soon, Did an update to get current and on reboot and login the entire system is read only. Looking at directories with emacs and all permissions look fine but any attempt to write fails.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux