UNIX filenames are case-sensitive, DOS/Windows filenames are not. To a
Windows machine, SEI001 and sei001 are the same filename. SMB is a
Windows protocol, so the behavior you describe is exactly what I would
expect Samba to do. It's the "right" behavior for something that
wants
to look like an NT Server.
If both machines are running Samba on UNIX and you're not too worried
about interoperability with Windows machines (but if not, why are you
running Samba?) you can try messing with the "case sensitive" option,
it
might do what you want but is also likely to end up causing strange
problems for Windows clients.
It works with NFS because NFS is a UNIX protocol. It will also work with
ftp, rcp, scp, rsync, and other common UNIX tools. If you need to retain
filename case while transferring files from one UNIX machine to another,
I think that Samba really isn't the best tool for the job.
On Wed, Mar 13, 2002 at 03:18:36PM +0100, Volkhart Welter
wrote:> Hello,
> i have a great problem with copying files via smbmount and smbclient.
> In my source-directory on computer1 i have the files
>
> sei001 with size 100 bytes
> and
> SEI001 with size 200 bytes.
>
> After copy these files to computer2 in the destination directory there only
> SEI001 with the size of 100 bytes has arrived.
>
> Samba does the following:
> It copies the file SEI001 to the destination and then overwrites the SEI001
> on the destination computer with the content of sei001 instead of creating
a
> new file.
--
Michael Heironimus