NFS - Revision history

imported>Huston at 15:35, 26 July 2013

2013-07-26T15:35:45Z

← Older revision		Revision as of 15:35, 26 July 2013
Line 3:		Line 3:

	== Basics ==		== Basics ==
	All department machines mount /u from ~~a [http://www.netapp.com NetApp] filer~~ which has redundant drive systems and is [[Backups\|backed up]] ~~nightly~~ (as well as having [[Backups#Snapshots\|snapshots]]). Many machines have local disk, either excess left over after the install of the OS, or extra disks installed, which are usable as [[Scratch disks\|scratch space]]. These scratch disks are setup as automounts, so that accessing the /scr1 disk of Coma from any other machine is as simple as typing '<tt>cd /scr/coma1</tt>' and it will be mounted for you.		All department machines mount /u from an OIT server which has redundant drive systems and is [[Backups\|backed up]] to protect against catastrophic failure (as well as having [[Backups#Snapshots\|snapshots]]). Many machines have local disk, either excess left over after the install of the OS, or extra disks installed, which are usable as [[Scratch disks\|scratch space]]. These scratch disks are setup as automounts, so that accessing the /scr1 disk of Coma from any other machine is as simple as typing '<tt>cd /scr/coma1</tt>' and it will be mounted for you.

imported>Huston at 16:53, 21 May 2007

2007-05-21T16:53:52Z

@@ Line 1: / Line 1: @@
-{{oldfaq|NUM=10}}
+NFS stands for Network File System.  It is the protocol used to mount directories and files from one computer to another so that they appear to be on the target.
 #Since we cannot verify if you have all the latest security patches and precautions installed on your home PC we cannot allow a possibly insecure machine to mount a secure resource.
-#The data between your PC and our network will not be encrypted which means anyone can eavesdrop on any of your NFS chatting.
+== Basics ==
-#OIT does not allow mounting between subnets unless it is to specific machines. They will not consider 100 separate request for Dormnet connectivity to other secure networks. In fact I would be surprised if they allowed it at all since they consider Dormnet inherently insecure. Other home based PCs could be even worse.
+All department machines mount /u from a [http://www.netapp.com NetApp] filer which has redundant drive systems and is [[Backups|backed up]] nightly (as well as having [[Backups#Snapshots|snapshots]]).  Many machines have local disk, either excess left over after the install of the OS, or extra disks installed, which are usable as [[Scratch disks|scratch space]].  These scratch disks are setup as automounts, so that accessing the /scr1 disk of Coma from any other machine is as simple as typing '<tt>cd /scr/coma1</tt>' and it will be mounted for you.

imported>Huston: NFS Mounting moved to NFS

2007-05-21T16:43:30Z

NFS Mounting moved to NFS

← Older revision	Revision as of 16:43, 21 May 2007
(No difference)

imported>Lkoven at 22:47, 2 May 2007

2007-05-02T22:47:29Z

← Older revision		Revision as of 22:47, 2 May 2007
Line 3:		Line 3:
	your home PC or one in the dorms:		your home PC or one in the dorms:

	a. Since we cannot verify if you have all the latest security patches and		#Since we cannot verify if you have all the latest security patches and precautions installed on your home PC we cannot allow a possibly insecure machine to mount a secure resource.
	precautions installed on your home PC we cannot allow a possibly insecure		#The data between your PC and our network will not be encrypted which means anyone can eavesdrop on any of your NFS chatting.
	machine to mount a secure resource.		#OIT does not allow mounting between subnets unless it is to specific machines. They will not consider 100 separate request for Dormnet connectivity to other secure networks. In fact I would be surprised if they allowed it at all since they consider Dormnet inherently insecure. Other home based PCs could be even worse.

	b. The data between your PC and our network will not be encrypted which means
	anyone can eavesdrop on any of your NFS chatting.

	~~c. CIT~~ does not allow mounting between subnets unless it is to specific
	machines. They will not consider 100 separate request for Dormnet
	connectivity to other secure networks. In fact I would be surprised if they
	allowed it at all since they consider Dormnet inherently insecure.
	Other home based PCs could be even worse.

imported>Lkoven: New page: {{oldfaq|NUM=10}} There are several reasons you can't NFS mount your Peyton home directory (/u/username) to your home PC or one in the dorms: a. Since we cannot verify if you have all th...

2007-05-02T16:04:10Z

New page: {{oldfaq|NUM=10}} There are several reasons you can't NFS mount your Peyton home directory (/u/username) to your home PC or one in the dorms: a. Since we cannot verify if you have all th...

New page

{{oldfaq|NUM=10}}
There are several reasons you can't NFS mount your Peyton home directory (/u/username) to
your home PC or one in the dorms:

a. Since we cannot verify if you have all the latest security patches and
precautions installed on your home PC we cannot allow a possibly insecure
machine to mount a secure resource.

b. The data between your PC and our network will not be encrypted which means
anyone can eavesdrop on any of your NFS chatting.

c. CIT does not allow mounting between subnets unless it is to specific
machines. They will not consider 100 separate request for Dormnet
connectivity to other secure networks. In fact I would be surprised if they
allowed it at all since they consider Dormnet inherently insecure.
Other home based PCs could be even worse.