From: Hufnus <tonyb@thekrnl.sysdev.org>
To: linux-msdos@vger.kernel.org
Subject: Re: Dosemu 1.3.2 and linux 2.6.7 headers
Date: Tue, 12 Jul 2005 20:20:59 -0800 [thread overview]
Message-ID: <20050712202059.55a23a1f.tonyb@sysdev.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0507131339070.32156@enm-bo-lt.localnet>
On Wed, 13 Jul 2005 13:44:33 +1200 (NZST)
Bart Oldeman <bartoldeman@users.sourceforge.net> wrote:
> No, those are not the /usr/include/linux headers, the ones you are
> talking about are those in include/linux in the kernel source code.
>
> > Maybe the kernel guys will pick that change up, if it carries no
> > other implications ...
>
> they won't, as they know that include/linux headers are broken
> beyond repair for user space inclusion.
Thanks, I found the latest official linux-libc-headers at:
http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
TonyB
--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers
next prev parent reply other threads:[~2005-07-13 4:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 20:07 Dosemu 1.3.2 and linux 2.6.7 headers Hufnus
2005-07-12 20:21 ` Maciek Stopa
2005-07-12 20:49 ` Hufnus
2005-07-12 20:58 ` Maciek Stopa
2005-07-12 23:05 ` Hufnus
2005-07-12 23:35 ` Bart Oldeman
2005-07-12 23:43 ` Julius Schwartzenberg
2005-07-13 0:15 ` Hufnus
2005-07-13 1:44 ` Bart Oldeman
2005-07-13 4:20 ` Hufnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-13 3:47 Stas Sergeev
2005-07-13 4:36 ` Hufnus
2005-07-13 7:53 ` Bart Oldeman
2005-07-13 15:19 Stas Sergeev
2005-07-13 16:03 Stas Sergeev
2005-07-13 22:26 ` Julius Schwartzenberg
2005-07-14 4:03 Stas Sergeev
2005-07-14 10:01 ` Julius Schwartzenberg
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=20050712202059.55a23a1f.tonyb@sysdev.org \
--to=tonyb@thekrnl.sysdev.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