caldera/2.0.x and rh60/2.2.9.
I've already posted about this twice to the samba list (since february) then
to samba-bugs (19990301); no response, so I retry.
I have
character set = iso8859-1
client codepage = 850
With samba 1.9.18p8:
smbstatus showed the filenames with localized characters ok (ie:
libert?.txt); smbclient was ok.
With samba 2.0.0 through 2.0.4b:
if I connect with smbclient to a Samba share I see those characters
ok, but smbstatus omits the localized characters in locked files so that
"libert?.txt" is:
libert?.txt with 1.9.18p8
and
libert.txt with 2.0.0-2.0.2
With samba 2.0.3 and 2.0.4b things got WORSE:
- smbstatus has exactly the same behavior as in 2.0.0/2.0.2.
- smbclient: with "character set = iso8859-1" doesn't even show
those files
and DOESN'T ALLOW THE win95 CLIENTS TO SEE those files (the files vanish
from
the samba shares); without "character set = iso8859-1" it shows the
files with
the same problem affecting smbstatus (the win95 clients see those files ok
though).
Should I change my settings??
