cutting down on boot messages

From: Jurriaan (thunder7@xs4all.nl)
Date: Fri Jul 25 2003 - 14:57:52 EST


If I boot my system, there are copious messages.

For example:

md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdc6 ...
md: adding hdc6 ...
md: hdc5 has different UUID to hdc6
md: hdc3 has different UUID to hdc6
md: hdc1 has different UUID to hdc6
md: adding hda6 ...
md: hda5 has different UUID to hdc6
md: hda3 has different UUID to hdc6
md: hda1 has different UUID to hdc6
md: hdi2 has different UUID to hdc6
md: hdi1 has different UUID to hdc6
md: hde2 has different UUID to hdc6
md: hde1 has different UUID to hdc6
md: created md5
md: bind<hda6>
md: bind<hdc6>
md: running: <hdc6><hda6>
md5: setting max_sectors to 128, segment boundary to 32767
raid1: raid set md5 active with 2 out of 2 mirrors

Now these messages are often uninteresting - but sometimes they are.
So just deleting them, or requiring a recompile or reboot is not good
enough.
Also, I noted that these messages were almost always grouped together.

Suppose these messages were removed from the normal output, but instead
stored in a buffer in the kernel.

Then, you could do

dmesg.raid

to get at the raid-messages,

and

dmesg.raid --clear

to clear the buffer.

The same goes for other groups of messages, like the whole APIC/IRQ
routing block, ide messages, usb messages etc.

Would this keep the interesting information, but cut down on the amount
of messages? I'm now at 22k of dmesg, including raid, usb, apic etc, for
a single CPU system.

I'd be interested in everyone's opinion on this!

Jurriaan

-- 
REAL LIFE MANAGEMENT 'DILBERT QUOTATIONS':
11: One day my Boss asked me to submit a status report to him concerning a
    project I was working on. I asked him if tomorrow would be soon
    enough. He said "If I wanted it tomorrow, I would have waited until
    tomorrow to ask for it!" (New business manager, Hallmark Greeting
    Cards.)
Debian (Unstable) GNU/Linux 2.6.0-test1-ac2 4112 bogomips load av: 1.00 1.00 1.00
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:26 EST