From: "Hinderling, Anselm" <Anselm.Hinderling@RKES.DE>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: /sbin/route problem with 2.4.0test
Date: Thu, 30 Nov 2000 12:34:34 +0100 [thread overview]
Message-ID: <91571DF701C0D211B7CA00805F628DBE23358D@BER1_B01> (raw)
> -----Original Message-----
> From: Dries van Oosten [SMTP:D.vanOosten@phys.uu.nl]
> Sent: Thursday, November 30, 2000 12:17 PM
> To: linux-kernel@vger.kernel.org
> Subject: /sbin/route problem with 2.4.0test
>
> I have plowed my way trough the kernel-digest archives, but I couldn't
> find an answer, so sorry if it's old news.
> I have a machine running 2.4.0test8 and /sbin/route refuses to work. It
> only prints the table headers and then nothing happens. I can stop it with
> ctrl-c, but the actual routing table is not printed. I don't know much
> about the changes between 2.2 and 2.4, so I looked up the routing table
> struct in include/net/route.h. At first I thought the table remained the
> same, because they were the same version. One closer inspection I found
> that the entry inet_peer had been added to the rtable struct. Can this be
> the cause of my problem with the route utility?
> If so? What's the fix?
>
have you ever tried "/sbin/route -n" (or even --help ;-)?
> thanks for your patience,
> Dries van Oosten
>
>
>
>
anselm.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-30 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 11:34 Hinderling, Anselm [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-30 11:17 Dries van Oosten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91571DF701C0D211B7CA00805F628DBE23358D@BER1_B01 \
--to=anselm.hinderling@rkes.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®