the file name length can be configured at compile time.
look for the NAMELEN enum.
like the cwfs64x in 9front uses 144 instead of 56.
you mentioned windows. theres a -o trspaces option in cifsd
that will convert space characters to non breaking space
and back for you.
hope this is usefull...
--
Thank you cinap,
I tried to copy all my Dropbox data to cwfs.
the number of files that exceeded 144B name limit was only 3 in 4 files.
I will be happy if cwfs64x natively accepts longer name, but the requirement
is almost endless. for example, OSX support 1024B names.
I wonder if making NAMEL
Hello,
I have updated u9fs for OSX.
the new version uses translation table.
therefor it can support not only japanese runes, but also any other runes.
NFD to NFC table of latin runes are included.
I hope the patch is useful for OSX users.
I also updated "trans". the previous version had bugs.
y
On Sun Jun 23 09:38:01 EDT 2013, aris...@ar.aichi-u.ac.jp wrote:
> Thank you cinap,
>
> I tried to copy all my Dropbox data to cwfs.
> the number of files that exceeded 144B name limit was only 3 in 4 files.
> I will be happy if cwfs64x natively accepts longer name, but the requirement
> is a
with 8K names, using base64, one could encode 6111 bytes of data in the
name. i just did a quick inventory[*] of my $home; 74% of my files have
less than 6112 bytes of data.
[*]
% fn pctfileslessthan6k () {
x=`{du -na $home|wc -l}
y=`{du -na $home|awk '$1 < 6112 {print $0}'|wc -l}
pct=`{echo '2k '
