Date: Thu, 3 Jul 2003 11:38:50 -0700 From: Mark Woodson <mwoodson@sricrm.com> To: Dmitry Sukhodoev <raven@sputnik.chel.su> Cc: stable@freebsd.org Subject: Re: smbfs can't access to files with symbol ? in name and some other Message-ID: <200307031138.50633.mwoodson@sricrm.com> In-Reply-To: <20030703110900.GH57410@dds.nl> References: <20030701212607.9EAA61A774@sputnik.chel.su> <20030703110900.GH57410@dds.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 03 July 2003 04:09 am, Alex de Kruijff wrote: > On Wed, Jul 02, 2003 at 03:26:07AM +0600, Dmitry Sukhodoev wrote: > > >Description: > > > > trying to: > > mount_smbfs -o ro -f 644 -d 755 -N -I 192.168.1.100 -E koi8-r:cp866 > > //raven@file-srv/e$ /mnt/smb/fileserver and mounted filesystem can't > > access to files with with non-standart symbols in name, same as =BF > > > > >How-To-Repeat: > > > > just mount and try > > > > >Fix: > > I beleave that this is not a bug but a _feuture_. The SMB protocol just > isn't design to do this. The window partions also don't allow these > symbols. > Not quite true. I've been experiencing a similar problem. There are=20 characters allowed with Windows that aren't accessible when trying use an s= mb=20 mounted share. The easiest one for me to track down and trace is the # sign on a 2k box. = =20 Though there are characters apparently on Win98 and XP boxes. I've tried digging through the documentation for some information on how to= =20 change the character mapping to try some kind of workaround (I'm building=20 scripts to backup win shares to s FreeBSD 4.8-STABLE box), but have not had= =20 much luck finding any info online for this. =2DMark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307031138.50633.mwoodson>