[Voyage-linux] Samba on Voyage Linux

[Joe.Kelly]

> Anyway, you should put your mount command in fstab.

Okay, I put my mount in fstab and I was able to successfully mount the samba
share. Thanks for the suggestion. However, it would be nice if Voyage could
also support on-the-fly mounting (i.e. after bootup) with the smbmount
command.

Even with fstab solution, my reliability test (see messages below) does not
work. That is, when I UNshare the mounted samba share, reshare it, and then
try to "ls" it, I still get the "invalid slot" error. Could it be a 2.6 vs
2.4 kernel issue? Could it be caused by voyage's mostly read-only file
system? Or is it some other reason? I've already ruled out samba version
differences -- both boxes run the same version.

> -----Original Message-----
> From: Punky Tse [mailto:punkytse at punknix.com] 
> Sent: Tuesday, February 07, 2006 5:23 PM
> To: Joe.Kelly
> Cc: 'voyage-linux at list.voyage.hk'
> Subject: Re: [Voyage-linux] Samba on Voyage Linux
> 
> 
> 
> Joe.Kelly wrote:
> > A very temporary workaround is to execute "remountrw" 
> before executing
> > smbmount. This is probably bad for the CF card though. Any 
> suggestions would
> > be appreciated. Perhaps symlinking /etc/mtab~ to 
> /proc/mounts~ would work?
> >   
> Probably you should create symlink /etc/mtab~ to 
> /rw/etc/mtab~ and touch 
> the file in /ro/etc/mtab~ 
> Anyway, you should put your mount command in fstab.  May fix in next 
> release.
> 
> > Anyway, here's another more troubling issue. After I did my 
> above workaround
> > to get smbmount to work, I could successfully do an "ls" on 
> the mount point
> > (/rw/tmp/smb) to show the files in the share. That's good. 
> Now to test
> > reliability, I UN-shared the remote Samba share and tried 
> to "ls" the mount
> > point again. This time I got a "invalid slot" error. Note 
> that when I try
> > this reliability test on a regular Debian-Sarge box (i.e. 
> not a Soekris box
> > running Voyage Linux), I do NOT get an error when I run 
> "ls"; instead it
> > just times out after a few seconds. 
> >   
> Compare the module lists (lsmod) in voyage and sarge box.  Find out 
> words like smb and cifs. 
> Moreover, compare the smbclient version and your mount 
> command as well.  
> I would like to know if it is problem in smbfs or cifs kernel module. 
> 
> > Furthermore, when I RE-shared the share and tried "ls" on 
> the Soekris box, I
> > still got an "invalid slot" error. In contrast, on my 
> regular Debian-Sarge
> > box, "ls" correctly shows the files in the share after I 
> RE-share the share.
> > In other words, the Debian-Sarge box recovers from a 
> temporary disconnection
> > of the share after mounting it but the Voyage Linux Soekris 
> box does not.
> > I've googled "invalid slot" to death and I can't find 
> anything helpful. I
> > suspect that it might have something to do with the kernel 
> configuration of
> > Voyage Linux versus the kernel configuration of "out-of-the-box"
> > Debian-Sarge Linux. Any suggestions????
> >
> > Cheers,
> > Joe
> >
> >   
> -- 
> 
> Regards,
> Punky
> P U N K N ! X  . c o m
> Technology + Lifestyle
> (http://www.punknix.com)
> 
> Voyage Linux
> (http://www.voyage.hk/software/voyage.html)
> 
>