From: "David S. Miller" <davem@redhat.com>
To: "Mads Martin Jørgensen" <mmj@suse.de>
Cc: netdev@oss.sgi.com
Subject: Re: /usr/src/linux/Documentation/networking/ifenslave.c
Date: Wed, 16 Jul 2003 05:42:55 -0700 [thread overview]
Message-ID: <20030716054255.1922d299.davem@redhat.com> (raw)
In-Reply-To: <20030716092354.GC24077@suse.de>
On Wed, 16 Jul 2003 11:23:54 +0200
Mads Martin Jørgensen <mmj@suse.de> wrote:
> $SUBJECT is a userspace tool, but includes kernel headers. This small
> obvious patch against 2.6.0-test1 should fix it.
This patch is absolutely senseless, you eliminate two such includes
> -#include <linux/if.h>
> -#include <linux/if_arp.h>
> +#include <net/if_arp.h>
but three more still remain.
> #include <linux/if_ether.h>
> #include <linux/if_bonding.h>
> #include <linux/sockios.h>
This whole anti-kernel-headers-in-userspace thing is a
total shamans dance and not founded in reality.
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.
next prev parent reply other threads:[~2003-07-16 12:42 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 ` David S. Miller [this message]
2003-07-16 12:59 ` /usr/src/linux/Documentation/networking/ifenslave.c Mads Martin Jørgensen
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=20030716054255.1922d299.davem@redhat.com \
--to=davem@redhat.com \
--cc=mmj@suse.de \
--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 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.