public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
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:36:17 -0800	[thread overview]
Message-ID: <20050712203618.61541a42.tonyb@sysdev.org> (raw)
In-Reply-To: <42D48EDF.2090501@aknet.ru>

On Wed, 13 Jul 2005 07:47:43 +0400
Stas Sergeev <stsp@aknet.ru> wrote:

> to beleive it really uses a symlink.
> I remember Patrick Volkerding claimed
> in that very list that Slackware doesn't
> do this, but it looks like it was changed,
> or at least there is some bug...
> If some distro really does this, then
> rooting out this tendency among users
> is going to be really troublesome:(
> And some people claim that even
> installing the 2.6 headers from the
> slackware package still gives an error!
> And only that the 2.4 headers work
> properly.

After some googling I think I finally found the
correct linux-libc-headers (as they are now called).

 http://ep09.pld-linux.org/~mmazur/linux-libc-headers/

So I will splice these to my devel box and see if 1.3.2
works better with Linux 2.6.7  (It does not work too bad
with the 2.6.7 Kernel headers on 2.6.7, but not as well
as with the 2.4.31 headers and kernel 2.4.31)

The thing about Slackware is that they stuck with the 2.4
kernel for a long time, since very conservative.  It was
just now that they have an alternate 2.6 kernel in the
distribution and note that it is an alternate!  So I have
been using plain 2.6 kernel headers for 2.6 development
(dangerous, but most of time works for my purposes) but
now I am going to switch to the libc headers or "sanitized
kernel headers", since they seem robust enough and I am
now aware of them...

TonyB


  __      __  _     I N C.               http://www.sysdev.org
/ __|\\// __||  \  __   __          /         tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers


  reply	other threads:[~2005-07-13  4:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13  3:47 Dosemu 1.3.2 and linux 2.6.7 headers Stas Sergeev
2005-07-13  4:36 ` Hufnus [this message]
2005-07-13  7:53 ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14  4:03 Stas Sergeev
2005-07-14 10:01 ` Julius Schwartzenberg
2005-07-13 16:03 Stas Sergeev
2005-07-13 22:26 ` Julius Schwartzenberg
2005-07-13 15:19 Stas Sergeev
2005-07-12 20:07 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

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=20050712203618.61541a42.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