heinrici76 at gmx.de
Fri Sep 20 15:29:01 GMT 2002
On Friday 20 September 2002 12:23, Frank Matthieß wrote:
> Freitag den 20.09.2002 um 11:26 CEST +0200, schrieb Axel
> > What do you mean by this? I really do not understand. A few
> > days ago I compiled samba-2.2.5. There is a configure option to
> > also compile smbmount.
> Do you compile with smbmount?
> If you do so, read the manpage of mount:
> -t vfstype
> For most types all the mount program has to do is
> issue a simple mount(2) system call, and no
> detailed knowledge of the filesystem type is
> required. For a few types however (like nfs,
> smbfs, ncpfs) ad hoc code is necessary. The nfs ad
> hoc code is built in, but smbfs and ncpfs have a
> separate mount program. In order to make it possi
> ble to treat all types in a uniform way, mount will
> execute the program /sbin/mount.TYPE (if that
> exists) when called with type TYPE. Since various
> versions of the smbmount program have different
> calling conventions, /sbin/mount.smb may have to be
> a shell script that sets up the desired call.
I know this.
> fm at fortytwo:~$ ls -l /sbin/mount.smb*
> lrwxrwxrwx 1 root root 17 06-28 08:05 /sbin/mount.smb ->
> /usr/bin/smbmount lrwxrwxrwx 1 root root 17 06-28 08:05
> /sbin/mount.smbfs -> /usr/bin/smbmount
The "make install" of the samba2.2.5 tarball sets this up in a
The path of the samba binaries is now/usr/local/samba/bin/. And so
is the link /sbin/mount.smbfs.
> > This may cause problems. At startup "mount -a" is called before
> > network is up (at least in some distributions). So better add
> > the "noauto"-option and mount the specific share later (after
> > network coming up) by a separate skript.
> I prefer debian systems. debian mount all local fs'es first.
> After startup of networking, they setup the remote fs'es.
SuSE is not so clever concerning this issue. I got some error
messages by doing it that way.
More information about the samba