File Management
File Management
Student’s name
POS/355
November 19, 2012
Instructor’s Name
File Management In a system that supports 5,000 users protection and accessibility are key roles for the system. On a system of 5,000 users allowing only 4,990 users to access one file must make good use of protection as well as accessibility. Protection of files needs to be set up so that there is access given to users on a system in three different permission categories. The first is the permission to read a file. The second is the permission to write or make changes to a file. The final is the permission to run or execute a file. A UNIX system sets up three classifications for its users; an owner or user, a group, and the other. First is the owner, which is the creator of a file, or the user at a specific time of a file. A group is a class to which the user or owner belongs. A group could be a department of a company or any other type of grouping with specific members. Last, the other is the general World Wide Web audience (“Unix Protection and Permissions”, n.d.). A review of how users are set up should be understood first and permissions can then be set. A UNIX system administrator sets up each user of the system to have a unique user name, whereas the UNIX operating system identifies users with a number, known as the user identifier or UID. Users are not limited to the humans that work on the system but the system functions are considered users as well (“Practical Unix & Internet Security”, n.d.). User names have a parameter of up to eight characters in length when created. A typical scheme would be the user’s first two initials of the first name and the full last name. In instances in which there were two users with the same name, such as two Marsha Grants, adding a number can create uniqueness, for example mg1grant. Even though the user names are a convenience for administration by humans, there is still a need for a user name to be unique. Group
Student’s name
POS/355
November 19, 2012
Instructor’s Name
File Management In a system that supports 5,000 users protection and accessibility are key roles for the system. On a system of 5,000 users allowing only 4,990 users to access one file must make good use of protection as well as accessibility. Protection of files needs to be set up so that there is access given to users on a system in three different permission categories. The first is the permission to read a file. The second is the permission to write or make changes to a file. The final is the permission to run or execute a file. A UNIX system sets up three classifications for its users; an owner or user, a group, and the other. First is the owner, which is the creator of a file, or the user at a specific time of a file. A group is a class to which the user or owner belongs. A group could be a department of a company or any other type of grouping with specific members. Last, the other is the general World Wide Web audience (“Unix Protection and Permissions”, n.d.). A review of how users are set up should be understood first and permissions can then be set. A UNIX system administrator sets up each user of the system to have a unique user name, whereas the UNIX operating system identifies users with a number, known as the user identifier or UID. Users are not limited to the humans that work on the system but the system functions are considered users as well (“Practical Unix & Internet Security”, n.d.). User names have a parameter of up to eight characters in length when created. A typical scheme would be the user’s first two initials of the first name and the full last name. In instances in which there were two users with the same name, such as two Marsha Grants, adding a number can create uniqueness, for example mg1grant. Even though the user names are a convenience for administration by humans, there is still a need for a user name to be unique. Group
References: Practical UNIX & Internet Security. (n.d.). Retrieved from http://www.diablotin.com/librairie/networking/puis/ch04_01.htm Unix Protection and Permissions. (n.d.). Retrieved from http://www.mtholyoke.edu/~easokolo/unix/perm.htm