All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lee <splee@plexio.com>
To: Bart Oldeman <Bart.Oldeman@bristol.ac.uk>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]
Date: 29 Aug 2002 12:27:37 -0700	[thread overview]
Message-ID: <1030649258.19139.179.camel@ralph.plexio.private> (raw)
In-Reply-To: <Pine.GSO.4.05.10208291935190.27437-100000@sh.enm.bris.ac.uk>

On Thu, 2002-08-29 at 11:54, Bart Oldeman wrote:
> FreeDOS kernels before ~2026 did not translate
> --------D-215C-------------------------------
> INT 21 - DOS 3.0+ - "FLOCK" - RECORD LOCKING
> into
> --------N-2F110A-----------------------------
> INT 2F CU - NETWORK REDIRECTOR (DOS 4.0+) - LOCK/UNLOCK REGION OF FILE
> 
> That was the problem - the redirector interface is a relatively recent
> addition to FreeDOS. DR-DOS should not have this bug.
> 
> I suspect that the way that DOSEMU tries to implement DOS locking
> techniques is not compatible with mandatory locking on the Samba Unix
> side.
Thanks for explaining the complexities. A few more questions:

1. Does that mean Sergey's hack to mfs.c is not a permanent solution?
I've made the changes but am waiting for my Foxpro users to test it.

2. Is using smbmount to access the Foxpro files from Dosemu a valid way
to get around the locking problem? I suspect it will be slower but
anything else?

Thanks again.
Stephen



  reply	other threads:[~2002-08-29 19:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 15:04 [Fwd: Re: Samba and kernel oplocks - Smbmount] Oscar A. Valdez
2002-08-29 16:30 ` Stephen Lee
2002-08-29 18:20   ` Oscar A. Valdez
2002-08-29 18:41     ` Stephen Lee
2002-08-29 18:54       ` Bart Oldeman
2002-08-29 19:27         ` Stephen Lee [this message]
2002-08-29 20:46         ` Oscar A. Valdez
2002-08-29 18:58       ` Oscar A. Valdez

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=1030649258.19139.179.camel@ralph.plexio.private \
    --to=splee@plexio.com \
    --cc=Bart.Oldeman@bristol.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.