From: Christian Fischer <Christian.Fischer@fischundfischer.com>
To: dr.claudia.neumann@gmx.de
Cc: linux-msdos@vger.kernel.org
Subject: Re: are there any limitations to use drive c on nfs volumes?
Date: Fri, 24 Sep 2004 15:13:54 +0200 [thread overview]
Message-ID: <200409241513.55174.Christian.Fischer@fischundfischer.com> (raw)
In-Reply-To: <200409241414.29324.dr.claudia.neumann@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Friday 24 September 2004 14:14, Claudia Neumann wrote:
> Am Freitag, 24. September 2004 13:20 schrieben Sie:
> > I've moved the drives to the local filesystem, everything works fine.
> > If dosemu can't use nfs volumes why my app thinks that the database is in
> > place? Normally the app tells me if no database is present.
>
> I am using dosemu and nfs constantly. It works fine. But I don't link it to
> drive c. I put a link from /home/user/.dosemu/drives/d to the mountpoint of
> the nfs volume and boot it as drive d:.
> Perhaps it is a problem with user rights of the mounted nfs volume?
No Claudia, it isn't, and there was no link to drive c.
Drive c was (now it is local)
~/.dosemu/drives/c
an home is an autofs mounted nfs volume.
Now drive c is
/opt/dosemu/drives/c
and everything works fine. I suppose that dosemu ist using for drive c the
physical (or a part of) file system layer, not an virtual like nfs (i hope
that's right, i don't know enough about that).
Thanks for the information that it works for you on drive d, that will be
helpful.
christian
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2004-09-24 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 9:57 are there any limitations to use drive c on nfs volumes? Christian Fischer
2004-09-24 11:20 ` Christian Fischer
2004-09-24 12:14 ` Claudia Neumann
2004-09-24 13:13 ` Christian Fischer [this message]
2004-09-25 8:27 ` Christian Fischer
2004-09-26 7:27 ` Claudia Neumann
2004-10-03 3:42 ` Ryan Underwood
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=200409241513.55174.Christian.Fischer@fischundfischer.com \
--to=christian.fischer@fischundfischer.com \
--cc=dr.claudia.neumann@gmx.de \
--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