From: Erik Andersen <andersen@codepoet.org>
To: Paul Rolland <rol@as2917.net>
Cc: "'Jens Axboe'" <axboe@suse.de>,
"'David S. Miller'" <davem@redhat.com>,
"'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: Wed, 1 Oct 2003 11:49:06 -0600 [thread overview]
Message-ID: <20031001174906.GA12587@codepoet.org> (raw)
In-Reply-To: <022901c387f8$d35c3320$4300a8c0@witbe>
On Wed Oct 01, 2003 at 10:48:45AM +0200, Paul Rolland wrote:
> Hello,
>
> > A classic recent example is iproute, which uses kernel headers
> > all over the place. It compiled with earlier 2.4.x kernels, but
> > it no longer compiles 2.4.22. I've not bothered to try and fix
> > it, but if it included its own set of sanitized kernel headers,
> > it would not have had a problem.
>
> And if some IOCTLs were changed in between, in the kernel and
> kernel headers ?
> You end up with an application that you can compile, but doesn't
> behave as expected ? What a progress :-(
People who change ioctl numbers needs their kneecaps broken.
Regardless, I didn't say I liked the current situation. I
just said that is the current officially sanctioned method
of dealing with it,
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2003-10-01 17:49 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
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 [this message]
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=20031001174906.GA12587@codepoet.org \
--to=andersen@codepoet.org \
--cc=ast@domdv.de \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
--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 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.