On Mon, 20 Sep 1999, H. Peter Anvin wrote:
> Roy Stogner wrote:
> >
> > The best solution for smbfs mounting I've seen is the "mount.smb"
> > script (and "mount.smbfs" symlink) included in Red Hat's distribution
> > of the samba clients. /bin/mount calls this script, and it basically
> > lets you "mount -t smb //server/share /mount/point" as if it were
> > normal, and the call to smbmount occurs behind the scenes. This
> > doesn't affect the mount() system call, but it works for programs like
> > autofs's mount_generic.so module that fork/exec the mount command.
> >
> > I personally think mount_smbfs.c should be thrown away (would this be
> > a mount_smbfs change that HPA would be happy with?), smbfs should be
> > removed from the list of non-generic filesystems, and people and
> > distributions should be encouraged to just make their mount programs
> > work right.
> >
>
> Oh, this is the only reasonable solution to this problem. I'd be happy
> to get rid of mount_smbfs and tell people to get mount.smbfs, as soon as
> one appears.
I'm using one. I don't know how official it is, however. It's a
shell script authored by [EMAIL PROTECTED], based on an earlier
version by [EMAIL PROTECTED] On my system /bin/mount, when getting a
filesystem type like smb or smbfs which it doesn't know how to handle
natively, tries executing /sbin/mount.whatever to handle it.
Does anyone else have this kind of setup? I've got
samba-client-2.0.5a and mount-2.9o packages (both put together by Red
Hat) installed, but I don't know whether the mount.smb functionality
is a standard thing or a Red Hat-only tweak.
> Note the correct filesystem name is "smbfs".
I know, but if I put -fstype=smbfs in my automount configs, then it
tries to use the mount_smbfs.so module, which chokes with recent
smbmount versions. With -fstype=smb automount just uses the
mount_generic.so module, which works on my system.
---
Roy Stogner
