Puppy Linux Discussion Forum

[mikeb]

This is a simple!! guide to setting up NFS file sharing on puppy using the kernel mode drivers.
Tested on puppy 4.12, 4.12 retro, 2.12 and 2.02..no additional dependancies should be required.
It is a manual process that requires a little familiarity with the linux and puppy file system so not suitable as a pet package but perhaps in the future a simple gui setup could be made along the lines of the one for pcurlftpfs included with puppy.

There are 2 parts ...the kernel modules and the software to run NFS.
If you are running puppy 2.xx you already have the modules (assuming zdrv is present in some cases)...skip part 1.
Puppy 3 may have the modules, new puppies are going to include as before.

1) For puppy 4.xx download and extract the appropriate archive to '/'.(the 2.6.25.16 modules are now a pet )
Then run 'depmod' in a terminal to register the added modules.
note...the retro modules are from an earlier puppy but load and run ok if the modprobe -f option is used.

2) Download and extract to '/' the 'common' archive.

3) Decide what you wish to share and add to or edit /etc/exports
for example

[Béèm]

Not suitable for woof then?

[mikeb]

Ok here are some updates courtesy of Patriot :0

I have posted them separately as the start up scripts are only in my common package above so these could be added afterwards if the update is needed. As far as I know this has nfs 4 support which I believe can handle mixed types of filesystem shares amongst other this so may be useful to some

mike

[DC]

Hi Mike,
Thanks very much, Works very well.
I tried it between two copies of Puppy 4.21
Alough it might be obvious that a mounted remote drive works the same as a local drive it still feels like applied magic
all normal fuctions seem to work i.e command prompt, pfind etc

And my next problem
I could not get it to run under SMP Puppy 4.20 as a client
Did you complie the nfs modules for 2.6.25.16 ?
If you did could I get a copies to try compling them for SMP.

Thanks again

DC

[mikeb]

Oh good.

No tempestuous did...thee efficient star.

Are the nfs modules definately not there ie can you modprobe nfs/nfsd ?

Otherwise whoever compiled that kernel would be the one to approach...I did try one of the smp versions recently and remember seeing the modules...
puppy-k26291smp-4.2.iso
(said he..cannot mount the sfs from here to double check )

mike

[mikeb]

Ok Beem I give in..where do I get woof from?

mike

[Patriot]

Hmmm .....

I have a need for NFS server recently for whacking some old routers and your super simple guide here has helped save me a bunch of time .....

Anyway, I'm still on k2.6.21.7 mostly ... A whole bunch of modules are missing (not just the nfs ones. BTW, I just noticed there's an ext4 DEV module in there ... maybe I'll take a peek at it one of these days to see if ext4 can be backported) ... I was able to pinpoint all the required modules (based on your super simple guide here) and compile them quickly ... I've also done the latest nfs-utils-1.2.1 (Nov'09) which seems to have removed a few binaries ... Give me a holler if you'd like try these new ones .....

Thanks to your super simple guide here I could get the NFS server up and running in minimum time ..... though honestly, I'm more comfortable with samba shares ...


Rgds

[mikeb]

Oh kool.....well I do like the simplicity of NFS.
I just got the NFS client working from windows via microsofts own UNIX package. Although its huge you can selectively install just the client or client and server of which the core is a handful of small binaries...I could make a reduced set of just whats needed and reg files but MS might object . The control applet is larger and does not work if Internet Explorer is removed (but mshta is a major security hole anyway) but everything can be setup via the cmd console anyway.) It runs as a service and connected itself without any fiddling! I'm still trying to understand their authentication mechanism but can map a network drive anonymously read only which gives transparent explorer access and streaming media...something which ftp netdrive could not. Indeed again its simpler than samba and pretty much unknown to hackers and such.
Basically free file networking linux to linux to windows
I use internet/ipp printing for that side.

The modules for 2.6.21 where hijacked from puppy 2.17 and have to be loaded by -f. If you have a proper set would you mind uploading them here to complete the set. I believe newer puppies now include the full set again. And the updated utilities perhaps

I'm not sure what the rush is with ext4 since it has no significant benefits to normal systems for some time to come but hey...

Thanks for your input and glad my distructions worked

mike

[DC]

As requested for the above
these are howto's I wrote for myself to remind me when doing a new install.
this is for kernal 2.6.25.16. (puppy 4.2, 4.21 etc)
obviously change things to suit

First the server;

# install
NFS-modules-k2.6.25.16.pet

# then the command (to register modules)
depmod

# extract to /
nfs_common.tar.gz

# make a file
/etc/exports
# containing - /root (what's shared) 192.60.26.9(rw...) (client allowed share)
/root 192.60.26.9(rw,no_root_squash,no_subtree_check,sync)

# edit
/etc/host.allow
# adding (dont forget comma spaced and carriage return)
ALL: 192.60.26.9 , 192.60.26.10

# add these to /etc/rc.d/rc.local
modprobe nfsd
/etc/rc.d/rc.nfsd start

# to check if nfs is running
rpcinfo -p localhost


And the client;

# make a dir on client
/mnt/dc_server

# install
NFS-modules-k2.6.25.16.pet

# extract to /
nfs_common.tar.gz

# edit
/etc/host.allow
# adding (dont forget comma spaced and a carriage return)
ALL: 192.60.26.9 , 192.60.26.10

# add these to /etc/rc.d/rc.local
modprobe nfs
/etc/rc.d/rc.portmap start

# to check if nfs is running
rpcinfo -p localhost

# script in (this allows time for ip address to come up before mounting)
/root/startup/DCmount_nfs.sh
## poll interface eth0
while [ -z "`ifconfig | grep 'eth0'`" ]
do
sleep 3
done

mount-FULL -t nfs 192.60.26.10:/root /mnt/dc_server


Finally;
For later kernals (puppy 4.3, 4.31) just leave out the "NFS-modules-k2.6.25.16.pet" as the builds have the NFS modules enabled.

Hope it all makes sense

DC

[mikeb]

Thanks DC

well a step by step 'what I did from start to finish' is good...it's easy to focus on the nitty gritty and forget the 'not always obvious'.

[mrd]

Nothing ruins my evening more than stupid problems like this.

I'm trying to run MacPup Foxy 3 which is supposedly based on puppy 4.31.1 and booting from the live CD I can nfs mount my network share with no problems and nothing more than the standard puppy mount-Full -t nfs -o rw,nolock 10.10.55.201:/MRD_FILES /mnt

This will not work once the install is done in a lin n win config. Everything else works fine, but when I try to mount I get "mount: RPC: Program not registered"

I can load the nfs modules by hand and see them loaded with lsmod and I can add the nfs_common.tar files and still have the same results.

I've had a long week and really just want this to work. I also tried to copy the other random looking z098098098234.sfs file off of the iso in case that was needed, but no luck there either.

[mikeb]

So sunrpc loaded?
Pretty sure the nfs modules should get included with a full install...maybe a depmod needed but unlikely.
Is
/etc/rc.d/rc.portmap start
still being run?
I usually have this in /etc/rc.d/rc.local (this gets cleared with an install and client will not run without it.
Also check yer /etc/exports and other files in /etc still are still correct and present...again install uses a pristine /etc folder.



regards mike

[mrd]

Something worked! But I'm not sure what because it seems like the /etc/files are the same as with the LiveCD...

Thanks for the help!

[mikeb]

I wonder...perhaps your shared folder was not mounted...takes a couple of goes for me

well anyway glad its working ok

mike

[mhanifpriatama]

Is there someone who has managed to use nfs with Lucid puppy? It has different kernel.