Tracy R Reed wrote:
[EMAIL PROTECTED] wrote:
Correct me if I'm wrong but it seems that dmesg only shows an
undefined subset
of all boot messages. Furthermore, it seems /var/log/messages misses
a few
also right?
dmesg only shows kernel messages. /var/log/messages shows only what
other daemons put through syslog. Stuff that just gets output straight
to console is lost as soon as it scrolls off the top of the screen afaik.
True. Most systems seem to configured to erase the screen when the login
program, usually mingetty, is called. In order to see that information,
I change my /etc/inittab file (portion shown) like this:
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty --noclear tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
The --noclear option prevents mingetty from clearing the screen. Then
when the system finishes booting and is sitting at the login prompt you
can use SHIFT-PageUp to scroll back up the screen.
Beware that Ubuntu Hardy 8.04 and Fedora 9 are moving to something
called Upchuck^H^H^H^H^H start which is supposed to be a "better" init
system. I find it to be a POS that takes what was a simple, centralized,
easy to understand file and now splits it up and scatters it all over
the place.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
