Hi all! Just stumbled upon this issue when trying to hook up a PDA and a mobile phone to my computer via Bluetooth. A quick and dirty solution can be found attached.
usage: * move the obexfs binary to obexfs.real * copy the attached script into its place and make sure permissions are set to 755 The fstab entry can be set to something like "obexfs#-b00:11:22:33:44:55\040-B10". The wrapper script will resolve the quotes and append the filesystem name needed for unmounting. Nevertheless this is only a workaround and no proper solution. either: * obexfs should be able to fetch its parameters from an other location as fstab OR * obexfs should be wise enough to scan for the channel providing the OBEX service - this seems to be implemented in obexfs 0.12+. So this workaround will no longer be needed then. As far as I can tell it is no flaw of the mount command as the man page for fstab states: If the name of the mount point contains spaces these can be escaped as '\040'. So mount is not meant to split up something as for further processing the name of a mount point (for which the mechanism exists) shall not be split. Yours, TS
#!/bin/bash # # a hack for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461509 # # move the original obexfs binary to obexfs.real # COMMAND=/usr/bin/obexfs.real COMMAND+=" " for argument in $@ do COMMAND+=$argument COMMAND+=" " done # fixes http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398051 COMMAND+="-o fsname=\"obexfs#$1\"" #echo "exec: $COMMAND" # need to use eval here eval $COMMAND
