Third & Last Try: Resend: Name Mangling
jas88 at cam.ac.uk
Wed Sep 13 12:43:26 GMT 2000
On Wed, 13 Sep 2000, Ross Branje wrote:
> Any chance that someone might address this inquiry?
> It was originally sent in Vol1 #93, on August 31, 2000.
> -----Original Message-----
> From: Ross Branje [mailto:ross at wanware.com]
> Sent: Thursday, August 31, 2000 11:06 AM
> To: 'samba-technical at samba.org'
> Subject: Name Mangling
> I currently have Samba 2.0.7 installed on a SCO5.5 box. I have seen previous
> posting regarding the fix to this name mangling issue but have had no luck
> resolving it. When I enable name mangling, the WIN9X pc's resolve long file
> names by inserting the mangling character and creating an 8.3 filename. When
> I disable mangling, the WIN9X pc's cannot see any file names longer than
> 8.3. The WINNT pc's are unnaffected throughout either of the changes.
> Because of large directory trees, the mangling character substitution and
> renaming to 8.3 format is not acceptable. For example, a directory may have
> sub-dir's that use a name & then a number( mylongdir1, mylongdir2...). The
> problem arises every 10 directories because mangling resolves mylongdir10,
> mylongdir20, mylongdir30 all to be mylongd~0. It is then impossible to tell
> which is which directory is which. I have compared my smb.conf with said
> file on a Linux box running Samba. The Linux box does not cause these
> problems but I have been unable to tell where the problem lies.
I would imagine NT is doing its own mangling locally, so it mangles
correctly? If mylongdir20 and mylongdir30 both mangle to MYLONG~0, there's
something rather nasty wrong... What SHOULD happen, of course, is that
after we've mangled something into MYLONG~9, we go into double figures:
MYLON~10, MYLON~11, etc. If Samba isn't doing this correctly, it should be
a fairly simple fix, I hope??
More information about the samba-technical