From: Uwe Feldtmann <uwe@microshare.com.au>
To: cristi.mitrana@gmail.com
Cc: linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: Distributions questions
Date: Tue, 20 Sep 2005 16:08:48 +1000 [thread overview]
Message-ID: <1127196529.8624.4.camel@localhost.localdomain> (raw)
In-Reply-To: <f1de940b05091910205e688d74@mail.gmail.com>
Do you know what the packages are called for Debian?
Or would I be better of compiling from source?
I am running Ubuntu 5.04 and would like to use dosemu/freedos but they
don't appear in the package list.
Thanks in advance.
On Mon, 2005-09-19 at 20:20 +0300, Cristi Mitrana wrote:
> On 9/19/05, Stas Sergeev <stsp@aknet.ru> wrote:
> > Hello.
> >
> > UNIREA Sannicolau Mare wrote:
> > > I.e. how can we make latest version of xdosemu to work on RedHat6,
> > > RedHat7 and RedHat8?
> > IIRC RedHat6 and 7 has the 2.2 linux kernels.
>
> RedHat 7.1 had 2.4.2 right out of the box.
>
> > Dosemu should work on those, but there may be
> > a few problems, mostly with the DPMI apps.
> > And apart from bugs and missing features, the
> > DPMI on 2.2 was IIRC very, very slow.
> > Additionally, IIRC RedHat7 had the broken gcc
> > that used to miscompile dosemu, but you can use
> > a binary distribution.
>
> They fixed that with several updates, but that's a long time ago :).
> RH 7.0 was the culprit.
>
> > On RedHat8 it should work almost normally, but
> > the kernel upgrade is still recommended.
>
> > > Or what older xdosemu versions work on such systems?
> > Older dosemus is a darkness. Unless your tasks
> > for it are really trivial and not mission-critical
> > (eg you can tolerate the frequent crashes, and
> > you don't afraid of a security holes), you almost
> > certainly don't want to have an older dosemu on any
> > of your machines.
>
> In my experience, debian provides a cleaner and simpler
> default installation, about 200mb for a basic setup (this includes networking).
> Also, 2.6 is included and also dosemu is up to date.
> I have several 'old' computers with the current debian stable distro and
> they work without a hitch (without Xwindows, I have to say).
> If networking is a good option then you can install something like LTSP
> (I know for a fact that some people using LTSP are running DOS apps
> via dosemu for a living :) and have a more poweful server which
> handles all the load and processing needs of the clients. All
> (x)dosemu instances
> cand be run over the net and the workstation clients could be as dumb as an P1.
> This can assure that you can run a modern distro with all the updates
> on the server
> and you can upgrade in one step the application used. Depending on the number
> of workstations and their distribution this could be a nice option.
>
> hth,
next prev parent reply other threads:[~2005-09-20 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 16:28 Distributions questions Stas Sergeev
2005-09-19 17:20 ` Cristi Mitrana
2005-09-20 6:08 ` Uwe Feldtmann [this message]
2005-09-20 6:51 ` Damyan Ivanov
2005-09-19 18:10 ` REAL " Cristi Mitrana
2005-09-20 6:03 ` Damyan Ivanov
-- strict thread matches above, loose matches on Subject: below --
2005-09-19 12:08 UNIREA Sannicolau Mare
2005-09-20 0:29 ` Justin Zygmont
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=1127196529.8624.4.camel@localhost.localdomain \
--to=uwe@microshare.com.au \
--cc=cristi.mitrana@gmail.com \
--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