Hi;
I was looking at my boot.log this morning and found confusing symbols that distract from its clarity.
E.g. ... emounting root filesystem in read-write mode: [60G[[0;32m OK [0;39m] Mounting local filesystems: [60G[[0;32m OK [0;39m] Enabling local filesystem quotas: [60G[[0;32m OK [0;39m] Enabling /etc/fstab swaps: [60G[[0;32m OK [0;39m] Entering non-interactive startup Applying Intel CPU microcode update: [60G[[0;32m OK [0;39m] ...
I gather, [60G[[0;32m has something to do with Tab [ and [0;39m] represents ]\n. The problem probably has something to do with locale and/or basic fonts installed.
Does anybody know how I should configure whatever to get the boot.log to print properly ?
None of my other logs have this problem.
On 09/18/2009 08:00 AM, William Case wrote:
Hi;
I was looking at my boot.log this morning and found confusing symbols that distract from its clarity.
E.g. ... emounting root filesystem in read-write mode: [60G[[0;32m OK [0;39m] Mounting local filesystems: [60G[[0;32m OK [0;39m] Enabling local filesystem quotas: [60G[[0;32m OK [0;39m] Enabling /etc/fstab swaps: [60G[[0;32m OK [0;39m] Entering non-interactive startup Applying Intel CPU microcode update: [60G[[0;32m OK [0;39m] ...
I gather, [60G[[0;32m has something to do with Tab [ and [0;39m] represents ]\n. The problem probably has something to do with locale and/or basic fonts installed.
Does anybody know how I should configure whatever to get the boot.log to print properly ?
None of my other logs have this problem.
I believe those are the ascii codes to change the colors. more or cat the file instead of editing it. :)
Hi;
On Fri, 2009-09-18 at 08:22 -0600, Phil Meyer wrote:
On 09/18/2009 08:00 AM, William Case wrote:
Hi;
I was looking at my boot.log this morning and found confusing symbols that distract from its clarity.
E.g. ... emounting root filesystem in read-write mode: [60G[[0;32m OK [0;39m] Mounting local filesystems: [60G[[0;32m OK [0;39m] Enabling local filesystem quotas: [60G[[0;32m OK [0;39m] Enabling /etc/fstab swaps: [60G[[0;32m OK [0;39m] Entering non-interactive startup Applying Intel CPU microcode update: [60G[[0;32m OK [0;39m] ...
I believe those are the ascii codes to change the colors. more or cat the file instead of editing it. :)
Right you are! Interesting. 'cat' and 'more' /var/log/boot.log prints a proper colourized file to stdout. However 'less' and 'gnome-system-log' only show me the ASCII colour codes without actually colourizing.
Of course it's not a big problem, but I would like to fix it. Any suggestions?
Add while I am at it, the boot.log gives me this message: ... Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 513: 1326 Segmentation fault "$@" [FAILED] ...
Yet nothing seems wrong with my graphics once I am logged in.
William Case wrote:
I believe those are the ascii codes to change the colors. more or cat the file instead of editing it. :)
Right you are! Interesting. 'cat' and 'more' /var/log/boot.log prints a proper colourized file to stdout. However 'less' and 'gnome-system-log' only show me the ASCII colour codes without actually colourizing.
Is you use less -R /var/log/boot.log the color escape sequences should be rendered properly. I've got no clue about gnome-system-log.
Of course it's not a big problem, but I would like to fix it. Any suggestions?
Add while I am at it, the boot.log gives me this message: ... Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 513: 1326 Segmentation fault "$@" [FAILED]
It may be that nvidia-config-display is crashing. From a very quick look, that seems to come from /etc/init.d/nvidia. Maybe you can poke around there and see which command is failing. I think it's probably:
action $"Enabling the $name driver:" $exec enable
where name=nvidia and exec="/usr/sbin/$name-config-display"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 18 Sep 2009, Phil Meyer wrote:
Date: Fri, 18 Sep 2009 08:22:50 -0600 From: Phil Meyer pmeyer@themeyerfarm.com To: "Community assistance, encouragement, and advice for using Fedora." fedora-list@redhat.com User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=unavailable version=3.2.3 Subject: Re: Boot.log question/fix ?
On 09/18/2009 08:00 AM, William Case wrote:
Hi;
I was looking at my boot.log this morning and found confusing symbols that distract from its clarity.
E.g. ... emounting root filesystem in read-write mode: [60G[[0;32m OK [0;39m] Mounting local filesystems: [60G[[0;32m OK [0;39m] Enabling local filesystem quotas: [60G[[0;32m OK [0;39m] Enabling /etc/fstab swaps: [60G[[0;32m OK [0;39m] Entering non-interactive startup Applying Intel CPU microcode update: [60G[[0;32m OK [0;39m] ...
I gather, [60G[[0;32m has something to do with Tab [ and [0;39m] represents ]\n. The problem probably has something to do with locale and/or basic fonts installed.
Does anybody know how I should configure whatever to get the boot.log to print properly ?
None of my other logs have this problem.
I believe those are the ascii codes to change the colors. more or cat the file instead of editing it. :)
Or you cand disable colors in boot process. Just change BOOTUP variable to something else in /etc/sysconfig/init (grep for BOOTUP in /etc/rc.d/rc.sysinit and /etc/rc.d/init.d/functions to see why).
Gabriel
- --
// Gabriel VLASIU // // OpenGPG-KeyID : 0xE684206E // OpenGPG-Fingerprint: 0C3D 9F8B 725D E243 CB3C 8428 796A DB1F E684 206E // OpenGPG-URL : http://www.vlasiu.net/public.key