** Assignment # 4 **
Sharing Files
Journals due: No later than Tuesday, June 15th, 1999.
The following assignments will involve cooperative tasks with other teams in the
class. System administrators commonly have their areas of responsibility overlap and must
be able to deal with these issues in a professional manner.
In an effort to scale down the amount of work and to respect the firewall
rules, your team will only have to interact with teams that are using the same
firewall/gateway. In short, all the "zero" teams (using IP addresses in the 192.168.0.* network,
or those that are in the Majors lab)
will work together and all of the "one" teams (using IP addresses in the 192.168.1.* network,
or those that are in the Grad lab) will work together.
Part 1: Practice with NFS!
- Create a series of directories on your Linux and Solaris machine with the following structure.
/sysadmin/linux/teamA
/sysadmin/solaris/teamA
/sysadmin/linux/teamB
/sysadmin/solaris/teamB
.
.
.
/sysadmin/linux/teamZ
/sysadmin/solaris/teamZ
Substitute the "A..Z" with the appropriate team numbers in your group.
For the "zero" teams, you will use team numbers 1, 2, 4, 5, 6 and 8. For the "one" teams, you
will use team numbers 9, 10, 11, 12, 13 and 14.
- Create an account named "linux" on your Linux machine with no password.
- Create an account named "solaris" on your Solaris machine with no password.
- Change the home directory of your "linux" account to be your
appropriate directory (e.g., Team 1 would place "linux"'s home
directory and files in /sysadmin/linux/team1).
- Change the home directory of your "solaris" account to be your
appropriate directory (e.g., Team 1 would place "solaris"'s home
directory and files in /sysadmin/solaris/team1).
- With the aid of the other five teams in your group ("zero" or "one"), mount their respective
/sysadmin/OperatingSystem/team*N* directories onto your machine. Notice this will
take coordination and changing of various system files to make sure
permissions are correct.
** DO NOT SHARE ROOT PASSWORDS! (it is not required) **
When you are all done, I should be able to log in as "linux" on
ANY of the UNIX machines and access all six of the "linux" home
directories, as well as the six "solaris" directories. This means having the ability to read/write/execute
files from any twelve of the directories. Set it up so that the "solaris"
user name acts the same way. In other words, if I log into, say, team 12's Solaris machine as
"linux" then my home directory will be /sysadmin/linux/team12. As user
"linux" I will have read/write access to all files and directories in my
home directory as well as any of the other directories from other teams in
my group (/sysadmin/linux/team9, /sysadmin/solaris/team9, /sysadmin/linux/team10,
/sysadmin/solaris/team10, etc.).
The NFS mounts should survive reboots.
Reference: Chapter 5 in ESA.
Part 2: Sharing with NT!
- Create an account named "nt" on your NT machine with no password.
- Create a common home directory for your NT "nt" account:
\sysadmin\teamA
\sysadmin\teamB
.
.
.
\sysadmin\teamZ
Substitute the "A..Z" with the appropriate team numbers in your group.
For the "zero" teams, you will use team numbers 1, 2, 4, 5, 6 and 8. For the "one" teams, you
will use team numbers 9, 10, 11, 12, 13 and 14.
- Change the home directory of your "nt" account to be your
appropriate directory (e.g., Team 1 would place "nt"'s home
directory and files in \sysadmin\team1).
- Set up five network shares on your NT machine so that new drive
letters get assigned to the five other NT machine's "team"
directory in your group. For example, on Team # 4's NT machine, you would have
drive D: assigned to \sysadmin\team1, E: -> \sysadmin\team2, etc.
** DO NOT SHARE ADMINISTRATOR PASSWORDS! (it is not required) **
When you are all done, I should be able to log in as "nt" on
any of the NT machines and access all six of the "nt" home
directories via the appropriate drive letter or share name.
The permissions should be set up so that files and directories can
be created in any six of the home directories.
The drive mappings
should survive reboots.
Reference: Page 148 in EWNTSA.
Don't forget if you need help to contact me or the class assistants.