[lug] Mounting a filesystem over SSH

[D. Stimits]

Ben Luey wrote:

> That's really awesome. But I'm having two problems with it. I have
> mandrake 9.0, with a custom kernel compile called 2.4.19-16mdkcustom. I
> run configure with --with-kernel=2.4.19-16mdkcustom and it compiles fine,
> but the module lufs won't load because it claims to be compiled against
> 2.4.19-16mdk and not 2.4.19-16mdkcustom. I think this is because

I would bet that your kernel source toplevel Makefile has "EXTRAVERSION 
= -16mdkcustom"...it won't care about the sym link. Editing EXTRAVERSION 
to keep compiles of the same kernel from colliding is common practice.

D. Stimits, stimits AT attbi.com

>
> /lib/modules/2.4.19-16mdkcustom/build is a symlink to
> /usr/src/linux-2.4.19-16mdk/. If I run insmod -f lufs.o to force loading
> the modules, the module loads -- is this bad, or is it just confused about
> the version, how can I get it to automatically load?. I can mount ftp with
> no problem (that's great). When I try to use lufsmount on an ssh volume, I
> get
>
> ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory
> Write failed: Broken pipe [5093](atomic_read)read failed!
> [5093](connect)failed to read version! [5093](slaveHandler)couldn't
> connect! ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or
> directory Ben Luey lueyb at jilau1.colorado.edu On 18 Nov 2002, Chris Riddoch
> wrote: Write failed: Broken pipe [5097](atomic_read)read failed!> Ever
> wanted to mount a filesystem over ssh? [5097](connect)failed to read
> version!> [5097](slaveHandler)couldn't connect!> Here's a *very* nice tool
> allowing you to do something like this: ssh_askpass:
> exec(/usr/lib/ssh/ssh-askpass): No such file or directory> Write failed:
> Broken pipe> lufsmount sshfs://username@host/ /mnt/point
> [509a](atomic_read)read failed!> [509a](connect)failed to read version!>
> You can then cd to /mnt/point and muck with things there, remotely. Of
> [509a](slaveHandler)couldn't connect!> course, you've got the overhead of
> ssh on top of the network
>
> I don't know if this is related to the module or something else... any
> ideas?
>
> Thanks,
>
> Ben
>
>
>
> >http://lufs.sourceforge.net/lufs/
>
>
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>