Date: Thu, 3 Feb 2005 14:28:13 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: Mark Ovens <marko@freebsd.org> Cc: FreeBSD Mailing list <freebsd-questions@freebsd.org> Subject: Re: [lorenl@alzatex.com: Re: Mounting a samba share on boot?] Message-ID: <20050203222813.GV8619@alzatex.com> In-Reply-To: <41FFB7E2.4000100@freebsd.org> References: <20050131120623.GA10752@alzatex.com> <41FE26DD.3020002@freebsd.org> <20050131134753.GE8619@alzatex.com> <20050201152035.GA7969@ei.bzerk.org> <41FFB7E2.4000100@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 01, 2005 at 05:09:54PM +0000, Mark Ovens wrote: > Ruben de Groot wrote: > >On Mon, Jan 31, 2005 at 05:47:53AM -0800, Loren M. Lang typed: > >>On Mon, Jan 31, 2005 at 12:38:53PM +0000, Mark Ovens wrote: > >>> Loren M. Lang wrote: > >>> >replacing MYWORKGROUP, SERVER, USER, secret as neccessary. Make sure > >>> >nsmb.conf is only readable by root. Add the following line to fstab: > >>> > > >>> >//user@server/share /mnt/share smbfs rw 0 > >>0 > >>> > > >>> > >>> PMJI, but do you know if it's possible to handle a share name > >>containing > a space when mounting smb filesystems using fstab? > >>> > >>> I tried > >>> > >>> "//user@server/Drive C" > >>> '//user@server/Drive C' > >>> //user@server/Drive\ C > >>> > >>> None of these worked. I know that using spaces in filenames is a Bad > >>> Idea, but this is Windows we're talking about here ;-) > >> > >>A random guess might be to try: //user@server/Driver%20C > >>%20 refers to the ascii character with hex value 20 which is space. > >>It's what webservers use for getting around spaces, samba might too.` > >>I'd be really curious to see if this works. > > > >The following seems to work for me: > > > >root@ei:/root> mount_smbfs //odo/"Temp Dir" /mnt > >Password: > >root@ei:/root> mount | grep smbfs > >//ROOT@ODO/TEMP DIR on /mnt (smbfs) > >root@ei:/root> > > > > Yes, that WFM too. The problem is if you try to add that as an entry in > /etc/fstab as it cannot handle the space. I had a quick look in fstab.c > and there appears to be no handling of escaped characters, which is > understandable I suppose since the first field would normally be > something /dev/da0s1a Well, the routines that read fstab may not handle escaped characters, but there may be some replacement for space that mount_smbfs accepts. Maybe you should check that program for some support for inserting spaces. > > Mark > > > > --- > avast! Antivirus: Outbound message clean. > Virus Database (VPS): 0505-0, 31/01/2005 > Tested on: 02/02/2005 01:30:28 > avast! - copyright (c) 2000-2004 ALWIL Software. > http://www.avast.com > > -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050203222813.GV8619>