How Do I Mount Remote Hard Disks?

[Flash]

I avoid the difficulty of making two computers talk to each other by transferring the files to a rewriteable CD or DVD, or a USB pen drive. This approach is not a long-term solution, and not all computers will have the necessary hardware for it, but it is a quick and dirty solution for when you occasionally need to transfer a few files.

[ozboomer]

I've been trying to do something with all this just now... with no joy at all.

Just unpack the binaries and kernel modules into /root/my-applications/nfs

rename mount to mount-FULL and put that into /root/my-applications/bin

Doing that broke my startup disk mount scripts, although I don't know how, considering I only call 'mount' and not mount-FULL... As soon as I removed /root/my-applications/mount-FULL and umount, all my disks appeared again on the next reboot.

Additionally, when I entered the 'server' commands into rc.d/rc.local, viz:

/root/my-applications/nfs/rpc.portmap
...rpc.mountd
...rpc.nfsd
...rpc.lockd
...rpc.rquotad

...each of the programs complained about no such directory, /var/lib/nfs (as well as there not being any rpc.rquotad at all).

So, it seems we'll have to try building a .tgz, .rpm, etc that gets unpacked into the correct, conventional locations in RAM disk at boot time and we'll try it again.

[Guest]

Hang on I'll give it a whirl on a fresh pup001 file with a kernel with nfs client\server modules compiled in

[ozboomer]

Hang on I'll give it a whirl on a fresh pup001 file with a kernel with nfs client\server modules compiled in

Ok.. I just tried unpacking and setting-up the Slackware 9.1 images... and, after setting files to executable (doing all my un/packing on Win98 removed some of the attributes, I think) and building a .gz file which I unpacked into the correct dirs. on Puppy 1.0.4, I had the following:

rpc.portmap - ran and is in the 'ps' list
rpc.mountd - ran without displayed error but created no 'ps' entry
rpc.nfsd - ran without displayed error but created no 'ps' entry
rpc.statd - ran and is in the 'ps' list
rpc.lockd - ran but terminated with the error -
lockdsvc: Function not implemented

I REALLY don't know what I'm doing here... but at least I have backups that I can roll back to after tonight

FYI...

[Guest]

Ok I missed the lib required form e2fsprogs-1.35

libuiid.so.1.2 which needs to be symlinked to libuuid.so.1
libblkid.so.1.0 which needs to be symlinked to libblkid.so.1

Now I mount a share a ok.....now to export one

[ozboomer]

Now I mount a share a ok.....now to export one

Yaaay! Congrats! See how it goes... Everything crossed here

[Guest]

ok we have success

Modded the slackware script, has a variable that point to the root of where the nfs binaires are

ie by default the tar file has all the binaries in
/root/my-applications/nfs

so NFS_PATH=/root/my-application/nfs

I thought I'd keep it this way to keep in clean

only the libs need will be copied to /root/my-applications/lib
exports & rpc will be placed in /etc
rc.portmap & rc.nfsd will be placed in /etc/rc.d
umount-NFS and mount-NFS are symlinks from /root/my-applications/nfs/bin to /root/my-applications/bin


One thing you will have to do is add the following line hosts.allow

Code: Select all

ALL:192.168.1.

Don't leave the period of the end........this assumes that your network is 192.168.1.0

EDIT

Youll have to change the modprobe command in /etc/rc.d/rc.nfsd to the required insmod commands.....The machine I was testing on has the client\server nfs stuff compiled in

rpcinfo & rpc.rquotad have been included

Look if you test and it goes ok (the tar file) I'll release a dotpup...so many thanks for your time in testing

[ozboomer]

ok we have success

[...]

Look if you test and it goes ok (the tar file) I'll release a dotpup...so many thanks for your time in testing

...and to you for building it up I'm crashin' into the cot for now... but I'll try it tomorrow when I get home from work.

Fanx! again for your efforts

[ozboomer]

One thing you will have to do is add the following line hosts.allow

Code: Select all

ALL:192.168.1.

[...]
Youll have to change the modprobe command in /etc/rc.d/rc.nfsd to the required insmod commands.....The machine I was testing on has the client\server nfs stuff compiled in

Well, I unpacked the file you had here into '/', placing all the files (and links) into the correct places.

I made the hosts.allow change and I had a look at the insmod commands you had earlier in this thread... but they didn't seem to do anything.

At any rate, I then had an rxvt session in /root/.etc/rc.d ... and here's what happened:-

root@tetrad # ./rc.nfsd start
Note: /etc/modules.conf is more recent than /lib/modules/2.4.29/modules.dep
modprobe: Can't locate module nfsd
Starting RPC portmapper: /root/my-applications/nfs/sbin/rpc.portmap
Starting NFS services:
/root/my-applications/nfs/usr/sbin/exportfs -r
exportfs: /etc/exports [4]: No 'sync' or 'async' option specified for export "*:/root".
Assuming default behaviour ('sync').
NOTE: this default has changed from previous versions
exportfs: could not open /var/lib/nfs/xtab for locking
/root/my-applications/nfs/usr/sbin/rpc.nfsd 8
/root/my-applications/nfs/usr/sbin/rpc.mountd
/root/my-applications/nfs/usr/sbin/rpc.lockd
lockdsvc: Function not implemented
/root/my-applications/nfs/usr/sbin/rpc.statd
root@tetrad #

Now, I'm not too flash on the modules that need to be loaded... Maybe you could do a modprobe (or whatever it is) and fling it here, so I can see what modules you have loaded... and we can try it step-by-step.

Oh... I can still ping Ok between the 2 PCs Ok, so I know the 'basic' networking is Ok.

Thx.

[Guest]

if you have a look at the archive you'll see where the module nfsd.o and the others (nfsd.o.gz) is (I haven't got access to it right now)...when you run insmod the full path name will need to be put on the command line...apart from the modprobe error all is good or your rc.local could copy nfsd.o to where the other modules are kept, run depmod -a then modprobe will work...


Just for interest my new puplet has the nfs server and client modules compiled into the kernel..see announcements....no need to insert any nfs modules