From: Przemyslaw Czerpak <druzus@acn.waw.pl>
To: linux-msdos@vger.kernel.org
Subject: Re: Who knows what was changed in 1.1.3.3 or 1.1.3.4 about file locking?
Date: Sun, 10 Nov 2002 19:55:44 +0100 [thread overview]
Message-ID: <20021110195544.A1899@189-moc-1.acn.waw.pl> (raw)
In-Reply-To: <87n0ohen0s.fsf@eatpbank.ru>; from solt@eatpbank.ru on Sun, Nov 10, 2002 at 01:29:07PM +0300
On Sun, 10 Nov 2002, Sergey Suleymanov wrote:
> Bart> Attached is a quick&dirty "proof of concept" 64-bit file offset
> Bart> patch. Of course it will need to be changed to be compatible
> Bart> with older libc's and kernels.
> I hope this will be compile-time option. I'm using mars_nwe
> for file sharing and it use regular offsets for locking.
mars clears the highest bit in locks offset - see nwshare.c file.
I've added 64bit locking to mars but I haven't public the patch
so far because I haven't time to change the method of file share mode
emulation. I want to make it samba compatible. If anyone on the list
is similar with samba code and can help it will be nice.
Last week Bart's sent patch for full 32bit locks in DOSEMU so I think it's
time to realize my changes to mars to make it compatible.
I will do that to the end of next week.
best regards,
Przemek
next prev parent reply other threads:[~2002-11-10 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1036654059.16614.24.camel@localhost.localdomain>
2002-11-07 23:00 ` Who knows what was changed in 1.1.3.3 or 1.1.3.4 about file locking? Bart Oldeman
2002-11-08 7:09 ` Michal Samek
2002-11-08 9:45 ` Michal Samek
2002-11-10 10:29 ` Sergey Suleymanov
2002-11-10 17:47 ` Bart Oldeman
2002-11-11 6:01 ` Sergey Suleymanov
2002-11-10 18:55 ` Przemyslaw Czerpak [this message]
2002-11-14 13:37 ` Michal Samek
2002-11-14 14:12 ` Michal Samek
2002-11-02 21:42 Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 14:55 Michal Samek
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=20021110195544.A1899@189-moc-1.acn.waw.pl \
--to=druzus@acn.waw.pl \
--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