From: Jens Axboe <axboe@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
schilling@fokus.fraunhofer.de, linux-kernel@vger.kernel.org
Subject: Re: Kernel includefile bug not fixed after a year :-(
Date: Tue, 30 Sep 2003 14:28:32 +0200 [thread overview]
Message-ID: <20030930122832.GO2908@suse.de> (raw)
In-Reply-To: <20030930052337.444fdac4.davem@redhat.com>
On Tue, Sep 30 2003, David S. Miller wrote:
> On Tue, 30 Sep 2003 14:12:06 +0200
> Andreas Steinmetz <ast@domdv.de> wrote:
>
> > Then please tell me why PPPIOCNEWUNIT is only defined in linux/if_ppp.h
> > and not net/if_ppp.h which is still true for glibc-2.3.2. And please
> > don't tell me to ask the glibc folks. There are inconsistencies between
> > kernel headers and userland headers which force the inclusion of kernel
> > headers in userland applications.
>
> Indeed, and equally someone tell me where all the IPSEC socket
> interface defines are in glibc? It doesn't matter which tree
> you check it won't be there.
Did you notify them of the addition?
> Even if one is of the opinion that nobody should be including the
> kernel headers, you must fully realize that as a matter of
> practicality people absolutely must do this to use many kernel
> interfaces to their full extent.
>
> Suggest changes to fix the problems, but just saying "don't include
> kernel header in your user apps, NYAH NYAH NYAH!" does not help
> anyone at all.
Well then change that to 'if you include kernel headers from your user
apps, be prepared to pick fix the breakage'.
Surely the kernel doesn't move at such an accelerated pace that it's
impossible to keep kernel headers uptodate.
--
Jens Axboe
next prev parent reply other threads:[~2003-09-30 12:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 11:44 Kernel includefile bug not fixed after a year :-( Joerg Schilling
2003-09-30 11:54 ` Jens Axboe
2003-09-30 12:12 ` Andreas Steinmetz
2003-09-30 12:21 ` Jens Axboe
2003-09-30 12:26 ` Andreas Steinmetz
2003-09-30 12:30 ` Jens Axboe
2003-09-30 12:32 ` David S. Miller
2003-09-30 12:40 ` Jens Axboe
2003-09-30 12:39 ` David S. Miller
2003-09-30 12:23 ` David S. Miller
2003-09-30 12:28 ` Jens Axboe [this message]
2003-09-30 12:34 ` David S. Miller
2003-09-30 12:42 ` Jens Axboe
2003-09-30 19:09 ` Erik Andersen
2003-10-01 8:48 ` Paul Rolland
2003-10-01 8:55 ` Arjan van de Ven
2003-10-01 17:49 ` Erik Andersen
2003-09-30 16:10 ` Sam Ravnborg
2003-10-01 6:39 ` David S. Miller
2003-10-02 6:42 ` Eric W. Biederman
2003-09-30 19:04 ` Erik Andersen
2003-09-30 12:25 ` Nick Piggin
2003-09-30 19:00 ` Erik Andersen
2003-10-01 8:47 ` Paul Rolland
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 1:05 Albert Cahalan
2003-09-30 13:26 Joerg Schilling
2003-09-30 12:52 Joerg Schilling
2003-09-30 12:37 Joerg Schilling
2003-09-30 13:21 ` Tomas Szepe
2003-09-30 11:57 Joerg Schilling
2003-09-30 12:06 ` Jens Axboe
2003-09-30 12:28 ` David S. Miller
2003-09-30 12:38 ` Jens Axboe
2003-09-30 14:41 ` Krzysztof Halasa
2003-10-10 6:36 ` Sandy Harris
2003-09-30 10:28 Joerg Schilling
2003-09-30 11:05 ` Jens Axboe
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=20030930122832.GO2908@suse.de \
--to=axboe@suse.de \
--cc=ast@domdv.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schilling@fokus.fraunhofer.de \
/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