From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-rc1-mm1
Date: 2 Mar 2004 13:52:03 GMT [thread overview]
Message-ID: <c223i3$o1s$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20040229222415.A32236@infradead.org
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
In article <20040229222415.A32236@infradead.org>,
Christoph Hellwig <hch@infradead.org> wrote:
| On Sun, Feb 29, 2004 at 02:06:17PM -0800, Andrew Morton wrote:
| > +scsi-external-build-fix.patch
| >
| > Fix scsi.h for inclusion by userspace apps - it used to work, so...
|
| This has been rejected on linux-scsi a few times. Don't use include/scsi/
| from the kerneltree - there's alredy a /usr/include/scsi from glibc anyway,
| so the situation is even more clear thæn the general you should not include
| kernel headers thing.
But the glibc headers don't describe 2.6, do they? Don't work with 2.6?
We went around with this for cdrecord unless I misread which headers are
involved.
It's not reasonable to expect people to rebuild glibc for each kernel,
even if it is "the right thing to do" in some purist sense. It would be
better to have something like user header in the kernel for just the
interface, and have the kernel include start by pulling in the user
header and then adding things the user doesn't need.
Changes between kernel series are always unpleasant during the time when
people have to boot back and forth, we should think about a better way
to do this for 2.7.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2004-03-02 13:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 22:06 2.6.4-rc1-mm1 Andrew Morton
2004-02-29 22:24 ` 2.6.4-rc1-mm1 Christoph Hellwig
2004-02-29 22:31 ` 2.6.4-rc1-mm1 Andrew Morton
2004-03-02 13:52 ` bill davidsen [this message]
2004-03-01 1:02 ` 2.6.4-rc1-mm1 Nick Piggin
2004-03-01 1:14 ` 2.6.4-rc1-mm1 Andrew Morton
2004-03-01 1:30 ` 2.6.4-rc1-mm1 Nick Piggin
2004-03-01 1:45 ` 2.6.4-rc1-mm1 Nick Piggin
2004-03-01 2:05 ` 2.6.4-rc1-mm1 Andrew Morton
2004-03-01 1:10 ` 2.6.4-rc1-mm1: multiple definitions of `debug' Adrian Bunk
2004-03-01 1:41 ` Andrew Morton
2004-03-01 17:49 ` Torrey Hoffman
2004-03-01 1:39 ` 2.6.4-rc1-mm1 Marc-Christian Petersen
2004-03-01 1:46 ` 2.6.4-rc1-mm1 Marc-Christian Petersen
2004-03-01 11:26 ` posix message queues, was 2.6.4-rc1-mm1 bert hubert
2004-03-01 14:27 ` Krzysztof Benedyczak
2004-03-01 16:41 ` 2.6.4-rc1-mm1 Prakash K. Cheemplavam
2004-03-02 13:38 ` 2.6.4-rc1-mm1 Prakash K. Cheemplavam
2004-03-02 20:45 ` 2.6.4-rc1-mm1, as scheduler causes higher idle temp? Prakash K. Cheemplavam
2004-03-02 21:11 ` Andrew Morton
2004-03-02 21:39 ` Prakash K. Cheemplavam
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 0:20 2.6.4-rc1-mm1 Pedro Larroy
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='c223i3$o1s$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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