search for: unicodenames

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (sorry about the resend forgot limits) I've got CA Arcserve 9.0 working (sorta) by changing /etc/sysconfig/i18n (Redhat 7.3 here) to: LANG="en_US.utf8" SUPPORTED="en_US.iso885915:en_US:en_US.utf8;en" SYSFONT="lat0-sun16" SYSFONTACM="iso15" The issue I'm having is that a file named Bj?r???n (see

Samba has multiple areas of case mangling problems that cause incompatibilities when used with windows or linux clients. How viable is the idea of fixing the problems? Would the sky fall in if it preserved case, but either 'ignored it', or gave preference to matches that included the case as typed (vs. alternate case matches). The first would be fairly compatible with current Win

...symlink: samba/tests/source.py -> python/samba/tests/source.py symlink: samba/tests/strings.py -> python/samba/tests/strings.py symlink: samba/tests/subunitrun.py -> python/samba/tests/subunitrun.py symlink: samba/tests/tdb_util.py -> python/samba/tests/tdb_util.py symlink: samba/tests/unicodenames.py -> python/samba/tests/unicodenames.py symlink: samba/tests/upgrade.py -> python/samba/tests/upgrade.py symlink: samba/tests/upgradeprovision.py -> python/samba/tests/upgradeprovision.py symlink: samba/tests/upgradeprovisionneeddc.py -> python/samba/tests/upgradeprovisionneeddc.py sym...