All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: bcc dpmi ver1.2.0
Date: Mon, 14 Jun 2004 14:45:31 +0400	[thread overview]
Message-ID: <40CD81CB.1030600@aknet.ru> (raw)

Hello.

R.L. Horn wrote:
> The kernel.  <linux/*> are kernel headers, not part of glibc, but the
> distributors appear to have muddied the waters considerably.
No, this is not the decision of distributors
any more.

> 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
Linux-related FAQs contains the precise
explanation for this:
http://www.linuxmafia.com/faq/Kernel/usr-src-linux-symlink.html

> If nothing else, it occults kernel header problems, which might explain 
> in part why they've been so long getting fixed.
AFAIK everything is fixed. There was the
problem with debian distro, but not any more
I think.
You erased and symlinked /usr/include/linux
on your own. Why do you expect the programs
to still compile or work correctly? I think
the above URL explains why you should not.


             reply	other threads:[~2004-06-14 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 10:45 Stas Sergeev [this message]
2004-06-15  3:26 ` bcc dpmi ver1.2.0 R.L. Horn
2004-06-15 17:35   ` Stas Sergeev
2004-06-16  3:20     ` R.L. Horn
  -- strict thread matches above, loose matches on Subject: below --
2004-06-14 11:05 Stas Sergeev
2004-06-13 22:58 Stas Sergeev
2004-06-14  6:00 ` R.L. Horn
2004-06-14 10:27   ` Ryan Underwood
2004-06-15  3:00     ` James B. Hiller
2004-06-15  3:31       ` Patrick J. Volkerding
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=40CD81CB.1030600@aknet.ru \
    --to=stsp@aknet.ru \
    --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 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.