From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 9 Apr 1998 17:08:19 -0500 From: G. David Butler gdb@dbSystems.com Subject: [9fans] allowing space (ASCII 0x20) in file names Topicbox-Message-UUID: 747e3282-eac8-11e9-9e20-41e7f4b1d025 Message-ID: <19980409220819.Y4_ClLKppMJ4EvW8AUsW1CaCn6d04ew_mg5XvgooNmY@z> >>From: "G. David Butler" > >>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.