932
edits
Changes
Setting up lab page skeleton
[[Category: OPS535]][[Category: OPS535-Labs]][[Category: peter.callaghan]]
=OPS535 Lab 2=
==Purpose==
Network File System (NFS) allows you to access files on remote hosts in exactly the same way you would access local files. It was originally created by Sun Microsystem and the implementation on Linux is largely by Rick Sladkey, who wrote the NFS kernel code and large parts of the NFS server.
For more information about NFS, please refer to Chapter 14 of the online Network Administrator guide.
You should also study chapter 23 of the course text book on NFS for this Lab.
Designate vm2 as the NFS server.
==Pre-Requisites==
The pre-lab must be complete so that your virtual machines share access to a private network.
Create a new user on each of your virtual machines using your own Seneca login.
==Investigation 1: NFS Server Setup==
==Investigation 2: File ownership of new files created on NFS shares==
==Investigation 3: File creation permission and user name mapping on NFS shares==
==Completing the Lab==
You should now have a common part of the filesystem available to all three vms. Files you store there on one machine will be accessible for the other machines too. Note that this should only be available when using your internal, statically assigned addresses.
You have also explored how access permissions are used between the machines, and since this service relies on UIDs accessed on each machine, keeping them synchronized between machines becomes vital. In a future lab we will explore a service that will manage that aspect of our networks.
Follow the instructions on blackboard to submit the lab.
==Exploration Questions==
# What is the purpose of the "su -" command?
# What is the purpose of the "rpcinfo -p" command?
# What information is stored in the /etc/exports file?
# What information is provided by the "showmount -e" command?
# Did your Linux kernel have NFS support compiled in?
# What is the full path name of the nfs module file? i.e. where is it on your hard drive?
=OPS535 Lab 2=
==Purpose==
Network File System (NFS) allows you to access files on remote hosts in exactly the same way you would access local files. It was originally created by Sun Microsystem and the implementation on Linux is largely by Rick Sladkey, who wrote the NFS kernel code and large parts of the NFS server.
For more information about NFS, please refer to Chapter 14 of the online Network Administrator guide.
You should also study chapter 23 of the course text book on NFS for this Lab.
Designate vm2 as the NFS server.
==Pre-Requisites==
The pre-lab must be complete so that your virtual machines share access to a private network.
Create a new user on each of your virtual machines using your own Seneca login.
==Investigation 1: NFS Server Setup==
==Investigation 2: File ownership of new files created on NFS shares==
==Investigation 3: File creation permission and user name mapping on NFS shares==
==Completing the Lab==
You should now have a common part of the filesystem available to all three vms. Files you store there on one machine will be accessible for the other machines too. Note that this should only be available when using your internal, statically assigned addresses.
You have also explored how access permissions are used between the machines, and since this service relies on UIDs accessed on each machine, keeping them synchronized between machines becomes vital. In a future lab we will explore a service that will manage that aspect of our networks.
Follow the instructions on blackboard to submit the lab.
==Exploration Questions==
# What is the purpose of the "su -" command?
# What is the purpose of the "rpcinfo -p" command?
# What information is stored in the /etc/exports file?
# What information is provided by the "showmount -e" command?
# Did your Linux kernel have NFS support compiled in?
# What is the full path name of the nfs module file? i.e. where is it on your hard drive?