TiVo Community Forums Archives - NFS problem with 2.0.1

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

NFS problem with 2.0.1
(Click here to view the original thread with full colors/images)

Posted by: sbs

I just grabbed nfs-2.0.1.o from 9thtee.com to be prepared for my TiVoNET tomorrow.
Unfortunately I get an error when making insmod nfs-2.0.1.o:

nfs-2.0.1.o: kernel-module version mismatch
nfs-2.0.1.o was compiled for kernel version 2.1.24-TiVo.1
while this kernel is version 2.1.24-TiVo.2.

I have Software Version 2.0.1-001-000.

What can I do?

Posted by: cworley

quote:
Originally posted by sbs:
I just grabbed nfs-2.0.1.o from 9thtee.com to be prepared for my TiVoNET tomorrow.
Unfortunately I get an error when making insmod nfs-2.0.1.o:

nfs-2.0.1.o: kernel-module version mismatch
nfs-2.0.1.o was compiled for kernel version 2.1.24-TiVo.1
while this kernel is version 2.1.24-TiVo.2.

I have Software Version 2.0.1-001-000.

What can I do?

Use "-f" in insmod. I compiled this with their latest kernel, but it still says mismatch. To check if a module is loaded, use "cat /proc/modules".

Posted by: sjf

Ok, I have nfs-2.0.1.o loaded on BOTH my tivos. On tivo #2 I have created a /etc/exports file which contains

/var/log (rw,no_root_squash)

But when I do the following on tivo #1, I get the the response shown...

[@TiVo /var/tmp] # mount 192.168.2.52:/var/log /mnt
mount: RPC: Port mapper failure - RPC: Unable to receive

What am I doing wrong?

[This message has been edited by sjf (edited 07-19-2001).]

Posted by: mprice

Sjf,

The the nfs kernel module simply provides the NFS specific code for the VFS (Virtual File System). ie it implements the NFS read (by issuing an rpc call to the server) when a read() system call is made against a vnode on an NFS filesystem.

In order to achieve what you want, exporting a filesystem from one tivo and mounting on another, would require you to port a number of binaries. I think it would be possible, but might require quite a bit of work.

For example you would need to port:

1. exportfs binary for the server. exportfs processes the /etc/exportfs file for the kernel.

2. The portmapper, (sometimes rpc.portmap) for the server. This provides the program to port number lookup. Will be required to find out which ports the rpc.mountd and nfsd processes are listening on.

3. rpc.mountd also for the server. This deals with the mount requests, checks exports for which filesystems are exported, where to, and which flags (ro,rw etc).

4. rpc.nfsd also for the server. This is a user level process which normally jumps straight into kernel and never comes back out (ie. calls mksysdaemon() - actually I think linux might do it differently, perhaps a call to nfssvc() )

nfsd would be really easy to port, its 68 lines of code, I'm not sure how much of the kernel side has been implemented in the nfs kernel module though. Maybe cworley can comment on if he had to rip anything out.

Things like rpc.mountd also rely on libnsl, so you would need to cut out all the code which used that.

I'm basing this on the 2.4.x kernel, which is quite different from the the kernel that the tivo uses, but I'm going to guess that most of the above applies.

Obviously if I'm wrong I'm sure someone will correct and put me in my place ;-)

Cheers, Mark.