Tiny Core Extensions > TCE Q&A Forum

nfs questions?

(1/5) > >>

bigpcman:
I'm trying to get nfs to work on tc2rc1. I've installed the nfs_utils and modified the exports file to include:
/home/tc 192.168.0.114(rw,insecure,no_root_squash)

I started nfs using the jwm menu and see that portmap, rpc.statd and rpc.mountd have all started. I then tried to access the server with a nfs client and receive an error message path not found after a long delay. The nfs client shows the nfs server (192.168.0.100) as part of the nfs network default LAN but that's as far as I get. I use http://192.168.0.100:/home/tc as the server address.

Note that "exportfs -a" generates error messages "can't open exports or rmtab for reading".

Any ideas would be appreciated.

Jason W:
Whem moving nfs-utils to 2.x I removed the .dep file that contained the filesystems kernel module extension and nfs server will not work without it.  I will add the filesystems extension to the info file instead since it is not needed for nfs client support, which would be probably the most common use. 

/etc/mtab is a symlink and I get that mtab error as well but all works well even with the error.

I will look at my setup when I get home to see what else needs to be done for using tc as an nfs server.  I can't remember off the top of my head.

Jason W:
I am running TC 1.x as my nfs server, and I can't see anything beyond the standard nfs configuration that I did.

bigpcman:

--- Quote from: Jason W on April 30, 2009, 07:50:13 PM ---I am running TC 1.x as my nfs server, and I can't see anything beyond the standard nfs configuration that I did.

--- End quote ---

Do you mean after "filesystems-2.6.26.tcem" is added as a dependency and installed with portmap.tce  and tcp_wrappers.tcel ?

Jason W:
Yes, filesystems-2.6.26.tcem must be loaded.

Navigation

[0] Message Index

[#] Next page