From: Julius Schwartzenberg <julius@zgod.cjb.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Dosemu 1.3.2 and linux 2.6.7 headers
Date: Thu, 14 Jul 2005 00:26:24 +0200 [thread overview]
Message-ID: <42D59510.9080003@zgod.cjb.net> (raw)
In-Reply-To: <42D53B62.4040001@aknet.ru>
Stas Sergeev wrote:
> those:( So the original suggestion
> still stays - using the slackware
> package of the 2.4 headers will work
> the best:(
Yes. I think the thing is (I've also had this myself), that when
updating a kernel on Slackware, many people just download all the tgz
files from the directory with the new kernel and install them all.
The problem with this is that the headers package is put in the same
directory as the others and people also get the new headers that way.
Making sure that you do not get the new header package instead of doing
just *.tgz when downloading and installing lets Dosemu compile & run
without any problems. The kernel header package that originally came
with the version of Slackware I was using would always solve the
problems for me.
Julius
next prev parent reply other threads:[~2005-07-13 22:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 16:03 Dosemu 1.3.2 and linux 2.6.7 headers Stas Sergeev
2005-07-13 22:26 ` Julius Schwartzenberg [this message]
-- 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 15:19 Stas Sergeev
2005-07-13 3:47 Stas Sergeev
2005-07-13 4:36 ` Hufnus
2005-07-13 7:53 ` Bart Oldeman
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=42D59510.9080003@zgod.cjb.net \
--to=julius@zgod.cjb.net \
--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