Bug? No, feature. A hacked patch for Linux smbmount.
urban at teststation.com
Sat Jan 20 12:49:54 GMT 2001
On Thu, 18 Jan 2001 nfudd at mellor.bc.ca wrote:
> It almost worked, except that I was forced to try and mount a share that
> had a space in it. There is no way to specify spaces in pathnames in
> /etc/fstab, neither quotes nor backslashes had any effect.
If mount won't allow spaces to be escaped with \ then maybe mount should
> Also, a cron job that says:
> */5 * * * * ls /ftp 2>&1 > /dev/null || (umount /ftp ; mount /ftp; echo remounted /ftp)
> since the NT share *sometimes* goes weird. Note, this only does
> something when 'ls' returns an error. If /ftp is completely
> mounted or unmounted, there is no error.
What kernel are you using? Do you get error messages from the kernel when
this happens? Does 2.2.18 work any better for you?
> I don't know if you'd want to allow url quoting of command line
> options by default, or if you'd be leery of breaking sites with percent
> signs in them. Perhaps an option on the command line that says
smbmount allows "username=user%password", so there would be a conflict
there. I know you suggest encoding only parts of the arguments, but a lot
of the option may contain space.
> 'I want to use url escaping' would be the best solution. Doesn't
> break any existing sites, yet allows this feature to be added.
An option that enables urldecoding of all parameters might be useful,
perhaps urldecode or just url.
mount -t smbfs -o username=my%20name,workgroup=silly%20name,urldecode \
autofs has the same problem (at least some versions) where it wouldn't
allow space and give no way to escape them. If mount and autofs is fixed
instead this wouldn't be necessary and that would solve the same problem
for other filesystems too.
More information about the samba