Re: determine default filename encoding

From: cent (centREMOVE_at_u.washington.edu)
Date: 12/30/04

  • Next message: Gernot Fink: "Re: boot knoppix from SCSI CD ROM" 
    Date: Thu, 30 Dec 2004 10:53:42 -0800

    > 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.

    >> 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

    > 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"

    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.

    > 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). 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.

    Thanks for your time!

  • Next message: Gernot Fink: "Re: boot knoppix from SCSI CD ROM"

    Relevant Pages

    • Re: determine default filename encoding
      ... > The files were copied there by the Mac users via Netatalk to the RHES ... > have now mounted on the SLES 9 server. ... you no longer have RHES 2.1 running/handy? ...
      (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: Looking For Cheat Sheets
      ... This PHP5 server will use the SQL API ... realize that SLES9 is not going to officially support ... Biggest problem is that SLES9 is closest to SUSE Prof 9.1 build-wise. ...
      (alt.os.linux.suse)
    • 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)