Guillaume Cottenceau wrote: > > Ron Stodden <[EMAIL PROTECTED]> writes: > > > > > 1. The nfs-utils rpm is still not being installed, even though > > > > nfs-utils-clients is. > > > > > > Sounds normal since one is for server us, the other for client > > > use. > > > > Oh dear, this is NOT true. nfs-utils contains all the nfs utils which > > includes > > exportfs. Without exportfs you cannot set up either a client or a > > server for > > networking. exportfs is a necessary utility for any networked PC. It > > makes the > > "shares" (nominated directories) as specified manually by the user in > > /etc/exports available to specific peer and server machines on the > > network. >
> I'm not convinced "exportfs" is needed at all for client > operation... The man reports "exportfs - maintain list of NFS > exported file systems". It also says: > > The exportfs command is used to maintain the current table of > exported file systems for NFS. This list is kept in a separate > file named /var/lib/nfs/xtab which is read by mountd when a > remote host requests access to mount a file tree, and parts of > the list which are active are kept in the kernel's export table. > > Why do you say the opposite? Any fact/anything? Huh?? Opposite?? Servers are not the only things that want to export parts of their file systems. Clients must do so all the time to other clients and to servers. For a server (or another client) to download anything to a client on the same LAN, the _CLIENT_ must tell (ie export) to the server all the places to be accessible to the server and the permitted access modes. This requires exportfs to be available on the client, hence the nfs-utils RPM to be installed, which currently it is not. Oh, dear... It's very simple. Crystal clear now? -- Ron. [au]
