From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: vmodem / virtual comport segfault
Date: Sun, 13 Apr 2003 14:50:49 +0400 [thread overview]
Message-ID: <3E994109.80506@yahoo.com> (raw)
Hello.
Pawel Szymczykowski wrote:
> Stock usermode 1.0.2.1 binaries
> I came across this problem in the archives, amd the only suggestion I
> could find was to upgrade the linux kernel.
That's because the suggestion to
upgrade your dosemu was repeated
so many times, people are tired to
repeat this all over again:)
It is useless to report bugs for
the 1.0.2.x versions here. This
version is out of support.
> ./dosemu: line 386: 4308 Segmentation fault $BINARY $MAINARGS
> "${par[@]}" 2>$LOG
> For us, using the 2.5 unstable series of
> kernel is not possible - but surely there must be some way of getting things
> to work under 2.4 current?
Sure. 2.4.20 is known to be rather
dosemu-friendly (quite a lot of work
was done in that area).
> P.S. Also, I tried the development version of dosemu, but couldn't get
> it to work (even without vmodem - it had a configuration file error of
> some sort).. though thanks to the archives, I think I know what I need
> to do to make it work now.. guess I will have to give it a try later..
Right. The cure is to upgrade to 1.1.4.15.
> though would really prefer to stick with stable versions if at all
> possible.
There are several definitions of the word
"stable". You may expect it to be a synonym
of the word "reliable", however it is not
the case here. It is "stable" because the
code base was not changing for years (bugs
were not get fixed etc). So in case you need
a reliability you have to upgrade.
next reply other threads:[~2003-04-13 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 10:50 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-13 5:16 vmodem / virtual comport segfault Pawel Szymczykowski
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=3E994109.80506@yahoo.com \
--to=stssppnn@yahoo.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