** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Does setting preserve case=no solve your issues ?
No, as “touch test.test ; touch TEST.test” still creates two separate
files.
Anyhow, “touch file.test ; ls FILE.test” (correctly) returns FILE.test?
--
case sensitivity option (case sensitive=no) is not honored
–– more importantly, with “preserve case = no” it is seems to be
impossible to create mixed-case file names; but only from Windows, LINUX
does allow this…?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification
My conclusion for now:
Does setting preserve case=no solve your issues ?
YES, BUT it creates a new critical issue. With this option, it is no
longer possible to create files with the case that the file passes (see
smb.conf). They are forced to be the default case (lower).
--
case sensitivity
hm… might “short preserve case = no” be the key?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
** Changed in: samba (Ubuntu)
Status: New = Invalid
** Description changed:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test”
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43896901/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
http://launchpadlibrarian.net/43896902/SambaInstalledVersions.txt
--
case sensitivity option (case sensitive=no) is not honored
I think what you're looking for is the preserve case option (default
to yes, which means new files are created with original case preserved).
case sensitive is just use to match existing files (default to auto).
See man smb.conf for details. Marking as invalid (not a bug), please
reopen with more
I disagree.
The problem is that when, for example, two files “test.test” and
“test.TEST” are being addressed they should be treated as the exact same
file, as case sensitivity should be off and SAMBA should not care about
letter cases. They do when being addressed by a Windows (7) machine, in
my
SMB shares work with a negotiation between the capabilities of the server and
the capabilities of the client.
By default, it tries to enable as many features as possible. By default (case
sensitive=auto, preserve case=yes), when using Linux clients to connect to
Linux servers, you'll get full
10 matches
Mail list logo
