Genes MailLists wrote:
I'm curious - how does a bad rsyslog package prevent the system from
booting ? Should it ??
That feels too brittle to me ... I mean its only logging after all
Ask the experts, not me.
vt1 hung endlessly, with a black screen once the daemons had finally all timed
On Sat, 19 Mar 2011, cornel panceac wrote:
what debugging options are available when f15 no longer starts?
Depends on when the start stops.
You may try serial console, dracut rdshell...
http://fedoraproject.org/wiki/How_to_debug_Dracut_problems
Adam Pribyl
--
test mailing list
2011/3/19 Adam Pribyl pri...@lowlevel.cz
On Sat, 19 Mar 2011, cornel panceac wrote:
what debugging options are available when f15 no longer starts?
Depends on when the start stops.
You may try serial console, dracut rdshell...
http://fedoraproject.org/wiki/How_to_debug_Dracut_problems
On Sat, 2011-03-19 at 18:53 +0200, cornel panceac wrote:
what debugging options are available when f15 no longer starts?
Boot rescue mode and downgrade today's updates. I could not determine
exactly which update caused the problem. I downgraded gcc, iproute,
rsyslog, libX11 and their
On 03/20/2011 01:56 AM, Jim Hayward wrote:
On Sat, 2011-03-19 at 18:53 +0200, cornel panceac wrote:
what debugging options are available when f15 no longer starts?
Boot rescue mode and downgrade today's updates. I could not determine
exactly which update caused the problem. I downgraded gcc,
Vaclav Misek wrote:
it was the rsyslog package.
Thanks a million!
yum downgrade rsyslog
cured it. I am back using F15 again.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
