Re: boot messages too fast to read.
In article <cistron.Pine.GSO.3.95.990824003731.24815B-100000@dvp.cs>,
Hwei Sheng TEOH <hsteoh@cs.toronto.edu> wrote:
>It seems that certain messages are not recorded by dmesg: such as isapnp
>messages. (I've never been able to see the board ID and "activated OK" message
>in dmesg -- only on the console.) Anybody can explain why??
Yes. There are 2 kind of messages: the ones originating from the kernel,
and the ones printed by applications to /dev/console. Only the first kind
is stored in a ring buffer by the kernel.
>I'd like to have
>dmesg record *every* bootup message, so that I don't have to avoid switching
>VC's right after bootup in order not to erase important messages that may not
>appear in dmesg.
Dmesg doesn't record anything. It's just a tool that reads /proc/kmsg
(which is an interface to the ring buffer of kernel messages).
Mike.
--
... somehow I have a feeling the hurting hasn't even begun yet
-- Bill, "The Terrible Thunderlizards"
Reply to: