> actually, you can change the default behavior of dmesg to see all of the boot
> messages if you so desire... man dmesg for more nfo.
That's nonsense. From the man page:
NAME
dmesg - print or control the kernel ring buffer
Not all boot-time messages are kernel messages; indeed, most of the useful
ones aren't. For example, dmesg won't display any of these:
Mar 7 18:35:49 possum lpd: lpd startup succeeded
Mar 7 18:35:50 possum autofs: Starting automounter:
Mar 7 18:35:50 possum rc: Starting autofs succeeded
Mar 7 18:35:50 possum keytable: Loading keymap: Loading system font:
Mar 7 18:35:50 possum rc: Starting keytable succeeded
As others have observed, even if it did, logging in is hardly the epitome
of convenience. If the messages stayed there, I could read the 'failed'
message and any accompanying information in a couple of seconds. In
contrast, logging in and checking wastes a couple of minutes.
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
