1) dmesg only covers kernel messages. There are other messages
that get printed to the screen when the system starts up that
don't get shown by dmesg. To see these, I just hold down
<shift> and use <PAGE-UP> and <PAGE-DOWN> to scroll through
the messages. Probably not the most scientific approach, but
it works for me.
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
file has a line to add a route for local network traffic through
the loopback interface. As of Kernel 2.2.0, you need to have
a netmask on that line. Debian Slink is designed for 2.0.x
kernels which don't really need this parameter. I have mailed
the maintainers about this problem. Until this gets changed,
change the line:
route add -net 127.0.0.0
to:
route add -net 127.0.0.0 netmask 255.255.255.0 lo
Hope this helps,
Bryan
On 11-Oct-99 Bryan Scaringe wrote:
>
> ----- Begin Included Message -----
>
> From [EMAIL PROTECTED] Mon Feb 8 02:33 EST 1999
> Date: Mon, 08 Feb 1999 07:18:41 +0000
> From: Paul Rogers <[EMAIL PROTECTED]>
> X-Accept-Language: en,ja,ko
> MIME-Version: 1.0
> To: Linux Newbie <linux-newbie@vger.rutgers.edu>
> Subject: Start up Messages
> Content-Transfer-Encoding: 7bit
> X-Loop: [EMAIL PROTECTED]
> X-Orcpt: rfc822;linux-newbie-outgoing
>
> Dear All
>
> Can any one tell me how to review the output generated on startup? I
> know about DMesg but would like to see the messages from the point that
> dmesg stops. I'm sure I've read here that by pressing <??> before
> (after?) the initial logon I am able to view the various messages, but I
> can't remember what <??> is.
>
> Secondly can anyone tell me / point me in the direction of any info as
> to what the following startup message means?
>
> SIOCADDRT:invalid argument
>
>
> Many thanks in advance
>
>
> Paul
>
>
>
> ----- End Included Message -----
----- End Included Message -----
--------------End of forwarded message-------------------------
