From: Aitor Santamaria Merino <aitor.sm@wanadoo.es>
To: linux-msdos@vger.kernel.org
Subject: File contents not being updated on DOSEmu crash
Date: Tue, 25 Feb 2003 13:19:08 +0000 [thread overview]
Message-ID: <3E5B6D4C.1050407@wanadoo.es> (raw)
Hi,
I am using DOSEmu 1.0.2.1 with FreeDOS, with kernel 2028, and I have
noticed the following unexpected behaviour:
I have experienced a full crash of DOSEmu when using the FreeDOS Editor,
which cause I am trying to determine. I have noticed that the file that
I had been editing wasn't updated within the LinuxFS, nor contents
neither modification date of the file were updated.
The same happens if you simply press Ctrl+C in the shell where you run
DOSEmu from.
The file tested has ALL the linux permissions, and is visible through [C:].
Is there any way to avoid any caching, or is this a bug?
Aitor
PS: Is there a way to report bugs other than in sourceforge? Is
sourceforge bug reporting system active?
next reply other threads:[~2003-02-25 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 13:19 Aitor Santamaria Merino [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 13:26 File contents not being updated on DOSEmu crash Aitor Santamaria Merino
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=3E5B6D4C.1050407@wanadoo.es \
--to=aitor.sm@wanadoo.es \
--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