nodata píše v Po 19. 05. 2008 v 23:41 +0200: > So can you log them instead? (expletives goe here) > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151238 This is becoming one of those tiresome bugs. Frankly, boot.log is _not_ that important, compared to many other bugs. If your system must be 100% reliable and you need to diagnose every problem, you need a logged remote console to capture kernel crashes and other urgent kernel messages. In other cases, just restarting the service/server and watching the output is usable, even if not perfect. The package maintainer has decided the bug is not that important, and has closed it _twice_ already. Screaming the bug is critical (without providing any arguments) doesn't make it so. As a maintainer eventually learns, you can't win a reopen war by closing the bug; you just train your eyes to skip the bug in your queries. So, this is Fedora - the best way to make this work is to provide working code. RHEL users can contact Red Hat support if they need boot.log for some reason - but, you might be surprised, it seems no RHEL user has asked Red Hat support to make boot.log work, at least as far as I can see. Mirek -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
