Mounting a samba share on boot?
btillman99 at yahoo.com
Wed Dec 12 12:27:37 UTC 2012
From: Polytropon <freebsd at edvax.de>
To: Bill Tillman <btillman99 at yahoo.com>
Cc: "freebsd-questions at freebsd.org" <freebsd-questions at freebsd.org>
Sent: Wednesday, December 12, 2012 12:40 AM
Subject: Re: Mounting a samba share on boot?
On Tue, 11 Dec 2012 14:08:38 -0800 (PST), Bill Tillman wrote:
> Typically, Samba is used so that Windows or other SMB type
> OS'es can access the server. That said, I would simplify all
> this with the way I have mine setup. You will of course need
> the shares configured in your smb.conf, then simply put a
> command in your /etc/rc.local or /etc/rc.d/ to launch smdb
> and nmbd. I don't rely on anything in /etc/fstab to use samba.
> It's all in my smb.conf file.
Yes, that would be "the other way round", which I thought would
be less probable due to the question presented in the subject.
Terms like "mount [...] on boot" suggests that FreeBSD would act
as a SMB client here. Of course, the standard way to do things
like this would usually be something like NFS, which is not
very well supported in "Windows" land (and therefor requiring
Delegating the configuration into _one_ file (instead of spreading
it across /etc/fstab, /etc/nsmb.conf and maybe some handcrafted
/usr/local/etc/rc.d script) sounds like a much better approach.
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
freebsd-questions at freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
I've heard from more than one person that Samba is no good. Including the IT
guru here where I work. All I know is that I've been running it for years and
without a single incident. I quietly and reliably allows my Windows workstations
to access my FreeBSD server's like they were very expensive Windows file
servers. Never messed with the printing side of it and don't need to . File
sharing alone has been worth the investment in time to learn Samba.
As for NFS, I have found, on my network at least that using the TCP and -i
options to keep it from timing out has worked fine.
More information about the freebsd-questions