[email@example.com: Re: Mounting a samba share on boot?]
Loren M. Lang
lorenl at alzatex.com
Thu Feb 3 14:29:09 PST 2005
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 at server/share /mnt/share smbfs rw 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 at server/Drive C"
> >>> '//user at server/Drive C'
> >>> //user at 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 at 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 at ei:/root> mount_smbfs //odo/"Temp Dir" /mnt
> >root at ei:/root> mount | grep smbfs
> >//ROOT at ODO/TEMP DIR on /mnt (smbfs)
> >root at 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
> 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.
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
More information about the freebsd-questions