>> Funny, you can also do that by looking at the file magic, without any
>> kernel modification.
> I was expecting something like this, but in a depersonalized manner, the
>> > It's really no different than the ACL storage issue
>>
>> The ACL storage issue is much more difficult, because it involves
>> security.
> Well, not really. It's another set of disk data structures that's got to
> be manage by the kernel. I'm assuming that the complexity comes from
> what to do with the ACL data once a file is opened and actively used
> from what I've read.
>> I have used Macintoshes and I have dealt with the problems caused by
>> file forks. And I came to a different conclusion than you did. Perhaps
>> you should try to argue your point based on more facts and less on
>> authority.
> Uh, using a Macintosh is different than programming it, right ?
Yeah... Looks like Mac user can retain his brain while Mac programmer can not.
> Didn't I say Macintosh GUI programmer have different perspective on
> the subject and not general application users of the Mac ?
You can say anything but references to Mac authority will not help here.
> You seem to have not acknowledged that "Macintosh programmers", not
> users see this VERY clearly.
Looks like programming for Macintosh GUI just make deep and unrecoverable
damage to your brain. If something is really clear then you must be able
to describe gains with easy. Sorry, guys, just "Mac does it, so it must be
good" argument does not help here.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/