From: Stas Sergeev <stssppnn@yahoo.com>
To: DOSEMU users mailing list <linux-msdos@vger.kernel.org>
Subject: Re: Dosemu 1.1.99.1 segfaults
Date: Thu, 30 Oct 2003 22:53:18 +0300 [thread overview]
Message-ID: <3FA16C2E.5020207@yahoo.com> (raw)
Hello.
Ged Haywood wrote:
>> What kernel are you using? Some kind of 2.6?
> 2.6.0-test5
Dumb question actually, it was written
in the beginning of the log...
>> You have to upgrade your dosemu in that case.
> Oh dear. Upgrade to what?
To CVS HEAD just as usual. It is known
to be a good practice to update to CVS
HEAD before reporting any bugs. That
really helps and not only with dosemu.
> Does it say that in the docs?
> If so, where? I haven't found anything about kernel versions
> in the docs
But dosemu tells you every time you
start it:
---
Please test against a recent version before reporting bugs and problems.
---
Most people don't understand the importance
of that note. But probably now it must be
adjusted to reflect the fact that there is a
CVS in use.
> If you will please tell me where or how to find the fix, I'll cease
> troubling you...
CVS repository of dosemu is the place where
the fixes are now lingering.
next reply other threads:[~2003-10-30 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 19:53 Stas Sergeev [this message]
2003-10-30 20:59 ` Dosemu 1.1.99.1 segfaults Ged Haywood
2003-10-30 21:12 ` Bart Oldeman
2003-10-30 21:30 ` Ged Haywood
2003-10-31 16:02 ` Ged Haywood
-- strict thread matches above, loose matches on Subject: below --
2003-11-01 18:18 Stas Sergeev
2003-11-02 17:58 ` Ged Haywood
2003-10-30 18:15 Stas Sergeev
2003-10-30 18:58 ` Ged Haywood
2003-10-30 19:07 ` Bart Oldeman
2003-10-29 18:49 Stas Sergeev
2003-10-29 21:18 ` Ged Haywood
2003-10-28 16:06 Ged Haywood
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=3FA16C2E.5020207@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.