From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9f3897940708201036r1d877f55v38f7594f48774537@mail.gmail.com> Date: Mon, 20 Aug 2007 19:36:56 +0200 From: "=?UTF-8?Q?Pawe=C5=82_Lasek?=" To: alltom@gmail.com, "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Re: everything is a directory In-Reply-To: <326364c20708200434y575bc6bdq5504d096cd429c21@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46C5638A.9080507@proweb.co.uk> <1187377796.983193.153800@j4g2000prf.googlegroups.com> <8ccc8ba40708200200p4b924ea7t68600a639e36accd@mail.gmail.com> <326364c20708200434y575bc6bdq5504d096cd429c21@mail.gmail.com> Cc: Topicbox-Message-UUID: ad5a2b60-ead2-11e9-9d60-3106f5b1d025 On 8/20/07, Tom Lieber wrote: > On 8/20/07, Francisco J Ballesteros wrote: > If the problem is stuffing data into a file that was never meant to be > in the file, attributes are a solution. After all, you quote from jsnx > did say, "But where do the oddball intermediaries put their metadata? > ... [They] can't very well stuff album art into your .mp3 files" (or > something like that...). While I don't give a damn about files being directories, I pretty much like Extended Attributes or NTFS files (in NTFS, file is something different than in *nix-like FS or FAT). While I don't like stuffing "persistent" data into EA's (like album art data, icons or similar things), they are fairly useful from system daemon perspective. Since you want examples, I'll give those that I know: * in XFS, several tools use EA's to assign attributes like "DO NOT DUMP" or hierarchical file management data. This data *should* be discarded by normal tools (since cp is creating a new file, and mv only modifes directories but not i-node's EAs) and are of interest only to those system daemons * (IIRC) Beagle daemon uses extended attributes to track files that were scanned and are not modified - they contain part of it's detected metadata, hash and DB pointer * NTFS discards the Unix concept of a file entirely - what was shown before as trouble with Alternate Data Streams is in fact trouble of keeping backward compatibility (Internally, NT doesn't have drive letters or any of the DOS stuff). A File in NTFS is a MFT entry with a bunch of attributes. Those attributes have several types/names defined, like DATA for file contents, one for keeping filename (for which there are three namespaces: DOS8.3, Windows, POSIX), one for legacy DOS attributes (used by the official, backward compatible API), one for security data, and others used mostly by system daemons (Although NT5+ explorer uses one to hold various comments about files. Rarely used by people I think). I especially like the NTFS implementation, because it allows to use NTFS for most Operating Systems without modifying internal structure, while making it easy to add "compatibility layer" As for things that need to work with cp/mv/others, I suggest making better file formats or adding metadata in different file. It's not the smartest use of Extended Attributes/NTFS attributes :-) > -- > Tom Lieber > http://AllTom.com/ > -- Paul Lasek