From: Andrew Brooks <arb@sat.dundee.ac.uk>
To: linux-msdos@vger.kernel.org
Subject: Re: Signaling dosemu application to kill itself from Linux
Date: Thu, 07 Apr 2005 17:35:06 +0100 [thread overview]
Message-ID: <4255613A.8E@sat.dundee.ac.uk> (raw)
In-Reply-To: 200504071206.47247.gene.heskett@verizon.net
Gene Heskett wrote:
>
> Then maybe the better question is: what bug does it address so that we
> may ascertain if we need it or not? And, is it against 1.3.1?
The patch was originally against 1.2.0 or 1.2.1 (I forget which). It
was not to fix a "bug" as such, rather that DOS time drifts in respect
to Linux/real time so the patch simply reads Linux time when a program
asks for DOS time. The web page describes the gory details:
http://sourceforge.net/tracker/index.php?func=detail&aid=1034800&group_id=49784&atid=457449
tonyb@thekrnl.sysdev.org wrote:
> We applied your patch in the hope it would fix a date/time corruption
> that happens after about 3wks of uptime.
We never found a "corruption", just a slow drift. To me "corruption"
means badly/randomly wrong and that would suggest a different cause.
Andrew
next prev parent reply other threads:[~2005-04-07 16:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 3:45 Signaling dosemu application to kill itself from Linux Stas Sergeev
2005-04-07 9:07 ` Andrew Brooks
2005-04-07 16:23 ` tonyb
2005-04-07 17:25 ` Gene Heskett
2005-04-07 16:06 ` Gene Heskett
2005-04-07 16:35 ` Andrew Brooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-10 8:40 Stas Sergeev
2005-04-08 3:55 Stas Sergeev
2005-04-10 0:32 ` tonyb
2005-04-07 17:59 Stas Sergeev
2005-04-07 17:50 Stas Sergeev
2005-04-08 2:14 ` tonyb
2005-04-07 3:38 Stas Sergeev
2005-04-07 6:12 ` tonyb
2005-04-06 16:06 Stas Sergeev
2005-04-06 22:16 ` tonyb
2005-04-07 0:47 ` Gene Heskett
2005-04-06 7:14 tonyb
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=4255613A.8E@sat.dundee.ac.uk \
--to=arb@sat.dundee.ac.uk \
--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.