On Fri, Apr 1, 2011 at 4:17 PM, cornel panceac wrote:
>
>
> 2011/4/1 Scott Robbins
>
>> On Fri, Apr 01, 2011 at 11:26:07AM +0200, Joachim Backes wrote:
>> > >
>> > >Matej, are you sure, the enforcing=0 works around this? I tried that,
>> and
>> > >my system still does not boot. Maybe just a bad
2011/4/1 Scott Robbins
> On Fri, Apr 01, 2011 at 11:26:07AM +0200, Joachim Backes wrote:
> > >
> > >Matej, are you sure, the enforcing=0 works around this? I tried that,
> and
> > >my system still does not boot. Maybe just a bad luck, but selinux=0
> > >worked. I'm not sure about the root cause o
I tried enforcing=0, it works fine. Probably a better option which doesn't
break things later.
--
v
On Fri, Apr 1, 2011 at 3:59 PM, Vamsi Krishna Brahmajosyula <
vamsikrishna.brahmajosy...@gmail.com> wrote:
> Sorry for the presumably wrong advice, i know the difference. As long as
> selinux=0 th
Sorry for the presumably wrong advice, i know the difference. As long as
selinux=0 things changed may go
with wrong/no labels. I tried /.autorelabel , it did not kick in for unknown
reasons. Or may be we can wait till the proper
solution arrives. I did not try enforcing=0 yet.
Thanks
--
v
On Fr
On Fri, Apr 01, 2011 at 11:26:07AM +0200, Joachim Backes wrote:
> >
> >Matej, are you sure, the enforcing=0 works around this? I tried that, and
> >my system still does not boot. Maybe just a bad luck, but selinux=0
> >worked. I'm not sure about the root cause of the problem, but maybe the
> >compl
As can I, enforcing=0 does not boot, selinux=0 does.
On Apr 1, 2011 5:26 AM, "Joachim Backes"
wrote:
> On 04/01/2011 10:57 AM, Adam Pribyl wrote:
>> On Fri, 1 Apr 2011, Matej Cepl wrote:
>>
>>> Dne 31.3.2011 23:36, Vamsi Krishna Brahmajosyula napsal(a):
please add "selinux=0" as kernel parame
On 04/01/2011 10:57 AM, Adam Pribyl wrote:
On Fri, 1 Apr 2011, Matej Cepl wrote:
Dne 31.3.2011 23:36, Vamsi Krishna Brahmajosyula napsal(a):
please add "selinux=0" as kernel parameter while booting. In earlier
cases relabeling worked for me. I haven't tried with the most recent
update yet.
P
On Fri, 1 Apr 2011, Matej Cepl wrote:
Dne 31.3.2011 23:36, Vamsi Krishna Brahmajosyula napsal(a):
please add "selinux=0" as kernel parameter while booting. In earlier
cases relabeling worked for me. I haven't tried with the most recent
update yet.
Please don't spread bad advice! The correct p
Dne 31.3.2011 23:36, Vamsi Krishna Brahmajosyula napsal(a):
> please add "selinux=0" as kernel parameter while booting. In earlier
> cases relabeling worked for me. I haven't tried with the most recent
> update yet.
Please don't spread bad advice! The correct parameter is enforcing=0. If
anybody
On 04/01/2011 03:17 AM, Erik P. Olsen wrote:
> Just saw that before this message another message reported:
>
> Starting ABRT Automated Bug Reporting Tool failed, see 'systemctl status
> abrtd.service' for details.
Boot with enforcing=0. Two different but related bugs
https://bugzilla.redhat.co
On 31/03/11 23:29, Erik P. Olsen wrote:
> I have few minutes ago (21:25 UTC) updated F15 Alpha and after a reboot the
> boot
> process stopped with the message:
>
> Stopping systemd Syslog Kernel Log Buffer Bridge...
>
> And the boot process did not proceed from here.
> Has anyone seen this also?
I am not sure about the exact problem but mostly the issue has been
incorrect selinux contexts with the new updates.
please add "selinux=0" as kernel parameter while booting. In earlier cases
relabeling worked for me. I haven't tried with the most recent update yet.
thanks
-
vamsi
On Fri, Apr 1,
I have few minutes ago (21:25 UTC) updated F15 Alpha and after a reboot the
boot
process stopped with the message:
Stopping systemd Syslog Kernel Log Buffer Bridge...
And the boot process did not proceed from here.
Has anyone seen this also? And what can I do to repair the system?
--
Erik
--
13 matches
Mail list logo
