From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Underwood Subject: Re: are there any limitations to use drive c on nfs volumes? Date: Sat, 2 Oct 2004 22:42:30 -0500 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <20041003034230.GA12437@dbz.icequake.net> References: <200409241157.21654.Christian.Fischer@fischundfischer.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Return-path: Content-Disposition: inline In-Reply-To: <200409241157.21654.Christian.Fischer@fischundfischer.com> List-Id: To: linux-msdos@vger.kernel.org --SUOF0GtieIMvvwua Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Late reply. I mount drives onto my AFS home directory and it works fine. I wouldn't recommend multitasking from an AFS mount though, because AFS doesn't support record locking (which most DOS network apps assume the presence of) .... On Fri, Sep 24, 2004 at 11:57:21AM +0200, Christian Fischer wrote: > Hi there. >=20 > I've moved my local homes to server based homes mounted via autofs. > I'm running an foxpro application. This application starts but it hangs o= n=20 > touching the database. Strace told me that the ressource is temporary=20 > unavailiable and at statup of strace it tolds me > "SHAREing doesn't work on drive C: (probably NFS volume?)" >=20 > I'm running dosemu 1.2.0.0 on Linux version 2.6.7-gentoo-r11. > Please don't ask me why my dos app isn't on my local file system. Well, I= =20 > confirm that the local file system is the better place for apps than an n= fs=20 > volume. This was the first test and i had planned to do the the move to t= he=20 > local filesystem for later. >=20 > Regards > Christian=20 > --=20 --=20 Ryan Underwood, --SUOF0GtieIMvvwua Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBX3UlIonHnh+67jkRAqmfAJ9MoarEOl2MPGOz6B1W3DkoDLI4TACcChQB 4g4ZM+Va+6OTBVDkVD5d99s= =Ts4P -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua--