DistOS 2014W Lecture 8: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
==Group 1== | ==Group 1== | ||
'''NFS:''' | |||
1) per operating traffic | 1) per operating traffic | ||
2) rpc based | 2) rpc based | ||
3) unreliable | 3) unreliable | ||
AFS: | '''AFS:''' | ||
1) design for 5000 clients | 1) design for 5000 clients | ||
2) high integrity. | 2) high integrity. | ||
==Group 2== | ==Group 2== | ||
1) more UNIX like | '''NFS:''' | ||
1) designed to share disks over a network, not files | |||
2) more UNIX like | |||
3) portable | |||
4) use UDP | |||
5) it is not minimize network traffic. | |||
6) used VNODE | |||
7) not have much hardware equipment | |||
8) later versions took on features of AFS | |||
9) stateless protocol conflicts with files being state-full by nature. | |||
'''AFS:''' | |||
1) designed to share files over a network, not disks | |||
2) better scalability | |||
3) better security. | |||
4) minimize network traffic. | |||
5) less UNIX like | |||
6) plugin authentication | |||
7) needs more kernel storage due to complex commands | |||
8) inode concept replaced with fid | |||
==Group 3== | ==Group 3== | ||
NFS: | '''NFS:''' | ||
1) cache assumption invalid. | 1) cache assumption invalid. | ||
Line 38: | Line 66: | ||
3) bad security | 3) bad security | ||
AFS: | '''AFS:''' | ||
1) cache assumption valid | 1) cache assumption valid |
Revision as of 17:27, 6 February 2014
Group 1
NFS:
1) per operating traffic
2) rpc based
3) unreliable
AFS:
1) design for 5000 clients
2) high integrity.
Group 2
NFS:
1) designed to share disks over a network, not files
2) more UNIX like
3) portable
4) use UDP
5) it is not minimize network traffic.
6) used VNODE
7) not have much hardware equipment
8) later versions took on features of AFS
9) stateless protocol conflicts with files being state-full by nature.
AFS:
1) designed to share files over a network, not disks
2) better scalability
3) better security.
4) minimize network traffic.
5) less UNIX like
6) plugin authentication
7) needs more kernel storage due to complex commands
8) inode concept replaced with fid
Group 3
NFS:
1) cache assumption invalid.
2) no locking
3) bad security
AFS:
1) cache assumption valid
2) locking
3) good security.