Empty bool.log

Gene Heskett gene.heskett at verizon.net
Wed Nov 15 23:41:47 UTC 2006

On Wednesday 15 November 2006 17:03, Anne Wilson wrote:
>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.
I agree, but thats how its been since Red Hat 5-ish times.

Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

More information about the users mailing list