Re: determine default filename encoding

From: prg (rdgentry1_at_cablelynx.com)
Date: 12/30/04 

Date: 30 Dec 2004 12:50:03 -0800

cent wrote:
> > So, you are serving both Macs _and_ Win clients?
> >
> >> About 1000 of the Macintosh files have a degree
> >> symbol in the filename.
> >
> > How did it get there? Extended chars can prove a hassle (as you
are
> > finding out). Can you substitute a more dependably portable char
-- an
> > ascci char?
>
> The files were copied there by the Mac users via Netatalk to the RHES
2.1
> server which is dead. The user files were on a separate hard drive
which I
> have now mounted on the SLES 9 server.

So, you no longer have RHES 2.1 running/handy? :(

> >> Although both versions of Linux use
> >> comparable versions of Netatalk (the protocol that allows
Macintosh
> >> computers to have access to a Linux fileserver)
> >
> > _What_ version? There is a new version out that addresses
lingering(?)
>
> RHES 2.1 server had Netatalk 1.6.4
> SLES 9 server has Netatalk 1.6.4-51.1

Yea, I couldn't find any 1.6.x docs at Netatalk site, so I don't know
if they were running afpd 3.x -- that is when it went UTF8 capable.
Check your docs to find out which version you are running.

> > Check that your LOCALE settings are the same on both systems:
> > $ locale
>
> RHES 2.1
> LANG = "en_US"
> LC_CTYPE="en_US"
>
> SLES9
> LANG= (appears empty!)
> LC_CTYPE="en_US.UTF-8"

You _might_ restore the "old" display by setting SLES9 locale the same
as RHES 2.1. From the man page:
LC_CTYPE Character classification (ie., encoding) and case
conversion.
You might also try:
[@pbrain]$ locale -k LC_CTYPE | fgrep charmap
charmap="ISO-8859-1"

See Cautions below ...

> Rather than make a custom SLES9 system I'd rather force the files
from the
> RHES 2.1 server to conform to the default SLES9 OS settings.
>
> Since my Mac OS9 and OSx users are not having problems with Netatalk
1.6.x I
> thought I would postpone migrating to Netatalk 2.0 until required. I
might
> actually be taking a half-step toward Netatalk 2.0 because the Suse
tech
> support said SLES9 is using UTF8.

That's the LC_CTYPE="en_US.UTF-8".

> > Since you gave us no examples of the display _differences_ you are
> > forcing us to take a shot in the dark. Is it _just_ a display
problem
> > (hopefully) or are some files inaccessible?
>
> The files are inaccessible by Mac users. I can copy new files to and
from
> the SLES9 server with a Mac using extended characters in the
filename.
> Those extended characters appear differently on the SLES9 server
(0xc2b0 I
> believe, they are non-printing) than the RHES 2.1 (:a1).

Arghhhhh ...
Sounds like the char in the RHES filenames are "UTF8 boinked" -- that's
a technical term.

> If I cut-and-paste
> 0x2b0 into the old file filenames (.AppleDouble folder too) they
become
> accessible again by Mac users on the new server. I have a script
that
> automates this process. I'm holding off using the script until I
know that
> it is right thing to do - I want to avoid making a horrible mess.
>

Definitely make a backup of the affected files. You might be able to
play with the filenames alone if you can find a way to get the
appropriate output from ls > filenamelist. Not sure if/how ls affected
by UTF8 setting -- by now you would think it would be OK. You might be
able to get the output you need by simply getting rid of the ".UTF-8"
in LC_CTYPE="en_US.UTF-8".

The problem with changing these settings on a server is that if you
don't take it off the network you may have filenames created that will
"fail" when you change back again.

Not being a Mac person -- the few we have at school aren't even on the
lan -- and not having access to machines or docs, etc. pertinent to
your case, I can't offer much experienced help. Willing to provide
moral support and do some spare time snooping if that will help.

Here are some links that _might_ provide some insight/background.
Don't study them too hard -- they will make your head hurt. (The
Unicode specs will make your head explode)

http://hektor.umcs.lublin.pl/~mikosmul/computing/articles/linux-unicode.html
http://en.wikipedia.org/wiki/Universal_character_set
http://home.no.net/david/i18n.php
http://www.jw-stumpel.nl/stestu.html

TLDP has some older HOWTOs that may be useful -- this area has been
changing over the last several years (especially re: apps) so you may
need some older docs to cover RHES 2.1 quirks.

Check Netatalk archives or post to the list may be the best way to get
experienced help.

And be prepared to google till sweat poors off your head ;)
hth,
prg
email above disabled

Relevant Pages

  • Re: determine default filename encoding
    ... The files were copied there by the Mac users via Netatalk to the RHES 2.1 ... have now mounted on the SLES 9 server. ... Rather than make a custom SLES9 system I'd rather force the files from the ... The files are inaccessible by Mac users. ...
    (comp.os.linux.setup)
  • Re: ProDOS, OS X and Netatalk
    ... my server is also my internet gateway and firewall so I ... It looks like Debian testing is built using PAM, ... By doing so, netatalk will ... support so-called 'RANDNUM' authentication. ...
    (comp.sys.apple2)
  • Re: Connect to Server... with linux?
    ... My server is a fresh install of Kubuntu 7.04, ... I can ssh > into the box, but typing it into the 'Connect to ... Server' box does > nothing. ... I did run across netatalk while I was researching this, ...
    (comp.sys.mac.system)
  • Re: So fn sick of viruses from just surfing the web!
    ... Mac users were saying for some time, up until quite recently, how there ... on other hand, if you have a samba server, you might wanna have a AV trying ... to keep it clear so that windows clients don't get infected using your ... don't fight malware with anti-malware... ...
    (microsoft.public.windowsxp.general)
  • Re: netatalk experiences
    ... > server with SFM. ... Will netatalk treat resource fork better? ... I use it for years on Suse and Debian. ... Macintosh application complaining about "Error ...
    (Debian-User)