From: "Mads Martin Jørgensen" <mmj@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: /usr/src/linux/Documentation/networking/ifenslave.c
Date: Wed, 16 Jul 2003 14:59:10 +0200 [thread overview]
Message-ID: <20030716125910.GB10817@suse.de> (raw)
In-Reply-To: <20030716054255.1922d299.davem@redhat.com>
* David S. Miller <davem@redhat.com> [Jul 16. 2003 14:52]:
> This whole anti-kernel-headers-in-userspace thing is a
> total shamans dance and not founded in reality.
Urgs.
> Quick, answer this as fast as you can, where in the glibc headers can
> you get at the PFKEY and XFRM_NETLINK interface definitions to
> configure IPSEC stuff in the kernel?
>
> BZZT, time is up, and I know you have no answer :-)
:-)
> That is why all of this is rediculious.
Problem is some of these includes are different on different archs, and
causes the thing to miscompile. How to fix that then?
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
next prev parent reply other threads:[~2003-07-16 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 9:23 /usr/src/linux/Documentation/networking/ifenslave.c Mads Martin Jørgensen
2003-07-16 12:42 ` /usr/src/linux/Documentation/networking/ifenslave.c David S. Miller
2003-07-16 12:59 ` Mads Martin Jørgensen [this message]
2003-07-16 13:10 ` /usr/src/linux/Documentation/networking/ifenslave.c David S. Miller
2003-07-16 13:35 ` /usr/src/linux/Documentation/networking/ifenslave.c Mads Martin Jørgensen
2003-07-16 13:28 ` /usr/src/linux/Documentation/networking/ifenslave.c David S. Miller
2003-07-16 14:12 ` /usr/src/linux/Documentation/networking/ifenslave.c Jeff Garzik
2003-07-16 14:14 ` /usr/src/linux/Documentation/networking/ifenslave.c David S. Miller
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=20030716125910.GB10817@suse.de \
--to=mmj@suse.de \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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).