11-23-2005
You can do that by exporting your directory (/etc/exports). Then on the client side (your pc) you have to install a NFS software. But I also recommend SAMBA. We have been using NFS client software until I was able to convince my boss that SAMBA is better in many ways (easier, more secure and more config options).
10 More Discussions You Might Find Interesting
1. SCO
Hi,
We are testing SCO6 for an upgrade.
We currently have a SCO5.0.4 system that mounts
a remote directory on a Windows 2000 server.
The windows server has 'services for unix' installed
to enable the required directory to be mounted on the SCO system.
On SCO we run '/etc/mount -v -f NFS... (2 Replies)
Discussion started by: sidnagra
2 Replies
2. Linux
Hi,
Re-building linux server from a kickstart image on cdrom.
We have a kickstart server.
the cdrom contacins the kickstart ks.cfg file and does a NFS mount from an IP to load the iso images and other files needed during the kickstart (re-build)
Now for some reason the kickstart stops and... (2 Replies)
Discussion started by: Andrek
2 Replies
3. UNIX for Advanced & Expert Users
We recently upgraded one of our engineering servers, and now the lone UNIX box that houses older CAD files can not connect to it. I have tried every variation of mount I can find, but to no avail. Help is appreciated. Here are the specs:
Server: Windows 2003 x64 with Unix Services for Windows... (8 Replies)
Discussion started by: shatterstorm
8 Replies
4. Red Hat
Hello
Can someone please suggest how should I configure Samba to share the drive from Linux to Window server, and Windows server is in AD environment.
is this require winbind to be installed ??
Thanks, (0 Replies)
Discussion started by: bobby320
0 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
I need to mount an nfs filesystem as below.
xxx.xx.xx.xxx:/media/nss/Rocky Catherine/logs
For the above as there is space in between the name, hoping it will not mount, if i give it with double quotes as below will it work?
mount "xxx.xx.xx.xxx:/media/nss/Rocky... (2 Replies)
Discussion started by: Rockyc3400
2 Replies
6. Red Hat
Dear All,
I have an NFS Server and client. I am trying to include the ipaddress of the client in servers exports file /etc/exports.
In this case , I could not mount , saying permission denied.
But when I give * symbol in the place of ipaddress ( Global , any IPS )
it is mounting.
... (1 Reply)
Discussion started by: jegaraman
1 Replies
7. UNIX for Advanced & Expert Users
Hi,
I would like to know how can we mount a directory using nfs v4 ?
When I use the below command, I am not sure what nfs version am using to mount the directory.
mount -t <server_name>:<shared_directory> <shared_directory>.
eg:
mount -t 10.50.0.8:/home/arun/mount/share_dir... (7 Replies)
Discussion started by: arunsriniv
7 Replies
8. Red Hat
The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports
i have added the following line
/home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash)
i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (1 Reply)
Discussion started by: ainstin
1 Replies
9. Red Hat
The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports
i have added the following line
/home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash)
i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (5 Replies)
Discussion started by: ainstin
5 Replies
10. Solaris
Hi,
I am having some issues mounting NFS files.
for some reason the mount -F nfs is not being recognized..
bash-3.2# mount -F nfs -o rw 192.168.245.129:/mnt/nfs1/ /mnt
UX:vxfs mount: ERROR: V-3-20135: FSType nfs not recognized
UX:vxfs mount: INFO: V-3-20147: Usage:
mount {special |... (5 Replies)
Discussion started by: br1an
5 Replies
LEARN ABOUT REDHAT
mountd
rpc.mountd(8) System Manager's Manual rpc.mountd(8)
NAME
rpc.mountd - NFS mount daemon
SYNOPSIS
/usr/sbin/rpc.mountd [options]
DESCRIPTION
The rpc.mountd program implements the NFS mount protocol. When receiving a MOUNT request from an NFS client, it checks the request against
the list of currently exported file systems. If the client is permitted to mount the file system, rpc.mountd obtains a file handle for
requested directory and returns it to the client.
Exporting NFS File Systems
Making file systems available to NFS clients is called exporting.
Usually, a file system and the hosts it should be made available to are listed in the /etc/exports file, and invoking exportfs -a whenever
the system is booted. The exportfs(8) command makes export information available to both the kernel NFS server module and the rpc.mountd
daemon.
Alternatively, you can export individual directories temporarily using exportfs's host:/directory syntax.
The rmtab File
For every mount request received from an NFS client, rpc.mountd adds an entry to the /var/lib/nfs/rmtab file. When receiving an unmount
request, that entry is removed. user level part of the NFS service.
However, this file is mostly ornamental. One, the client can continue to use the file handle even after calling rpc.mountd 's UMOUNT proce-
dure. And two, if a client reboots without notifying rpc.mountd , a stale entry will remain in rmtab.
OPTIONS
-d kind or --debug kind
Turn on debugging for kind.
-F or --foreground
Run in foreground (do not daemonize)
-f or --exports-file
This option specifies the exports file, listing the clients that this server is prepared to serve and parameters to apply to each
such mount (see exports(5)). By default, export information is read from /etc/exports.
-h or --help
Display usage message.
-o num or --descriptors num
Set the limit of the number of open file descriptors to num. The default is 256.
-N or --no-nfs-version
This option can be used to request that rpc.mountd do not offer certain versions of NFS. The current version of rpc.mountd can sup-
port both NFS version 2 and the newer version 3. If the NFS kernel module was compiled without support for NFSv3, rpc.mountd must be
invoked with the option --no-nfs-version 3 .
-n or --no-tcp
Don't advertise TCP for mount.
-P Ignored (compatibility with unfsd??).
-p or --port num
Force rpc.mountd to bind to the specified port num, instead of using the random port number assigned by the portmapper.
-V or --nfs-version
This option can be used to request that rpc.mountd offer certain versions of NFS. The current version of rpc.mountd can support both
NFS version 2 and the newer version 3.
-v or --version
Print the version of rpc.mountd and exit.
TCP_WRAPPERS SUPPORT
This rpc.mountd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.mountd if they should be
allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:
mountd: .bar.com
You have to use the daemon name mountd for the daemon name (even if the binary has a different name).
For further information please have a look at the tcpd(8) and hosts_access(5) manual pages.
SEE ALSO
rpc.nfsd(8), exportfs(8), exports(5), rpc.rquotad(8).
FILES
/etc/exports, /var/lib/nfs/xtab.
AUTHOR
Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others.
25 Aug 2000 rpc.mountd(8)