[ On Wednesday, June 26, 2002 at 12:03:38 (-0400), David Maxwell wrote: ]
> Subject: Re: location of dmesg.boot
>
> The _logged_ messages also go to /var/log/messages

Indeed, but so does a lot of noise unrelated to the kernel, and that
file tends to rotate even more often and thus boot messages are more
likely to get lost if that's where you expect to find them.  I
personally find /var/log/messages almost useless.  Either I want
everything for a recent event, in which case it's got to be in my
"*.debug /var/log/debug" files, or I want the longer history of a
selective facility, such as my /var/log/kern.

(I assume you highlight "logged" because in syslogd output the timestamp
is prefixed, which IMNSHO is also a _good_ thing!  ;-)

> but as dmesg.boot is
> revelant only to the current uptime/boot-session of the system, /var/run
> seems quite appropriate.

That's what a careful but isolated-from-the-real-world analysis would
suggest, but I know we're far from alone in thinking /var/log is more
appropriate for the real-world (/var/run is kinda like /usr/libexec to
me -- only for use by other programs, not humans).

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>