On Fri, 2021-04-23 at 07:08 -0600, home user wrote:
My gut tells me the SELinux re-label either never finished or never
started. The 4 lines that I put into my most recent post came up in
under 2 minutes after the grub menu disappeared, and I never saw any
hint of output from a SELinux relabelling. So when I try what Ed
and Joe suggest, should I also add "selinux=0" to the linux line? And
how long should I wait before assuming something is stuck in a loop,
frozen, etc. and do a hard reset?
Have you removed rhgb and quiet from the kernel line, so you can see
what your computer is doing as it boots up?
If you can get the computer to boot up, perhaps doing another reboot
with selinux=0 to see if that helps, you can manually schedule a
relabel.
touch /.autorelabel
Then reboot. When your system sees that file, it does a relabel, then
removes it when the job is done.
For what it's worth, I think it's a ridiculously silly idea to hide the
boot processes, by default, on an experimental OS that's always going
through changes. Leave that kind of dopeyness to fixed installations.
--
uname -rsvp
Linux 3.10.0-1160.24.1.el7.x86_64 #1 SMP Thu Apr 8 19:51:47 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.