Be sure you have read chapter 3 and 6 in the textbook. Also read all of this document before starting to work.
For this assignment, each group is to install Fedora Core 2 on one of ``our'' machines in HAS 200 and do some minimal setup. I've tried to assign people to groups in such a way that each group contains people with varying levels of experience installing and running Linux. It might be tempting to put the person with the most experience in charge, but you will collectively learn more if you instead give the people with less experience a chance to learn by doing. Also, as an experiment in doing things ``the right way'', each group should designate a console operator (someone to sit in front of the machine and operate the keyboard and mouse) and a scribe (someone to take notes on what is being done and any interesting/unusual results -- on paper or using another computer). You don't have to make these permanent roles -- today's scribe can be tomorrow's console operator -- but you should be sure they're always filled when you're installing or administering your system.
Below is a table of group assignments showing group members and the hostnames and IP addresses I want you to use. Hostnames are not case-sensitive as far as I know, but if you capitalize as in this table you will be consistent with Dr. Howland's grand master scheme, which is a good thing.
The machines we will use are in HAS 200, just to the left of the door, labeled ``CSCI 3291 Group 1'', ``CSCI 3291 Group 2'', and ``CSCI 3291 Group 3''. They are connected to Trinity's network by way of the router currently sitting on top of Group 3's CPU. The idea is to have these machines form a subnetwork, using the router as a gateway to the outside world.
For this assignment, your mission is install enough of Linux to get a system that boots, is able to communicate over the network, and run graphical applications. Do this by running FC2's installer (by booting from the first of the installation CDs). If you already have a set of installation CDs for FC2, feel free to use them; I also have two sets of CDs, which I will leave in my mailbox in the department office for any of you to pick up.
For the most part you should be able to just accept the installer's defaults, but here are some tips on when to take the defaults and when to do something else.
Once you have a running system, use command-line commands to create a user account for each person in the group (you decide about usernames -- as far as I know there aren't obvious advantages to using your Trinity usernames) and for me (username blm). Make a home directory for each user in /home. (Hint: useradd and passwd may be helpful. If you make a mistake, userdel may also be a help.)
Once you have user accounts set up, define a group (you make up the name) that includes all of you, but not me, as members. (Hint: groupadd and usermod may be helpful. If you make a mistake, groupdel may also be a help.)
Each user should then log in, confirm that his account works, and experiment with creating files with a group owner of the new group.
Briefly describe your group's experiences with the above steps: What non-default choices did you make (e.g., using static IP addresses rather than DHCP)? Were there any problems? If so, what did you do to resolve them? (And of course, you won't answer any of these questions ``I don't remember,'' because you have a group scribe taking notes, right?)
Also tell me what root password you assigned (in case I need it to check something you've done -- but I won't make changes without asking the group unless there's some kind of emergency), plus what password you assigned for the blm account (which I will probably change).
Briefly describe (1) your role in the installation process and (2) anything interesting you discovered about your (non-root) account (e.g., one person appears to have discovered that his group's system enforces rules presumably intended to make passwords hard to guess).