From: Sergey Suleymanov <solt@eatpbank.ru>
To: Linux-MSDOS Mailing list <linux-msdos@vger.kernel.org>
Subject: Re: [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again))
Date: 11 Feb 2003 11:37:37 +0300 [thread overview]
Message-ID: <87d6lzyzzi.fsf@boo.eatpbank.ru> (raw)
In-Reply-To: Pine.LNX.4.44.0302101502580.2215-100000@euler.math.ohio-state.edu
>>>>> Bart Oldeman writes:
Bart> But Windows locking and Linux locking techniques are
Bart> incompatible so translating them through smbfs transforms
Bart> information.
Do you know how Samba server's _posix_ locking consist with
Dosemu's one? I mean, is samba's mapping SMB locks to posix
locks compatible enough to dosemu's emulation?
--
Sergey Suleymanov
next prev parent reply other threads:[~2003-02-11 8:37 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
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 [this message]
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=87d6lzyzzi.fsf@boo.eatpbank.ru \
--to=solt@eatpbank.ru \
--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