[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to use smbfs even though compiled in.



After doing some double checking I've found the problem. I was assuming
that dpkg was setting up the symbolic links to the new kernel images
properly. It creating a link /vmlinuz, which is what I was expecting,
and thought was working. However SILO is using /boot/vmlinuz. I think
this is because /boot is my first partition, and silo.conf sets
partition=1 and image=1/vmlinuz.

It should have been obvious the wrong kernel was being used since smbfs
wasn't available, even though I compiled support for it in, but I guess
I'm a little slow, and was sure that the new kernel was being used. (I'm
not certain, but I think another sign that the new kernel was not being
used is that I got numerous "depmod: Unresolved symbols" messages at
boot up). I now have smbfs working as an installable module and am using
the 2.4.18 kernel that is available from the debian servers. Hopefully
I'll be as successful with a custom kernel.

Thanks,
Rob Mosher


On Tue, 2003-06-24 at 16:25, Roy Bixler wrote:
> On Tue, Jun 24, 2003 at 04:10:43PM -0400, Robert C. Mosher II wrote:
> > On Tue, 2003-06-24 at 15:07, Roy Bixler wrote: 
> > > On Tue, Jun 24, 2003 at 02:40:20PM -0400, Robert C. Mosher II wrote:
> > > > I have been trying to compile a kernel to be used on several Ultra 5s in
> > > > my schools computer science lab. One of the main reasons I need to
> > > > recompile the kernel is so that smbfs will be supported. Although the
> > > > kernel compiles and is usable, smbfs is not supported: 
> > > > 
> > > > 	ERROR: smbfs filesystem not supported by the kernel 
> > > > 	Please refer to the smbmnt(8) manual page 
> > > > 	smbmnt failed: 255 
> > > 
> > > When you do 'lsmod', do you see something like the following?
> > > 
> > > Module                  Size  Used by    Not tainted
> > > smbfs                  39376   1 (autoclean)
> > > 
> > 
> > Running 'lsmod' only gives me the headings. There are no modules listed.
> 
> I guess that would be expected if you compiled a non-modular smbfs.
> Did you?
> 
> I am using the Linux 2.4.21 kernel on a Sun Blade 100 with Debian
> unstable.  Mounting a Samba share works as expected.
> 
> i.e. with
> 
> # mount -t smbfs -o username=user,uid=user //samba/share /mnt
> 
> I am prompted for a password, the mount works and the share is mounted
> under /mnt.
> 
> -- 
> Roy Bixler <rcb@ucp.uchicago.edu>
> The University of Chicago Press
> 




Reply to: