How to get NFS working in Puppy?

Message

miriam · #1 Post by **miriam** » Tue 28 Apr 2009, 11:02

Samba is useful for networking Puppy with MSWindows, but I don't have any MSWindows machines, and it is slower than nfs, which is a real disadvantage when you want to back up hundreds of Gigabytes between machines. Also Samba is kind of flaky on my machine -- sometimes it works and sometimes it doesn't and I've never been able to work out why.

I was rapt when recent Puppies introduced FTP servers that root could use, but quickly found that either gFTP or PureFTPd unpredictably refuses to transfer (or even see) certain files, which makes it useless for backing up tens of thousands of files.

What I'd like, is to be able to use nfs and all the command tools you'd expect to be able to use in Linux to treat the files exactly the same whether on one machine or the other.

Anybody know how to do it?

mikeb · #2 Post by **mikeb** » Tue 28 Apr 2009, 23:09

Ok I ran out of attachment space and also to avoid confusion I have made a how-to for kernel mode NFS
http://www.murga-linux.com/puppy/viewto ... 820#327820

MIke

miriam · #3 Post by **miriam** » Wed 29 Apr 2009, 00:55

Thanks mikeb.
Likewise if I work out anything on it in the meantime I'll post it here too.

I'd be very wary of backing up large amounts of data using ftp. I did this recently and used rox to show a count (right-click the directory and choose "count") of the files on the destination machine and the source machine. The numbers did not match. Some files that didn't transfer had stupid names (for example some began with a space character), but others looked like perfectly normal files -- name, attributes, owner, all seemed fine. It scares me that I have data sitting on a drive that is due to fail sometime soon (it is about 7 years old). I'm considering temporarily opening up the two machines and swapping the drive across so I can backup the data reliably. But Linux is supposed to have networking built into it with nfs the natural way to do it... seems such a waste to be unable to use it...

mikeb · #4 Post by **mikeb** » Wed 29 Apr 2009, 02:23

The basic client side is in puppy..its the server thats incomplete...nfsd module and getting rpc right, though rpc is needed for a reliable client it seems

mike

Arthur · #5 Post by **Arthur** » Wed 29 Apr 2009, 02:56

I've used Clonezilla successfully to copy from one hard drive to another. Succeeded in cloning the data to a newer hard drive and successfully swapped the hard drives over.

Nathan F · #6 Post by **Nathan F** » Wed 03 Jun 2009, 05:51

I may have to tackle this sometime. I just set up nfs on FreeBSD and Debian (first time ever trying it) and am amazed at how great it works. I'm pretty sure I could get the client half going with a minimum of fuss, but the server end could be problematic I suppose, what with rpc-bind to deal with.

Maybe I'll try it later this week.

Nathan

gposil · #7 Post by **gposil** » Wed 03 Jun 2009, 08:01

I have been using NFS with Puppy for a couple of months, works brilliantly. All you need is the pet below, which is the NFS daemon and rpc bindings all done.

Once installed, edit or create your /etc/exports file....
eg /root/my-documents (insecure,rw,nohide)

Then restart puppy and its away....simple as that.

The only problem you may strike is dependencies for the pet, my full hdd install had all the depends, if you need anything let me know i'll already have it.

miriam · #8 Post by **miriam** » Wed 03 Jun 2009, 10:38

Squeeee!

Thankyou.
I can hardly wait to try it.

EDIT: okay, it requires libgnutls.so.26
I've checked through Puppies 2,3, and 4 and find no version higher than libgnutls.so.12

GNU TLS library page is at http://www.gnu.org/software/gnutls/
I decided to download the latest: gnutls-2.8.0.tar.bz2 (holy smoke! 6MB -- more than half an hour on my slow dialup) and make links to it that pretend to be the 2.6 version. There seem to be some security problems with the 2.6.x versions. http://www.gnu.org/software/gnutls/security.html

Libcrypt is required to build gnutls... ftp://ftp.gnupg.org/gcrypt/libgcrypt/

uh... libgpg-error is needed to build libcrypt... ftp://ftp.gnupg.org/gcrypt/libgpg-error/

Do we detect the beginning of descent into dependency-hell here? [sigh]

Nope. [whew!]
libgpg-error compiles and installs... so does libcrypt... and (drum roll) gnutls-2.8.0 Yay! (huh? it looks like gnutls-2.8.0 is actually gnutls.so.26)

I don't know how to make them into a pet package or I'd upload them. Sorry... I really do need to look into that.

Now I just need to make the little tweaks suggested and reboot.
More later...

mikeb · #9 Post by **mikeb** » Wed 03 Jun 2009, 12:59

Thanks a bunch but I won't squeeze you.
I got as far as thinking my configuration was not correct but seemed to have everything running (using old pups and binaries) but looking forward to trying the pet

It would be a sensible puppy inclusion as curlftp is ok but has some quirks.
And if there is a windows client that would be even groovier yeah baby

regards

mike

mikeb · #10 Post by **mikeb** » Wed 03 Jun 2009, 16:41

Yes those dependancies. Looking at configs it seems some would be optional depending on required functions/security. This is the user space server....how is it started as I found nothing in etc?

I do have a collection of files for the kernel mode server in puppy 2...quite small and everything was running but I got permission denied errors trying to connect and it seemed my configs needed tweaking in the rpc area.

mike

gposil · #11 Post by **gposil** » Wed 03 Jun 2009, 21:54

Make sure the /etc/exports file is set up with your shares in the format I outlined above, then in console cd to /etc/init.d and run in this order:

./portmap start
./nfs-user-server start

To check that the server is running type rpcinfo -p, you should get something like this

# rpcinfo -p
program vers proto port
100000 2 tcp 111
100000 2 udp 111
100024 1 udp 34406
100024 1 tcp 52795
100003 2 udp 2049
100003 2 tcp 2049
100005 1 udp 672
100005 2 udp 672
100005 1 tcp 673
100005 2 tcp 673

if you have port 2049 being used by tcp and udp then it's running.

When you restart puppy the server will autostart as any script in /etc/init.d will be run with start as its argument.. Hope that explains it.

mikeb · #12 Post by **mikeb** » Wed 03 Jun 2009, 22:19

Cheers.

...do /etc/hosts.allow , /etc/host.deny and /etc/hosts need modifying?

regards

mike

gposil · #13 Post by **gposil** » Thu 04 Jun 2009, 02:04

You shouldn't need to modify the allow,deny or hosts files unless you specifically want to deny particular hosts etc or want to disable loop back in hosts.

mikeb · #14 Post by **mikeb** » Thu 04 Jun 2009, 02:32

Sucess...yay
well was very close before...used
/mnt/hda5 192.168.1.0/255.255.255.0(rw)
in /etc/exports and voila...the sample file wouldn't play ball..kept getting 'permission denied'
This is using the kernel mode fileset testing in puppy 2.12. For puppy 4.xx would probably just need nfsd kernel module as the rest is included.
Ok will further test and such

regards

mike

gposil · #15 Post by **gposil** » Thu 04 Jun 2009, 02:42

Please be aware that kernel mode nfs is not enabled in Puppy 4...so you have to enable it by adding the kernel module at boot up...then use the kenel mode nfs daemon.(Unless you have a real reason to use kernel mode instead of user space mode, I wouldn't...)

mikeb · #16 Post by **mikeb** » Thu 04 Jun 2009, 04:27

Well anything is better than using something based on one of windows biggest security holes...lol..PuppyNT4.21...
Size and speed factors....the kernel way adds up to less than 500k which is mostly the kernel modules.
I assume that the same configs will work for kernel or user implementations?
Will have to if no modules for 2.6.25 kernel.....2.6.21 mods are available.

mike

gposil · #17 Post by **gposil** » Thu 04 Jun 2009, 04:48

Yes all the same configs work whether you use kernel or user mode...

mikeb · #18 Post by **mikeb** » Thu 04 Jun 2009, 10:46

--> does a common config and successful nfs file share dance <<--

jessgwiii · #19 Post by **jessgwiii** » Fri 05 Jun 2009, 01:02

Thanks for the tips. Here is my contribution for your dependencies. I compiled them on Puppy 4.2 SMP kernel Dual Pentium III machine.

The first dependency: libgpg-error-1.7-i686.pet

The second dependency: libgcrypt-1.4.4-i686.pet

The third dependency: gnutls-2.8.0-i686.pet

I hope they work.

It won't let me attach the third file maybe there is a limit, will try on another reply. It is saying trying to upload an empty file for some strange reason, the file is not empty.

You can also make your your own pet packages, take a look at this page:

http://www.puppylinux.com/development/createpet.htm

jessgwiii · #20 Post by **jessgwiii** » Fri 05 Jun 2009, 01:13

Maybe the file is too big as it won't let me upload it! I mdo not know why but it keeps saying trying to upload an empty file. I'm sure it has something to do with limits as the file is only 3megs. Sorry I tried. Respond to this reply and I will email it to you.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

How to get NFS working in Puppy?

How to get NFS working in Puppy?

backup

Pet Packages!

The third dependency!