From: Ashok N N <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 with new kernel
Date: Sat, 23 Nov 2002 08:41:37 +0000 [thread overview]
Message-ID: <marc-lartc-103804095927405@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103788251315201@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 21 November 2002 09:20 am, Tomas Bonnedahl wrote:
> well, does it matter _which_ kernel include files you include in the
makefile for iproute2?
> (or, does the term "correct" mean the old or just a bootable/normal kernel?)
>
> -tomas
>
> On Thu, Nov 21, 2002 at 11:02:02AM -0300, Esteban Ribicic wrote:
> > from iproute2 tarball
> >
> > How to compile this.
> > --------------------
> > 1. Look at start of Makefile and set correct values for:
> > KERNEL_INCLUDE should point to correct linux kernel include directory.
> >
> > blah blah blah
> >
> > greets!
> >
> >
> > On Thu, 2002-11-21 at 10:47, Stef Coene wrote:
> > > On Thursday 21 November 2002 13:40, Tomas Bonnedahl wrote:
> > > > hello, is it necessary to recompile iproute2 when you add a new
kernel, and
> > > > hence move the link /usr/src/linux to point on a different kernel?
> > > I'm not sure, but iproute uses some kernel files, so I think you better
> > > recompile.
> > >
> > > Stef
> > >
hi,
what about the iproute2 installed as a package (say RPM) and then later the
kernel was compiled for newer kernel versions. I keep compiling the kernel as
newer versions become available, but had installed iproute2 when I installed
Redhat 7.3 and have not yet upgraded iproute2 which works fine even after
kernel compilations. so compiling the iproute2 after a kernel compile would
be for safety??
thanks,
ashok
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE93z9DRhXpVty0Ty4RAoSsAJ4rEjQOjnO6PKXTgIhGRR4HHUumLACeL90N
qgapHdgcYAQNNkqbyk0J7X4=GrKN
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-11-23 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 12:40 [LARTC] iproute2 with new kernel Tomas Bonnedahl
2002-11-21 13:47 ` Stef Coene
2002-11-21 14:02 ` Esteban Ribicic
2002-11-21 14:20 ` Tomas Bonnedahl
2002-11-23 8:41 ` Ashok N N [this message]
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-103804095927405@msgid-missing \
--to=nalkunda@cse.msu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox