Sun, 4 Nov 2018 17:52:11 +0800
Ed Greshko kirjoitti:
> No, I meant when you get the boot screen to select which kernel to
> start that you type "e" and edit the linux16 line to add that to the
> end.
Sri, not good morning :) didn't think that...
Now works, was my stupid editing selinux config
fi
On 11/4/18 4:26 PM, jarmo wrote:
> Sun, 4 Nov 2018 15:58:07 +0800
> Ed Greshko kirjoitti:
>
>
>> You can probably get it to boot by adding "selinux=0" to the boot
>> params.
> Other words live media and edit via that. As quessed..
>
No, I meant when you get the boot screen to select which kernel
Sun, 4 Nov 2018 15:58:07 +0800
Ed Greshko kirjoitti:
> You can probably get it to boot by adding "selinux=0" to the boot
> params.
Other words live media and edit via that. As quessed..
Tnx, Jarmo
___
users mailing list -- users@lists.fedoraproject
On 11/4/18 3:41 PM, jarmo wrote:
> Brought nasty surprise. I have selinux disabled has been in F28
> and upgraded F29. Now, I can't get laptop (HP) running. Stops
> to: Can't find selinux policy freezing!
> Upgrade itself went smoothly, but this last systemd upgrade
> made it.
>
> Shortest way to r
Brought nasty surprise. I have selinux disabled has been in F28
and upgraded F29. Now, I can't get laptop (HP) running. Stops
to: Can't find selinux policy freezing!
Upgrade itself went smoothly, but this last systemd upgrade
made it.
Shortest way to repair system. Laptop is for testing, so no
imp
