[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4935A692.3050300@hp.com>
Date: Tue, 02 Dec 2008 16:20:18 -0500
From: jim owens <jowens@...com>
To: Steve French <smfrench@...il.com>
CC: Jamie Lokier <jamie@...reable.org>,
Andreas Dilger <adilger@....com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"linux-cifs-client@...ts.samba.org"
<linux-cifs-client@...ts.samba.org>
Subject: Re: Support for applications which need NFS or CIFS "share_deny"
flags on open
Steve French wrote:
> On Tue, Dec 2, 2008 at 2:06 PM, Jamie Lokier <jamie@...reable.org> wrote:
>> The bit I find interesting is that other CIFS clients are said to
>> implement these flags. If that means real unixes, maybe they've
>> worked out a sensible way to handle them?
>
> I thought that MacOS uses these flags (not just Windows, and of course
> older clients too OS/2, DOS etc.).
The title of their proposal was "client"... as in not the local
filesystem, but the impression of what wine really wanted is
for local linux filesystems to implement these non-posix behaviors
so "wine apps can run just like on windows" on the local machine.
Thus the strong objection from everyone doing local filesystems.
Passing exclusive DENYREAD DENYWRITE DENYDELETE network
protocol flags from a linux client to a remote server
is an entirely different and IMO acceptible thing.
And AFAIK on unix the only local support would be by doing
a client-on-server loopback, where the server implements
these modes as best it can and you are only protected
against wine apps that are also inside the "share drive".
jim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists