Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.sdsmt.edu!news.mid.net!mr.net!news.sgi.com!enews.sgi.com!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!psinntp!psinntp!interramp.com!usenet From: dcmyers@access.digex.net (David C. Myers) Newsgroups: comp.unix.bsd.freebsd.misc Subject: High-bit characters in file names Date: 8 Aug 1996 03:41:52 GMT Organization: PSI Public Usenet Link Lines: 19 Sender: myers@freebsd.interramp.com (David C. Myers) Message-ID: <4ubnm0$l0d@usenet10.interramp.com> NNTP-Posting-Host: 38.12.171.220 X-Newsreader: knews 0.9.6 When transferring files via NFS from my Mac, I sometimes end up with high-bit characters (> 128) in the file name. This presents a big problem to the shell, which doesn't allow the entry nor the display of high-bit characters. Thus I can't enter the proper characters to delete the file, and I can't rename it. Using "ls" will show a file name, but this file name is false, in that it doesn't show the real characters. rm -r doesn't work either, since it apparently tries to resolve the file name using shell- type mechanisms, which also fail. So, is there a way I can read the "true" name of the file directly from the inode, or something like that? At least if I have the true file name, I can write a perl script to delete it. Any other ideas would be welcome. -David.