Help! modifying os to support >14 char filenames (sys V.3)

[Miguel A. Ramirez]

In article <8738 at orca.wv.tek.com> jeff at onion.pdx.com (Jeff Beadles) writes:
>pcg at cs.aber.ac.uk (Piercarlo Grandi) babbles:
>|
>|Do you *really* need much larger? Why? If something like 30 instead of
>|14 would do, an easy hack exists.
>
>We could use a few less "hacks". :-)

I'll second this! 


>|Well, this can be (and has been) done in two ways:
>|
>|1) keeping the current organization, but just extending the size limit.
[...]
>This is **NOT** true.  There are hard-coded user programs that depend on a
>14 character filename limit!  It's by no means as easy as changing a
>#define or two.
>
>For example, what will this code fragment do with >14 character filenames?
>...
>	for(i=0; i<14; i++)
>		if(*xx)
>			*yy++ = *xx++;
>		else
>			break;
>	*yy ='\0';
>...
>
>This is typical of parts of the SYSV 3.2 code.  True, this is not an robust way
>to handle this, but it is typical of the code.  The ONLY way to find these
>sorts of problems is by inspection or searching.
>
Finally, someone on the net with a much better grip on reallity. There's no 
such thing as an easy hack. BTW, Piercarlo  did you test not only the kernel
but also all the commands that were effected by the long file name support? 
No? But I thought it was an easy hack? 
-- 

Miguel A. Ramirez, | machina at uts.amdahl.com | {sun,uunet}!amdahl!machina