From: smiley@zenzebra.mv.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] files vs. directories
Date: Fri, 4 Feb 2011 00:24:31 +0000 [thread overview]
Message-ID: <86hbck1wao.fsf@cmarib.ramside> (raw)
In-Reply-To: <AANLkTikXZ19gT9qhqKgu3LtFqq0VEk3W5eP3MD+H81_L@mail.gmail.com> (Eric Van Hensbergen's message of "Thu, 3 Feb 2011 17:13:23 -0600")
Eric Van Hensbergen <ericvh@gmail.com> writes:
>> build an experimental OS around it! But if you go this path,
>> do consider providing a few more datatypes in the filesystem
>> (integers, file-id, strings, ...). Basically persistent data
>> types. Or just use an object or relational database as your
>> filesystem.
IIRC, Reiserfs was aiming to incorporate general database semantics into
the file system design. /me wonders what ever happened to Hans...
> gets in the way of the sensible interface. The world has become
> considerably richer than collections of byte-stream files, yet we have
> no way of notionally representing richer structures in the name space.
I occasionally daydream about having naming conventions like:
$mtpt/timestamp # application interface node
$mtpt/timestamp.printf # returns printf strings representing I/O format
$mtpt/timestamp.usage # returns human readable help on "timestamp" file
...etc.
--
+---------------------------------------------------------------+
|E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2011-02-04 0:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 11:45 dexen deVries
2011-02-03 13:05 ` erik quanstrom
2011-02-03 13:40 ` dexen deVries
2011-02-03 13:59 ` erik quanstrom
2011-02-03 13:36 ` roger peppe
2011-02-03 13:40 ` erik quanstrom
2011-02-03 13:44 ` dexen deVries
2011-02-03 14:15 ` roger peppe
2011-02-03 14:27 ` dexen deVries
2011-02-03 18:42 ` smiley
2011-02-03 22:33 ` dexen deVries
2011-02-04 1:42 ` Robert Ransom
2011-02-04 1:49 ` erik quanstrom
2011-02-04 3:30 ` Robert Ransom
2011-02-04 4:11 ` Eric Van Hensbergen
2011-02-04 4:17 ` andrey mirtchovski
2011-02-04 5:36 ` erik quanstrom
2011-02-03 14:35 ` dexen deVries
2011-02-03 16:58 ` Bakul Shah
2011-02-03 23:13 ` Eric Van Hensbergen
2011-02-04 0:24 ` smiley [this message]
2011-02-04 0:45 ` Skip Tavakkolian
2011-02-04 1:29 ` Nick LaForge
2011-02-04 18:26 Lucio De Re
2011-02-04 18:28 Lucio De Re
2011-02-04 18:31 Lucio De Re
2011-02-04 18:41 ` Lucio De Re
2011-08-21 17:33 ` Enrico Weigelt
2011-02-04 18:38 Lucio De Re
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=86hbck1wao.fsf@cmarib.ramside \
--to=smiley@zenzebra.mv.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).