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: Dosemu 1.3.2 and linux 2.6.7 headers
Date: Wed, 13 Jul 2005 07:47:43 +0400	[thread overview]
Message-ID: <42D48EDF.2090501@aknet.ru> (raw)

Bart Oldeman wrote:
> This is not its default symbolic link. You must have created it 
> yourself, manually.
Hi Bart, actually I've seen such
a problem with Slackware in many
different places, so I am starting
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.

Maybe add the proper headers to the
dosemu source tree as we did before?
We can convince people to use the
proper headers by answering the same
question over and over again, but we
really can't change the distribution.


             reply	other threads:[~2005-07-13  3:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13  3:47 Stas Sergeev [this message]
2005-07-13  4:36 ` Dosemu 1.3.2 and linux 2.6.7 headers Hufnus
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=42D48EDF.2090501@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