Empty bool.log

Anne Wilson cannewilson at tiscali.co.uk
Wed Nov 15 22:03:39 UTC 2006


On Wednesday 15 November 2006 21:09, Gene Heskett wrote:
> On Wednesday 15 November 2006 13:41, Paul Lemmons wrote:
> >I have poked around and found a number of discussions on
> >/var/log/boot.log being empty. Even located a bugzilla report on it
> >(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151238). However,
> >what I have not found is a solution.
> >
> >Anybody else figure out how to capture the boot log?
> >
> >$ uname -a
> >Linux xxxx.xxx.xxx 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006
> >i686 i686 i386 GNU/Linux
>
> When you boot, the final log, in addition to being appended
> to /var/log/messages is written out to /var/log/dmesg.  This is the
> current boot as its overwritten by a new boot.
>
But don't you think that is totally illogical?  boot.log would be a much 
better place for it.

Anne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20061115/85e5e96e/attachment-0001.sig>


More information about the fedora-list mailing list