9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: G. David Butler gdb@dbSystems.com
Subject: [9fans] allowing space (ASCII 0x20) in file names
Date: Thu,  9 Apr 1998 17:08:19 -0500	[thread overview]
Message-ID: <19980409220819.Y4_ClLKppMJ4EvW8AUsW1CaCn6d04ew_mg5XvgooNmY@z> (raw)

>>From: "G. David Butler" <gdb@dbSystems.com>
>
>>I think each component limited to 27 octets is ok.
>
>What am I saying?!?  A 9 "character" file name (with up to 3 octets
>per "character") is a little anemic!  This neeeds to be at least 20.
>
>So do we change NAMELEN from 28 to 64, or bigger?  Anybody from Japan
>have an opinion?

Hello?  Where did everybody go...?

[continuing to talk to self...]

Self, first you need to split user name lengths from file name
lengths.  How about FNAMELEN?  Seems reasonable.

NAMELEN = 28
FNAMELEN = 64? 128? 256!?  Hell, might as well fix it now. 256.

In that case the overhead for 9p now gets quite high given all
the Twalks.  So how about a uchar length followed by data?  Makes
sense.

Boy, the fileserver needs a much bigger inode.  I don't see any way
around it.  Of course DIRPERBUF gets a lot smaller.  It's good I
have indexes.

And another thing, there is enough about Plan9 that the user needs
to be aware of, might as well add spaces to file names so the DOS
weenys don't eat your lunch when you do IMAP and CIFS...

Off to work.

-------------------------------------------------------------------
G. David Butler   | Who I? Zathras, a Plan9er. Nobody uses Zathras'
                  | system, but Zathras not mind. Zathras used to 
                  | having others ignore Zathras. Besides, Zathras
gdb@dbSystems.com | have best system, so Zathras happy.




             reply	other threads:[~1998-04-09 22:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-09 22:08 G.David [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-04-14 15:18 Russ
1998-04-14 15:16 Tom
1998-04-14 13:50 Rob
1998-04-14 13:35 Elliott.Hughes
1998-04-14 13:04 Russ
1998-04-14  9:50 Elliott.Hughes
1998-04-14  9:08 Elliott.Hughes
1998-04-14  6:38 Nigel
1998-04-14  6:24 forsyth
1998-04-14  5:33 forsyth
1998-04-13 23:03 geoff
1998-04-13 13:50 G.David
1998-04-13  6:00 geoff
1998-04-12  3:27 ozan
1998-04-10 14:49 G.David
1998-04-10 14:43 forsyth
1998-04-10  4:04 geoff
1998-04-10  1:03 G.David
1998-04-09 23:44 Tom
1998-04-09  3:10 G.David
1998-04-08 23:56 G.David
1998-04-08 22:05 Rob
1998-04-08 21:54 G.David
1998-04-08 20:32 Russ
1998-04-08 19:58 G.David
1998-04-08 17:45 Tom
1998-04-08 17:08 Russ
1998-04-08 16:56 G.David

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=19980409220819.Y4_ClLKppMJ4EvW8AUsW1CaCn6d04ew_mg5XvgooNmY@z \
    --to=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).