On Mon, Jan 28, 2013 at 8:45 PM, Daniel J Walsh <dwalsh(a)redhat.com> wrote:
>>>> Boot your machine with enforcing=0 on the kernel
line. If you still
>>>> have the problem, then it is probably not SELinux. If it works, then
>>>> I would try to relabel.
>>>
>>>
>>> Thanks, Daniel. I have meanwhile overcome the problem by re-installing
>>> Fedora. Now, everything seems to be working perfectly.
>>>
>>> By the way,
>>>
>>> enforcing=0
>>>
>>> was to be placed in the line that starts with the word
>>>
>>> 'linux',
>>>
>>> right?
>>>
>>> How can one do the relabeling?
>>>
>> touch /.autorelabel; reboot
>
>
> Thanks, Daniel. But what is the kernel line? The one that starts with the
> word 'linux' when one at the booting time presses the key 'e'?
>
> Paul
>
Yes, something like:
linux /vmlinuz-3.8.0-0.rc4.git1.1.fc19.x86_64
root=UUID=43a08079-a288-4e6f-8767-404eb56b8df3 ro rd.md=0 rd.lvm=0 rd.dm=0
SYSFONT=True KEYTABLE=us
rd.luks.uuid=luks-d78a7fd8-3aba-4152-82c6-e9000fb2ca83
rd.luks.uuid=luks-f1cc16a9-e403-4eeb-b5c7-5a6aa567f7c6 LANG=en_US.UTF-8 rhgb quiet
Thanks, Daniel. I had done that but with no success. However, I did
not do any relabeling, unfortunately. Anyway, the problem seems to be
overcome now.
Paul