All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2: Searching for the rune stone. . .
Date: Wed, 10 Sep 2003 01:31:25 +0000	[thread overview]
Message-ID: <marc-lartc-106315756504991@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106315642704232@msgid-missing>

Brian Capouch wrote:
> I'm reading the LARTC HOWTO, and it talks about iproute2.
> 
> It doesn't talk about--at least the first one I found with 
> google--whether or not this program is still in development. When I go 
> to the .ru site that I find when looking for it the latest version I 
> find there is from January 2002.
> 
> Is that really the latest there is?

That's  good question, I was asking myself the same thing yesterday
when I was trying to compile it for the 2.6 kernel.

iproute2 includes kernel headers, which the 2.6 kernel doesn't like and
spits out warnings, which are treated as errors in our dev environment.




-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer  email:     damion@snapgear.com
SnapGear ---                           ph:         +61 7 3435 2809
  | Custom Embedded Solutions          fax:         +61 7 3891 3630
  | and Security Appliances            web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-09-10  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  1:12 [LARTC] iproute2: Searching for the rune stone. . Brian Capouch
2003-09-10  1:31 ` Damion de Soto [this message]
2003-09-10  3:07 ` Dancer Vesperman

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=marc-lartc-106315756504991@msgid-missing \
    --to=damion@snapgear.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.