Fedora Users — Re: Empty bool.log

-------- Original Message --------
Subject: Empty boot.log
From: Anne Wilson <cannewilson@xxxxxxxxxxxxx>
To: For users of Fedora <fedora-list@xxxxxxxxxx>
Date: 11/15/2006 03:03 PM

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

I did look there but it does not seem to have what was shown during the boot process. During boot I see a module load error and I know it has "cpufreq" in it. I wanted to see the exact text of the message but it does not appear in either dmsg or messages. I can probably figure out the modprobe problem without it but it would be easier if it was actually recorded some place.

begin:vcard
fn:Paul Lemmons
n:Lemmons;Paul
org:Tucson Medical Center;Information Services
adr:;;5301 E. Grant Road;Tucson;AZ;85712;USA
email;internet:paul.lemmons@xxxxxxxxx
title:Lead Systems Software Engineer
tel;work:520-324-1034
tel;fax:520-324-1206
tel;pager:paullem@xxxxxxxxx
tel;home:520-722-2642
tel;cell:520-603-7392
x-mozilla-html:TRUE
url:http://www.tmcaz.com
version:2.1
end:vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature