"case sensitive" parameter - was Re: Any help would be greatly appreciated...
Tim Potter wrote: > On Thu, Aug 15, 2002 at 12:29:32AM -0500, Gerald (Jerry) Carter wrote: > > Can't we get rid of the case sensitive option?. It just seems to cause > people lots of uncessary pain. Strangely enough, having "case_sensitive = yes", makes SAMBA more responsive for case insensitive file systems. It probably would be better to have SAMBA allow the VFS level to do the file name matching, so that it can be taylored to the file system. The OpenVMS file api that is eventually called by readdir() accepts a wildcard mask. So if a vfs_wild_reeaddir() existed, it would do the wildcard matching and the wildcard file lookup could be optimized to the file system. -John [EMAIL PROTECTED] Personal Opinion Only
Re: Any help would be greatly appreciated...
On Thu, Aug 15, 2002 at 12:29:32AM -0500, Gerald (Jerry) Carter wrote: > > We run SAMBA on a Unix box with case sensitive file naming (i.e. standard > > Unix usage). > > Relevant entries in smb.conf > > case sensitive = yes > > This is really bad. Do no do this unless you are willing to suffer the > consequences of certain file searches not working Can't we get rid of the case sensitive option?. It just seems to cause people lots of uncessary pain. Tim.
Re: Any help would be greatly appreciated...
On Wed, 14 Aug 2002 [EMAIL PROTECTED] wrote: > > We run SAMBA on a Unix box with case sensitive file naming (i.e. standard > Unix usage). > Relevant entries in smb.conf > case sensitive = yes This is really bad. Do no do this unless you are willing to suffer the consequences of certain file searches not working > mangled map = (*.html *.htm) This may or may not work. No one really tests it that I know of. > I have another (undesirable) fix available, which is to set the Samba > server to be case insensitive but this leaves a gaping hole whereby two > files differing only in case could be incorrectly retrieved (or worse > the incorrect one overwritten). Any other suggestions as alternative to > the two former?? SMB (and Windows file systems) expect case insensitive file matches. cheers, jerry - Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org --http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Any help would be greatly appreciated...
We run SAMBA on a Unix box with case sensitive file naming (i.e. standardUnix usage). Relevant entries in smb.confcase sensitive = yesmangled map = (*.html *.htm) Using NT4 clients no problems are experienced in accessing files andnavigating directories. Have a (small) client base using Win98SE which canmap top level folders on the Samba server but cannot navigate. Problem isidentified as Win98 sending filenames in upper case to Samba server whichsearches case sensitive and returns "not found" . NT4 preserves case. Does anyone know of registry key to add/modify to cause Win98 to preservecase when using SMB? Win98 displays correct case when the initial mapping isdone but requests for navigation (and/or properties) are incorrectlyformatted. I have another (undesirable) fix available, which is to set the Samba serverto be case insensitive but this leaves a gaping hole whereby two filesdiffering only in case could be incorrectly retrieved (or worse theincorrect one overwritten). Any other suggestions as alternative to the twoformer?? Joseph L. Ibarra 214-914-4883 cell 785-276-4249 office 775-320-3589 fax ELOA [EMAIL PROTECTED]
