🚀 go-pugleaf

Syco a �crit :
> 
> Louis A.S. Holbrook <lash@artports.net> a �crit dans le message :
> L0xn6.5745$8c.692166@news01.chello.no...
> > how about modprobe smbfs?
> >
> > lash

Useless to do it here, smbfs support must be at least modularized within
the kernel. You may have smbfs.o somewhere, but if the smbfs support
option is not in the kernel, you have to make a new kernel.

> 
> Yes, effectively, I forgot it !
> So I did it : Loading of the module is OK, but the client is not.
> When I mount the ressource, all seems good : no message.
> But  indeed, there is two problems in fact :
> - when I try to learn the mount dir, ( simply ls /mnt )
>         the result is "I/O error" but the ressource is in fstab
> "//PC-1/PC-1_C on /mnt"
> - when I try to unmount : "/mnt is not in fstab or is busy" !!!
> - when I look my / dir : /mnt does not exist anymore !!!
> - after reboot, /mnt is here again.
> 
> What a fair affair !
> 
> Any suggest ?

Build a new kernel.

...
> > "Syco" <sycoweb@chez.com> wrote in message
> > news:97m52k$b5a$1@news2.isdnet.net...
> > > I installed without problem Samba FROM SUSE distrib TO SLACK Linux ( I
> > don't
> > > have samba in my Slack distrib ! ).

???? Slack knows samba for years, now ????

> > > All is OK ( few modifs to do ) for Samba -Server- ( sharing Linux dirs
> for
> > > W95 stations ).
> > > But, SMB-client doesn't work :
> > > When I try to "mount" a smb ressource, the message is allways the same :
> > > Exemple :
> > > mount -t smbfs -o username=papa,password=corons file://papa/papa_c /mnt
> > >
> > > "ERROR: smbfs filesystem not supported by the kernel
> > > Please refer to the smbmnt(8) manual page
> > > smbmnt failed: 255
> > > mount.smbfs: ioctl failed, res=-1"
> > >
> > > How can I
> > > - have a kernel OK for Slack with smbclnt ( smbmount or mount.smbfs )
> > > - Warning : this kernel *MUST* include MCA Bus support too ( MCA machine
> > > with SCSI disks ).
...

Rebuild a kernel. 'su root, cd /usr/src/linux, make clean, make
menuconfig, make dep, make zImage, make modules, make modules_install,
save your old kernel to some place, make install, add an entry to lilo
and modify the old one according to the place you've saved your old
kernel to, lilo, breath, reboot'

-- 
Manuel VIET * mailto:mviet@noos.fr * http://mapage.noos.fr/sordm68/
BB: il me dit "Unable to parse configuration file". Que dois je faire ?
JM: Lire la doc
BB: CA MARCHE !!!!!! * BB in : http://neuneu.ctw.cc - Le RTFM pour les
nuls