FC4 boot.log no longer being written to

• To: "For users of Fedora Core releases" <fedora-list@xxxxxxxxxx>
• Subject: FC4 boot.log no longer being written to
• From: "Ben Roberts" <ben@xxxxxxxxxxxx>
• Date: Sat, 16 Jul 2005 20:59:16 +0100
• Importance: Normal
• In-reply-to: <v04020a0cbeff139400ca@[192.168.123.162]>
• List-archive: <https://www.redhat.com/archives/fedora-list>
• List-help: <mailto:[email protected]?subject=help>
• List-id: For users of Fedora Core releases <fedora-list.redhat.com>
• List-post: <mailto:[email protected]>
• List-subscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=subscribe>
• List-unsubscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=unsubscribe>
• Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>

I've just upgraded a fresh FC3 installation to FC4 using yum. It
appears that /var/log/boot.log is no longer being written to at
boot time.

I've searched google and found some sparse references to the fact
that FC4 no longer writes to boot.log, but no conclusive answers.

Does anyone know what's going on here ? If boot.log is no longer
being used, where are boot time messages now stored in FC4 ??

Thanks

Ben Roberts
ben@xxxxxxxxxxxx

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.16/50 - Release Date:
15/07/2005

• Follow-Ups:
  • Re: FC4 boot.log no longer being written to
    • From: Jim Cornette

• References:
  • Re: Max Files Per Directory
    • From: Tony Nelson

• Prev by Date: Re: spamassassin report problem
• Next by Date: Re: spamassassin report problem
• Previous by thread: Re: Max Files Per Directory
• Next by thread: Re: FC4 boot.log no longer being written to
• Index(es):
  • Date
  • Thread