public inbox for linux-msdos@vger.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: Tue, 15 Jun 2004 21:35:29 +0400	[thread overview]
Message-ID: <40CF3361.5050605@aknet.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0406142127530.593@hani.compact.bogus>

Hello.

R.L. Horn wrote:
>> You erased and symlinked /usr/include/linux on your own.
> I did no such thing.  As I've explained before, I DON'T USE A
> DISTRIBUTION.
What you said before was only
"I don't run a distribution kernel...".
Most of us do not run a distribution kernel.
And as for "I don't use a distribution" - I
don't think I understand what do you mean by
that. LFS?

> Perhaps I'm a bit behind the times, but my argument is
> still valid.  The kernel developers aren't hearing about bugs (and I'm
> talking about gross compile errors here, not nitpicky stuff about
Apparently you haven't even looked into an
URL I (and other people) pointed you to :( 

> structures and unions) because the distributors are fixing them on their
> own and not bothering to tell the kernel guys.  The <sys/pci.h>/
If you at least made a quick glance at an URL,
you'll probably notice that it was the quote
from Linus, and he himself doesn't want people
to ever include the kernel headers and don't
want glibc maintainers to symlink the
/usr/include/linux to /usr/src because that no
longer work and not going to work ever again.
Now you say distributors are not bothering to
tell the kernel guys? Sigh... Please RTFM.

> <linux/pci.h> thing was fixed months ago...but the bug is still there in
> kernel 2.6.6.
Kernel headers are fine. Their only purpose
is to compile with the kernel, and for that they
suit very well. If someone thinks he can include
the kernel headers everywhere, ignoring whatever
comes with the glibc, it is another problem. If
the same person doesn't even bother to read the
documents that were pointed to him, that's also
a completely different problem.

> Now, let's get off this topic and talk about dosemu, ok?
Right, such a discussion leads us nowhere.
Go ahead an fill the bug report for kernel
as you intended to do before. The best thing
you'll hear is "don't include the kernel headers
into your program", but since that makes no
sense to you, go ahead and try. Maybe that
will even work, who knows...


  reply	other threads:[~2004-06-15 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 10:45 bcc dpmi ver1.2.0 Stas Sergeev
2004-06-15  3:26 ` R.L. Horn
2004-06-15 17:35   ` Stas Sergeev [this message]
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=40CF3361.5050605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox