SMBFS problems in this morning's -CURRENT
sanewo at ba2.so-net.ne.jp
Thu Jun 17 00:04:12 GMT 2004
Before calling mount(2), mount_smbfs calls smb_lib_init(), which requires
smbfs module loaded.
Solution 1: It's a spec. Put ``smbfs_load="YES"'' in your loader.conf.
Solution 2: Modify(backout) mount_smbfs so that it behaves as before.
Solution 3: Modify smb_lib_init so that it tries to load smbfs if it failed.
----- Original Message -----
From: "leafy" <leafy at leafy.idv.tw>
To: "Jonathan Fosburgh" <syjef at mdanderson.org>
Cc: <freebsd-current at FreeBSD.org>; "Lukas Ertl" <le at FreeBSD.org>; "Alex
Dupre" <ale at FreeBSD.org>
Sent: Tuesday, April 20, 2004 1:46 AM
Subject: Re: SMBFS problems in this morning's -CURRENT
> On Mon, Apr 19, 2004 at 11:36:35AM -0500, Jonathan Fosburgh wrote:
> > I had to do the same thing this time, but I assumed (perhaps
> > it had something to do with trying to use the previous, incorrect
> > mount_smbfs.
> > - --
> > Jonathan Fosburgh
> The new binary requires this, the old one did not. The commit message
> says that mount(2) will auto-load the smbfs kernel module, but I am
> afraid it's not the case.
> "Without the userland, the kernel is useless."
> --inspired by The Tao of Programming
More information about the freebsd-current