From: Mariusz Mazur <mmazur@kernel.pl>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: iproute2 and kernel headers
Date: Tue, 3 Aug 2004 19:14:40 +0200 [thread overview]
Message-ID: <200408031914.40751.mmazur@kernel.pl> (raw)
In-Reply-To: <20040803083142.5a4ccaad@dell_ss3.pdx.osdl.net>
On wtorek 03 sierpień 2004 17:31, Stephen Hemminger wrote:
> > > I am willing to put some headers (not all) in with the user level
> > > code, provided they are copies since they I can easily update. I don't
> > > want to get into keeping an edited set of headers in sync.
> >
> > Aren't linux-libc-headers (*) sufficient?
> >
> > * - http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
>
> The theory of that is good, but in practice it would make the problem
> worse. What iproute2 wants is to have the same kernel data structures as
> the latest kernel. It is awkward enough making sure to get them from the
> correct kernel sources, but doing it from a different package would make
> updating and keeping everything current worse.
This message was forwarded to me (I'm the llh maintainer). Llh is being
updated by generating a diff between incremental kernel releases, fixing that
diff and applying it to the last version of llh. I do have scripts to check
wether such an update doesn't break any headers. There is a slight
possibility that such an update might omit some crucial changes, but (at
least when it comes to network headers) co-developers of my distribution
(PLD) will most likely detect that allmost instantly and notify me what's
wrong (in such a case I will release a fixed version of llh asap).
Since removing all those glibc/linux-headers workarounds from
iproute2/iptables was quite a pain for me I would really like to see building
against llh at least as an option available from 'configure'.
(In case you're wondering - yes, we've been building all the linux network
userland stuff against llh for about 8 months now without any problems...
quite the opposite actually)
--
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again
next prev parent reply other threads:[~2004-08-03 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 22:38 iproute2 and kernel headers Stephen Hemminger
2004-08-02 23:04 ` David S. Miller
2004-08-03 7:55 ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-03 21:21 ` David S. Miller
2004-08-03 0:14 ` Tomasz Torcz
2004-08-03 15:31 ` Stephen Hemminger
2004-08-03 17:14 ` Mariusz Mazur [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 0:50 Jean Tourrilhes
2004-08-06 16:39 ` Stephen Hemminger
2004-08-07 0:07 ` Jean Tourrilhes
2004-08-07 14:04 ` jamal
2004-08-08 9:38 ` Mariusz Mazur
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=200408031914.40751.mmazur@kernel.pl \
--to=mmazur@kernel.pl \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).