From: "R.L. Horn" <lists@eastcheap.org>
To: linux-msdos@vger.kernel.org
Subject: Re: bcc dpmi ver1.2.0
Date: Mon, 14 Jun 2004 01:00:44 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0406140037320.969@hani.compact.bogus> (raw)
In-Reply-To: <40CCDC14.9040802@aknet.ru>
On Mon, 14 Jun 2004, Stas Sergeev wrote:
> Are you sure you are upgrading glibc with patches?
The kernel. <linux/*> are kernel headers, not part of glibc, but the
distributors appear to have muddied the waters considerably. (So, what
else is new?)
> diff -u /usr/include/linux/pci.h
> /usr/src/linux-2.6.6/include/linux/pci.h before filling such a report.
My /usr/include/linux is a symlink into the kernel source.
It sounds as though the distributors are maintaining multiple, possibly
disparate, copies of the kernel headers. Whether this is to ease
installations without kernel sources or because 2.6 is so thoroughly
buggered up I don't know, but it seems like a horrendously bad idea to me.
If nothing else, it occults kernel header problems, which might explain in
part why they've been so long getting fixed.
At any rate, this is getting kind of far afield.
next prev parent reply other threads:[~2004-06-14 6:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 22:58 bcc dpmi ver1.2.0 Stas Sergeev
2004-06-14 6:00 ` R.L. Horn [this message]
2004-06-14 10:27 ` Ryan Underwood
2004-06-15 3:00 ` James B. Hiller
2004-06-15 3:31 ` Patrick J. Volkerding
-- strict thread matches above, loose matches on Subject: below --
2004-06-14 11:05 Stas Sergeev
2004-06-14 10:45 Stas Sergeev
2004-06-15 3:26 ` R.L. Horn
2004-06-15 17:35 ` Stas Sergeev
2004-06-16 3:20 ` R.L. Horn
2004-06-12 8:29 Stas Sergeev
2004-06-13 3:55 ` R.L. Horn
2004-06-13 19:11 ` Bart Oldeman
2004-06-13 21:47 ` R.L. Horn
2004-06-11 19:54 David Stevenson
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=Pine.LNX.4.58.0406140037320.969@hani.compact.bogus \
--to=lists@eastcheap.org \
--cc=linux-msdos@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