File Management Paper
{Your Name}
{Your Class}
{Date}
{Instructor}

File Management Paper Before we discuss how I would specify a protection scheme in UNIX® for 4990 users out of 5000 to access one file I think we need to first discuss what file management is in UNIX® and how security is implemented for this type of request. File management is a lot like file management in the DOS days of computers operating systems. Even with the early days of Windows up to Windows 3.11 file management and security were perfumed much the same way UNIX® still does it. Why? Because it works. In DOS and still in the most current version of Windows, Windows 8.1, security to files and directories is performed the same way. You have an attributed command with switches for specific action: R- Read Only, A- Archive, S- System Files, H- Hidden Using the + and – symbols before each instructs the system whether to add or remove the attribute. Example: Attrib –R Text.doc. This command will allow the file text.doc to be editable. Where in DOS and Windows upper and lowercase mean the same thing. I file called. TEXT.DOC is the same as a file named text.doc. Not so in UNIX®. A file with uppercase, DOCUMENT.TXT, or lowercase, document.txt, are two totally different files. UNIX® already provides a way for a system administrator to grant access to files and directories for other users. There are three classes of users who may have access to files and directories. They are: User (u) – the owner or creator of the file Group (g) – In UNIX® all users are assigned to one or more groups. So there can be group ownership of a file. Other (o) – These are users other than the user or the file’s group. So if we were to run the command: “ls –alg” ‘ls’ for list, ‘a’ for all files in a given directory, ‘l’ for long format and ‘g’ to