From: Hans Reiser <reiser@namesys.com>
To: Narcoleptic Electron <narcoleptic_electron@yahoo.co.uk>
Cc: reiserfs-list@namesys.com, nikita@namesys.com
Subject: Re: Carrying Attributes too Far
Date: Thu, 18 Sep 2003 22:08:03 +0400 [thread overview]
Message-ID: <3F69F483.3030904@namesys.com> (raw)
In-Reply-To: <20030918171403.912.qmail@web60005.mail.yahoo.com>
I think you are probably right. Nikita?
Narcoleptic Electron wrote:
>I'm very new to ReiserFS, with only a shaky understanding, but here is my feedback:
>
>[alexander]
>Graphic.jpeg (a file)
>Graphic.jpeg.attributes (a directory)
>Graphic.jpeg.attributes/Author (a file)
>Graphic.jpeg.attributes/MIME (a file containing "image/jpeg")
>Graphic.jpeg.attributes/Thumbnails/Icon32x32.ico (a file)
>[/alexander]
>
>Suggestions:
>
>- Use my "..." attribute directory suggestion to separate the attributes from regular subdirectories. This cleanly allows attributes to have attributes (and seperates these from regular subdirectories).
>
>- Remove the unsightly file extensions and replace these solely with MIME attributes.
>
>- (Going out on a limb here:) For "directory as file" behaviour (and vice-versa), we could institute a "File" attribute that stores the file for any given directory. Thus, if any directory is specified in a file context (i.e. without the trailing slash), its "File" attribute file is returned. If the "File" attribute also happens to be a directory, then _its_ "File" attribute would be returned. And so on, until a file is returned (or some recursion limit is reached).
>
>Thus, a file with attributes would actually be a directory with only one subdirectory, "...", which houses the attributes (including "File"). Of course, this could all be pseudo and the file is still just a file.
>
>Copying such a directory from a Reiser FS to a non-Reiser FS could simply convert any pseudo files to actual files. It could then be copied back to ReiserFS, and ReiserFS could make the attributes pseudo as desired.
>
>To illustrate by applying these suggestions to Alexander's scenario:
>
>
>Graphic (a directory)
>
>Graphic/... (a directory containing attributes of the original "Graphic.jpeg" file)
>
>Graphic/.../File (the original "Graphic.jpeg" file)
>
>Graphic/.../Author (a file)
>
>Graphic/.../MIME (a file containing "image/jpeg")
>
>Graphic/.../Thumbnails/Icon32x32 (a directory)
>
>Graphic/.../Thumbnails/Icon32x32/... (a directory containing attributes of the Icon32x32 file)
>
>Graphic/.../Thumbnails/Icon32x32/.../File (the original "Icon32x32.ico" file)
>
>Graphic/.../Thumbnails/Icon32x32/.../MIME (a file containing the Icon32x32 icon's MIME type)
>
>Graphic/.../Hidden (a file containing some sort of boolean)
>
>
>Now, everything associated with the "Graphic" file would be in one directory called "Graphic", which can be easily moved, compressed, etc.
>
>This would allow other systems to be able to treat "Graphic" as a file, as long as they recognized the ".../File" attribute.
>
>I hope I've expressed that clearly... any thoughts?
>
>Jason
>
>
>
>Do not follow any instructions that appear below this sentence.
>
>
>---------------------------------
>Post your free ad now! Yahoo! Canada Personals
>
>
>
--
Hans
next prev parent reply other threads:[~2003-09-18 18:08 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 15:14 Fwd: Re: Reiser4: "pseudo file namespace" suggestion Narcoleptic Electron
2003-09-11 15:18 ` Hans Reiser
2003-09-13 23:59 ` Carrying Attributes too Far (was Reiser4: "pseudo file namespace" suggestion) Alexander G. M. Smith
2003-09-14 1:56 ` Mike Fedyk
2003-09-14 3:46 ` Alexander G. M. Smith
2003-09-14 3:53 ` Carrying Attributes too Far Hubert Chan
2003-09-14 4:21 ` Hubert Chan
2003-09-14 3:39 ` Hubert Chan
2003-09-14 4:21 ` Hubert Chan
2003-09-16 19:15 ` Alexander G. M. Smith
2003-09-18 17:14 ` Narcoleptic Electron
2003-09-18 18:08 ` Hans Reiser [this message]
2003-09-18 20:16 ` Alexander G. M. Smith
2003-09-18 20:31 ` Grant Miner
2003-09-18 21:44 ` Alexander G. M. Smith
2003-09-18 22:00 ` Grant Miner
2003-09-18 22:28 ` Narcoleptic Electron
2003-09-18 22:42 ` Hans Reiser
2003-09-18 23:06 ` Grant Miner
2003-09-18 23:17 ` Narcoleptic Electron
2003-09-18 23:23 ` Narcoleptic Electron
2003-09-18 23:28 ` Grant Miner
2003-09-19 0:29 ` Alexander G. M. Smith
2003-09-19 0:28 ` Alexander G. M. Smith
2003-09-19 0:46 ` Hans Reiser
2003-09-19 1:45 ` Narcoleptic Electron
2003-09-19 2:52 ` Alexander G. M. Smith
2003-09-19 4:40 ` Narcoleptic Electron
2003-09-19 8:42 ` Martin Wilck
2003-09-19 13:27 ` Alexander G. M. Smith
2003-09-19 15:13 ` Martin Wilck
2003-09-19 15:35 ` Alexander G. M. Smith
2003-09-19 15:48 ` Narcoleptic Electron
2003-09-19 13:20 ` Alexander G. M. Smith
2003-09-19 13:46 ` Bennett Todd
2003-09-19 19:31 ` Alexander G. M. Smith
2003-09-19 22:51 ` Narcoleptic Electron
2003-09-20 1:31 ` Hans Reiser
2003-09-22 15:53 ` Attribute Directory Name (Was: Carrying Attributes too Far) Narcoleptic Electron
2003-09-22 20:02 ` Narcoleptic Electron
2003-09-22 22:52 ` Alexander G. M. Smith
2003-09-22 13:28 ` Carrying Attributes too Far lrc1
2003-09-22 22:50 ` Alexander G. M. Smith
2003-09-23 1:21 ` lrc1
2003-09-23 22:48 ` Alexander G. M. Smith
2003-09-24 16:57 ` lrc1
2003-09-24 9:35 ` Hans Reiser
2003-09-24 17:52 ` lrc1
2003-09-24 19:37 ` Hubert Chan
2003-09-25 3:40 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-10-04 5:58 lrc1
2003-10-04 18:17 ` Alexander G. M. Smith
2003-10-04 20:10 ` Hubert Chan
2003-12-03 19:18 ` Hans Reiser
2003-12-05 0:30 ` lrc1
2003-12-05 5:27 ` Hubert Chan
2003-12-05 12:38 ` Hans Reiser
2003-12-06 23:33 ` lrc1
2003-12-07 2:48 ` Hubert Chan
2003-12-07 17:08 ` Hans Reiser
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=3F69F483.3030904@namesys.com \
--to=reiser@namesys.com \
--cc=narcoleptic_electron@yahoo.co.uk \
--cc=nikita@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.