Date: Wed, 11 Jun 2008 14:40:06 +1000 From: Antony Mawer <fbsd-current@mawer.org> To: Stanislav Sedov <stas@FreeBSD.org> Cc: Garrett Cooper <yanefbsd@gmail.com>, current@freebsd.org, Peter Wemm <peter@wemm.org> Subject: Re: Moving from smbfs to cifs Message-ID: <484F5726.9050300@mawer.org> In-Reply-To: <20080611022502.3d6c01d5.stas@FreeBSD.org> References: <7d6fde3d0806091102k62637099qbaa73ca4d38ff64c@mail.gmail.com> <e7db6d980806091319n1caef691k2b0dbf295d796311@mail.gmail.com> <484DB796.4030204@mawer.org> <20080611022502.3d6c01d5.stas@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Stanislav Sedov wrote: > On Tue, 10 Jun 2008 09:07:02 +1000 > Antony Mawer <fbsd-current@mawer.org> mentioned: > >> - Problems dealing with various character encodings in filenames > > What problems you mean? It has a '-E' switch to set encoding. > E.g. '-E koi8-r:cp866' always works for me. The problems I was referring to are mainly regarding smbfs on FreeBSD talking to Samba on Mac OS X. My understanding (from conversations with R. Imura) is that the Mac OS X implementation of Samba speaks Unicode by default, whereas the smbfs implementation is not multi-byte aware. This can lead to situations where files on the Mac OS X server with multi-byte characters in the filenames are not accessible via SMBFS - they appear with jumbled names in the directory listing, and cannot be accessed using any name (smbfs returns "file not found"). I stumbled across patches available by R. Imura which are a work todays adding Unicode support to smbfs, and from what I gather are derived from changes in Darwin (Mac OS X) smbfs: http://people.freebsd.org/~imura/kiconv/ There are potentially other improvements available from the Darwin SMBFS implementation, available here: http://www.opensource.apple.com/darwinsource/10.5.2/ http://www.opensource.apple.com/darwinsource/tarballs/other/smb-348.1.tar.gz --Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?484F5726.9050300>