> The file server is Linux. However, there are also some Windows machines
> who want to say a word. And they all(Dosemu and Windows clients) must work
> together well.
Well you could use NFS to export to Linux clients and Samba to export to
Windows clients for the same directory.
> > The locking
> There is a fundamental problem in that DOS locking is incompatible with
> UNIX locking. Now if you use smbfs and samba you add two extra layers
> where things can go wrong. This makes it complex. If the file server is
> not running Windows then it's probably better to use NFS instead.
The file s
On Wed, 2002-11-06 at 12:58, Siim Vahtre wrote:
>
> How much ways dosemu actually knows to lock one file?
>
> As I mentioned already, I need quite special way of locking files (paradox
> databases). It must be able to lock one certain record, that is being
> changed, and leave every other record
On Wed, 6 Nov 2002, Siim Vahtre wrote:
> How much ways dosemu actually knows to lock one file?
just a few days ago I wrote down the way how DOSEMU handles file locking
now (since 1.1.3.3) here:
http://marc.theaimsgroup.com/?l=linux-msdos&m=103627393213889&w=2
see src/dosext/mfs/mfs.c for the imp
How much ways dosemu actually knows to lock one file?
As I mentioned already, I need quite special way of locking files (paradox
databases). It must be able to lock one certain record, that is being
changed, and leave every other record readable/writeable.
Can dosemu handle it in any way?
(I'm n
> > Try it with the latest patches (1.1.3.7) at
>
> It works!
*sigh*
It doesn't work :)
The samba has shared everything well. Windows clients get done their
locking correctly. However, when dosemu clients come, they don't care
about locking any more. Even if they are exclusive locks that should
f
> Try it with the latest patches (1.1.3.7) at
It works!
I now just hope that this testing version is 'stable' enough.
Thank you!
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/m
On Wed, 2002-11-06 at 06:20, Siim Vahtre wrote:
> > OK, there ARE 2 locking problems. One with a file lock and another with
> > a record lock. Try to search archives. Try 1.1.3 version, for some
> > people it seems to work (not for me and for some clipper users i
> > think). But what do you try w
> OK, there ARE 2 locking problems. One with a file lock and another with
> a record lock. Try to search archives. Try 1.1.3 version, for some
> people it seems to work (not for me and for some clipper users i
> think). But what do you try with test.txt is maybe ok, when I open for
> ex. with NC
Hi Bart,
I've compiled 1.1.3 to change the way cpu cicles are released when asking time
of day (I'm using dosemu to run a clipper program which asks what time is it
when it has nothing to do, this is clipper runtime standard bahaviour) to
release less time, but there is a problem, right now dosemu
On St, 2002-11-06 at 12:55, Siim Vahtre wrote:
> > For example, when I open (read-only!) some file (let's say "L:\test.txt"
> > that is actually "/mnt/samba/test.txt") then I can't open the same file
> > with another dosemu. (It says "Access denied.")
OK, there ARE 2 locking problems. One with a f
> For example, when I open (read-only!) some file (let's say "L:\test.txt"
> that is actually "/mnt/samba/test.txt") then I can't open the same file
> with another dosemu. (It says "Access denied.")
One thing more:
It does not matter HOW I configure the samba. Even if there is no locking
whatsoev
Hi.
I need to use some dosemu clients(running old database programs made in
turbo pascal) that read/write paradox databases on linux samba server.
However, it seems that samba and dosemu doesn't share their thoughts about
file locking.
For example, when I open (read-only!) some file (let's say "
13 matches
Mail list logo
