From: "Alexander G. M. Smith" <agmsmith@rogers.com>
To: Nate Diller <nate.diller@gmail.com>
Cc: reiserfs-list@namesys.com, tdwebste2@yahoo.com
Subject: Re: Viewing files as directories
Date: Tue, 25 Jul 2006 21:25:17 -0400 EDT [thread overview]
Message-ID: <5822151589-BeMail@DualP3> (raw)
In-Reply-To: <5c49b0ed0607250922w60f217dap468d2356129479ac@mail.gmail.com>
Nate Diller wrote on Tue, 25 Jul 2006 09:22:01 -0700:
> On 7/25/06, Timothy Webster <tdwebste2@yahoo.com> wrote:
> > ===========================
> > My question
> > ===========================
> > How should directory mime types be recorded?
> > What is the standard?
>
> there's no standard for this sort of thing, but the Be file system did
> this, maybe it's the 'standard' cause no one else has really even
> tried. either way, the book about it is *very* worthwhile, and these
> days is free
>
> http://haiku-os.org/downloads.php?mode=view_dl&id=7
Apple developed their own file typing system. It's more of a class hierarchy
than MIME types. Have a look at "Uniform Type Identifiers", a good
description is at http://arstechnica.com/reviews/os/macosx-10.4.ars/11
Maybe there's a standard cluster of UTIs there for containers, like
directories. By the way BeOS had directories identified with a MIME
type of application/x-vnd.Be-directory and there were other ones for
disk volumes and the like.
- Alex
next prev parent reply other threads:[~2006-07-26 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 8:27 our 2.6.17 patch is not stable, please be warned Hans Reiser
2006-07-25 13:35 ` Viewing files as directories Timothy Webster
2006-07-25 16:22 ` Nate Diller
2006-07-26 1:25 ` Alexander G. M. Smith [this message]
2006-07-26 0:08 ` David Masover
2006-07-26 2:39 ` Toby Thain
2006-07-26 2:39 ` Toby Thain
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=5822151589-BeMail@DualP3 \
--to=agmsmith@rogers.com \
--cc=nate.diller@gmail.com \
--cc=reiserfs-list@namesys.com \
--cc=tdwebste2@yahoo.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.