From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OT: ZFS
Date: Mon, 20 Sep 2004 11:44:22 +0300 [thread overview]
Message-ID: <200409200844.i8K8iM61000676@skeeve.com> (raw)
> > Someone has to swap them, if they don't use the same order.
>
> Not really.. Could be ascii. xml even. ;-)
If you extend ASCII to directory entries, and outlaw \n in filenames,
using it instead to terminate the directory entry, you could have
cat'able directories. That'd be pretty cool. :-)
Arnold
next reply other threads:[~2004-09-20 8:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 8:44 Aharon Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-17 17:21 bmaroshe
2004-09-16 0:21 YAMANASHI Takeshi
2004-09-16 0:36 ` Russ Cox
2004-09-16 0:08 YAMANASHI Takeshi
2004-09-16 0:10 ` boyd, rounin
2004-09-16 2:14 ` Dan Cross
2004-09-15 16:39 Sam
2004-09-15 18:37 ` boyd, rounin
2004-09-15 19:05 ` Dan Cross
2004-09-15 19:12 ` Tim Newsham
2004-09-17 7:09 ` geoff
2004-09-17 8:04 ` Lucio De Re
2004-09-17 8:52 ` rog
2004-09-17 9:27 ` Fco. J. Ballesteros
2004-09-17 13:38 ` Nigel Roles
2004-09-17 20:54 ` Tim Newsham
2004-09-17 15:21 ` Ronald G. Minnich
2004-09-17 14:37 ` Bruce Ellis
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=200409200844.i8K8iM61000676@skeeve.com \
--to=arnold@skeeve.com \
--cc=9fans@cse.psu.edu \
/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).