[tex-live] Fwd: filename clash (upper/lower case)

Zdenek Wagner zdenek.wagner at gmail.com
Mon Jan 15 11:24:13 CET 2007

2007/1/15, Frank Küster <frank at kuesterei.ch>:
> Jonathan Kew <jonathan_kew at sil.org> wrote:
> > On 15 Jan 2007, at 7:03 am, Frank Küster wrote:
> >
> >> OS X has a case-sensitive filesystem by default, I'm not
> >> sure whether you can switch it off or what Mac OS 9 does.
> >
> > No, HFS+ is case-insensitive (but case-preserving). There's a variant
> > (HFSX) that has a case-sensitive option available, but I'd guess the
> > proportion of users running it is tiny. Likewise, UFS is available
> > but rarely used.
> Hm, just before posting I created a directory "Kochen" in my wife's
> MacBook's home folder, where there is already "kochen", and it didn't
> have a problem with that.  But maybe I'm just confused...
I use TeXLive in OS/2. I can get OS/2 binaries without the texmf tree
and I add the texmf tree from TL. The OS/2 machine has dual boot with
Linux but no DVD drive. Thus I boot Linux, mount the HPFS drive,
symlink it to my Linux home which is exported over NFS and from
another Linux machine copy the texmf tree by cp --recursive. HPFS is
not case sensitive and does not support symlinks, so I do not even
know what happens is I try to copy a symlink. Maybe it will not be
copied or it may create an empty regular file. Thus if it first copies
"readme" and later while copying symlink "README" and empty file is to
be created, the system remembers that the name originally was readme
and README will overwrite it keeping the old name. Maybe -L willl help
if I copy the files like that but if the package comes from .zip or
.tar.gz, the behaviour will be different. I like symlinks and case
sensitive file systems but TeX should stay patform independent.

> Regards, Frank
> --
> Dr. Frank Küster
> Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
> Debian Developer (teTeX/TeXLive)

Zdeněk Wagner

Zdeněk Wagner

More information about the tex-live mailing list