From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil speed
Date: Thu, 27 Jan 2005 14:28:00 -0800 [thread overview]
Message-ID: <9ae435ffe99020d753c5dc9cbc2cb5d9@collyer.net> (raw)
In-Reply-To: <890920aeecd9e2d81069fa15843b37b3@plan9.ucalgary.ca>
File names are unbounded, as always in Plan 9 (and originally in Unix,
before Unix was ``fixed'').
File name *components* are limited to NAMELEN-1 bytes (not characters).
This was 27 ASCII characters or 9 Japanese characters. In the new ken fs,
I've made it 55 ASCII characters or 18 Japanese characters, which turns
out to be enough to handle all but one of the file names that lnfs on
my machines recorded (and that was one was some obscene XML file name).
When you install the new ken fs, you can crank NAMELEN up higher if you want,
though you'll then get few directory entries per block.
next prev parent reply other threads:[~2005-01-27 22:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 2:00 [9fans] browse /sys/src YAMANASHI Takeshi
2005-01-26 2:27 ` Kenji Okamoto
2005-01-26 2:31 ` Michael H. Collins
2005-01-26 2:45 ` boyd, rounin
2005-01-26 3:50 ` Russ Cox
2005-01-26 4:28 ` Kenji Okamoto
2005-01-26 4:39 ` Kenji Okamoto
2005-01-26 8:49 ` Skip Tavakkolian
2005-01-26 10:00 ` Matthias Teege
2005-01-26 21:32 ` [9fans] fossil speed rog
2005-01-26 21:36 ` andrey mirtchovski
2005-01-26 22:09 ` Charles Forsyth
2005-01-26 22:18 ` andrey mirtchovski
2005-01-26 22:22 ` andrey mirtchovski
2005-01-26 22:48 ` rog
2005-01-26 22:26 ` rog
2005-01-26 22:13 ` Charles Forsyth
2005-01-26 22:15 ` Charles Forsyth
2005-01-26 22:40 ` andrey mirtchovski
2005-01-27 2:47 ` Russ Cox
2005-01-27 19:20 ` rog
2005-01-27 7:51 ` Fco. J. Ballesteros
2005-01-27 21:09 ` geoff
2005-01-27 21:23 ` andrey mirtchovski
2005-01-27 21:35 ` Russ Cox
2005-01-27 22:28 ` geoff [this message]
2005-01-28 2:11 ` Kenji Okamoto
2005-01-28 4:08 ` geoff
2005-01-28 4:39 ` Kenji Okamoto
2005-01-28 4:54 ` geoff
2005-01-27 3:39 ` boyd, rounin
2005-01-26 9:55 ` [9fans] browse /sys/src Fco. J. Ballesteros
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=9ae435ffe99020d753c5dc9cbc2cb5d9@collyer.net \
--to=geoff@collyer.net \
--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).