public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Anderson Pereira Ataides <anderson.pa@persogo.com.br>
To: Lista dosemu <linux-msdos@vger.kernel.org>
Subject: Re: dosemu and CLIPPER locks (again) (fwd)
Date: Wed, 5 Feb 2003 10:24:14 -0200	[thread overview]
Message-ID: <03020510241400.01004@anderson.cdc.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0302050114040.11388-100000@enm-bo-lt.localdomain>

Em Qua 05 Fev 2003 04:40, Bart Oldeman escreveu:
> But what you can check is in the following scenario:
> suppose the Linux box is a samba server and the Windows client issues a
> lock. Now can a DOSEMU which runs on that samba server see that lock?
Yes if I mount a samba share instead of opening file locally. Ok it is not 
the right thing to do. It should be able to open file locally and see windows 
locks, but if I could not make it work by the right way, I think it is a 
solution for now.

Opening file using mounted samba share, Windows can see dosemu locks and 
dosemu can see Windows locks. The problem is that the same application in 
dosemu is working different. I am using DBU (do you know it) to open the same 
file in dosemu and Windows ant this is what happens:

1. Open in dosem first
When I open DBU in Windows it can see file is exclusive opened in dosemu and 
show only the name of dbf file, but do not show its fields and can not open 
it to see contents of file. That is expected to happen.

2. Open file in Windows first
When I open DBU in dosemu it gives an error message: "File corruption 
detected" and abort. Ok, that means dosem can see file is already opened but 
the problem is the way it is dealing with it. DBU should work the same way as 
in Windows.

> ...Now as you can
> guess that would be quite a bit of work and I certainly will not be
> doing this any time soon (though I would happily accept patches of
> course).
And I am not the one to make this patch :-(. I do not have knowledgement 
enough in C programming language for this. If you or our dosemu partners 
could only make DBU have the same behaviour in dosemu and Windows I will be 
happy. If it happens, that means I can finally send Windows to .......

Off topic: if my english is bad and is not making problems clear enough 
please tell me and I'll try to write better next time.

[]s
Anderson Pereira Ataides

  reply	other threads:[~2003-02-05 12:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SOL.4.44.0302050103010.25172-100000@math.ohio-state.edu>
2003-02-05  6:40 ` dosemu and CLIPPER locks (again) (fwd) Bart Oldeman
2003-02-05 12:24   ` Anderson Pereira Ataides [this message]
2003-02-06  6:56     ` [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again)) Bart Oldeman
2003-02-07 12:06       ` Michal Samek
2003-02-10 15:42       ` Gregor Ibic
2003-02-10 18:07         ` Bart Oldeman
2003-02-10 18:45           ` Gregor Ibic
2003-02-10 18:57             ` Bart Oldeman
2003-02-10 19:04               ` Gregor Ibic
2003-02-10 19:14                 ` Bart Oldeman
2003-02-10 19:36                   ` Gregor Ibic
2003-02-10 19:49                     ` Bart Oldeman
2003-02-10 20:00                       ` Gregor Ibic
2003-02-10 20:06                         ` Bart Oldeman
2003-02-11  8:37                           ` Sergey Suleymanov
2003-02-11 17:11                             ` Bart Oldeman
2003-02-10 21:28                     ` WARNING: smbfs and locking (was RE: [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again)))) Bart Oldeman
2003-02-10 23:17                       ` WARNING: smbfs and locking -- POSIX v. CIFS locking, and how DOS doesn't do CIFS locking (bad things man) Bryan J. Smith
2003-02-11  0:31                         ` Bart Oldeman
2003-02-11 13:00                           ` WARNING: smbfs and locking -- Mega-oversimplification Bryan J. Smith
2003-02-11 12:07                       ` WARNING: smbfs and locking Anderson Pereira Ataides
2003-02-11 13:01                         ` Reinhard Karcher

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=03020510241400.01004@anderson.cdc.net \
    --to=anderson.pa@persogo.com.br \
    --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