From: steve <steve@steve-ss.com>
To: simo <idra@samba.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Jeremy Allison <jra@samba.org>,
linux-nfs@vger.kernel.org,
"samba-technical@lists.samba.org"
<samba-technical@lists.samba.org>,
Ondrej Valousek <webserv@s3group.com>
Subject: Re: NFSv4 ACLs
Date: Sat, 21 Apr 2012 13:34:40 +0200 [thread overview]
Message-ID: <4F929B50.1020407@steve-ss.com> (raw)
In-Reply-To: <1334972084.2492.722.camel@pico.li.ssimo.org>
On 21/04/12 03:34, simo wrote:
> On Fri, 2012-04-20 at 18:08 -0400, J. Bruce Fields wrote:
>> On Fri, Apr 20, 2012 at 02:59:45PM -0700, Jeremy Allison wrote:
>>> On Fri, Apr 20, 2012 at 05:26:27PM -0400, J. Bruce Fields wrote:
>>>> On Fri, Apr 20, 2012 at 11:55:53AM -0700, Jeremy Allison wrote:
>>>>> On Fri, Apr 20, 2012 at 12:04:02PM +0200, Ondrej Valousek wrote:
>>>>>> Hi List,
>>>>>>
>
>> (By the way, is reexporting nfs with samba really going to work well
>> anyway?)
>
> Not really, it is generally unsupported, except for read only shares. It
> will work in most of the simple cases for writing .. until it breaks :)
>
Hi
That's worrying.
We been rw'ing nfs/samba for years. Maybe we're the only ones. nfs3 for
our Linux clients and samba for the rest. Same shared data. Only Posix
acl's though. Maybe that's the simple bit?
Cheers,
Steve
next prev parent reply other threads:[~2012-04-21 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F913492.8000402@s3group.cz>
[not found] ` <20120420185553.GB32622@samba2>
2012-04-20 21:26 ` NFSv4 ACLs J. Bruce Fields
2012-04-20 21:59 ` Jeremy Allison
2012-04-20 22:08 ` J. Bruce Fields
2012-04-21 1:34 ` simo
2012-04-21 11:34 ` steve [this message]
2012-04-21 23:57 ` Andrew Bartlett
2012-04-23 14:49 ` steve
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=4F929B50.1020407@steve-ss.com \
--to=steve@steve-ss.com \
--cc=bfields@fieldses.org \
--cc=idra@samba.org \
--cc=jra@samba.org \
--cc=linux-nfs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=webserv@s3group.com \
/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;
as well as URLs for NNTP newsgroup(s).