Messages in this thread | | | Date | 13 Aug 2000 12:13:00 +0200 | From | (Kai Henningsen) | Subject | Re: Re(2): NTFS-like streams? |
| |
tdk@thelbane.com (Timothy Knox) wrote on 12.08.00 in <20000813001947.21502@shalmaneser.thelbane.com>:
> Somewhere on Shadow Earth, Alexander Viro wrote: > > >1001st time: icons are _NOT_ file properties. > >They depend on user. Get over it, already... > > Actually, in (for example) Mac OS, icons *ARE* file properties (if a > custom icon is assigned to a given filesystem object).
And in the default case, icons are application properties that the Finder extracts from the application into the Finder database. (The same way it extracts the custom icon, incidentally, except it doesn't copy that one into its database.)
Note that custom icons are a very late MacOS feature. The Finder database, OTOH, is older than hierarchical filesystems. And it still works essentially the same way as in the beginning.
And to get back to Unix permission problems with this concept:
1. Yes, MacOS *does* have the concepts of owner, group, and permissions. It just restricts those to network filesystems (and other networking stuff).
2. When you don't have permissions to change a MacOS file (be it network permissions or simply a read-only flag), guess what?
*You cannot manipulate the custom icon for that file*.
Why would Linux need something different?
MfG Kai
- 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/
| |