From: Phil Pishioneri on
On 7/22/10 2:59 PM, Trond Myklebust wrote:
> The fact remains that most of us would be hard pressed to name an
> application

Microsoft Office?

> that requires you to share the same dataset to both
> Windows/CIFS and posix NFS clients.

NFS client: Mac OS X (NFSv3, since v4 on it is still alpha *cough*).

> tends to discourage mixing the two environments.

Or is "discourage" not strong enough term to describe that we shouldn't
be doing this?

-Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jan Engelhardt on

On Friday 2010-07-30 23:22, utz lehmann wrote:
>On Thu, 2010-07-22 at 09:40 -0700, Linus Torvalds wrote:
>> But the fact is, th Unix ctime semantics are insane and largely
>> useless. There's a damn good reason almost nobody uses ctime under
>> unix.
>>
>> So what I'm suggesting is that we have a flag - either per-process or
>> per-mount - that just says "use windows semantics for ctime".
>
>When abusing an existing time stamp use atime not ctime please.
>ctime has it's uses. atime was just a mistake and is nearly useless.

MUAs make use of atime.

>And with noatime we already have creation time semantics for atime.

noatime was a late afterthought, and because it can interfere with
some programs, relatime came along too.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jan Engelhardt on

On Friday 2010-08-13 19:54, Jeremy Allison wrote:
>On Fri, Aug 13, 2010 at 08:54:32AM -0400, J. Bruce Fields wrote:
>> On Sun, Aug 08, 2010 at 06:05:01AM -0700, Jeremy Allison wrote:
>> > We don't need to ape Windows in everything.
>> > The coming ACL disaster will show that (we will go from an ACL
>> > model that is slightly too complex to use, to one that is impossibly
>> > complex to use :-).
>>
>> Care to elaborate?
>
>POSIX ACLs -> RichACLs (NT-style). Not criticising Andreas here,
>people are asking for this. But Windows ACLs are a nightmare
>beyond human comprehension :-). In the "too complex to be
>usable" camp.

Well, for one, ACLs in NT can be recursive IIRC. You can't say that of Linux
ACLs - instead you have to setfacl -R and setfacl -Rd to give one user access
to a directory and all its subdirs including future new inodes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/