This is really only a quick sketch of a complete FAQ. Hopefull, however, I'll be able to cover the necessary basics.
Here again I would like to stress how to get help. For general Unix questions, email unixhelp@psu.edu. For help regarding software in the lab, or hardware problems in the 316 Hammond unix lab, mail ptpadmin@psu.edu.
So if you changed you access account password, the password on the machines in hammond will change as well.
The kpasswd command. For the average user (ie: not administrator) this will function exactly the same way as the passwd command. First, type in your old access acount password. The the new password twice. (To make sure you typed in it correctly.) Then, the password is changed.
It then it also changed for dialing in, or using the other public Mac/PC labs. If you have any scripts wt home ith the password it in, (like dial up scripts, or PPP connection script) don't forget to change them.
Remote login is not allowed in the classroom machines, namely h30-h60. (You're welcome to try, but face it, it ain't gonna happen.) This is done because at times classes are taught in this room, and we don't want to steal time from people using the machines.
Now, you can read mail and send mail from each of the machines. When you send mail from any of the machines, it changes your address from, say, chilly@h42.ptph.psu.edu to chilly@psu.edu. This means that all mail sent from the labs will look like it came from your access account, so all reply sent to you will go to you access acount mail box.
This mail box is normally userid@email.psu.edu, (ie: chilly@email.psu.edu for me) the POP server. When you get an access acount, it is automatically set to receive mail with the POP server, so unless you specifically changed it, you will be getting mail from the POP server.
If you want to check where your mail is going, type "ph -r $USER" at you prompt. The email: field is where mail sent to "userid@psu.edu" is being forwarded to. If this ends with email.psu.edu, the mail is going to the POP server.
If you want to read mail from the ptph machine (and you can, really, it's fine) check out reading pop mail.

What this script does, is to call the programm "popclient" to get your mail from the POP server. It deletes it from the server to save CAC resources, and copies it to your afs directory. Therefor, if you try and read your mail with Eudora from home, then all messages that you recieved at the lab will not appear. (There is a way to let the messages stay on the server, but we don't like people doing this per se, so I'm not going to tell you how to do it. Figure it out yourself if it's so important.)
Unlike some other UNIX machines, mail on the ptph lab is not stored in /usr/spool/mail or /var/spool/mail, it's stored in everyone home directory, in the subdirector access_mail. So, the enviromental MAIL variable is set to $HOME/access_mail/$USER, instead of /usr/spool/mail/$USER. So DO NOT DELETE THE access_mail DIRECTORY, YOU WILL LOSE YOUR MAIL.
Thank you.
This is idenitical to all other CAC supported labs. You have to authorize printing through any of the signature stations. (There is one in Willard, and there is one in the accounting office in the Computer Building.)
If you know MS-DOS or it's clones, these commands are fairly self-explanitory.
For the gory details, do a man whatever on them. (Don't
look at me, I use a real computer at home...) Remember, if you are copying
text file's back and forth, which you probably are, use the -a
option. This will convert DOS' stupid cr/lf combination to just lf, or
vica-versa depending which way you are going. The -a option will
also place a cntl-Z at the end of the file if you are copying it onto a
disk.
Note: when you log on, you are automatically given a token in the psu.edu cell, which is where your home directories are.
Or, for those who really want to know the answer to this question, the AFS FAQ at transarc.com will explain everything you want to know.
unix does permissions by file, AFS does permission by directory. The only unix permission bit that matters in a file on AFS is the execute bit. ie: you can only run file which are marked as executable, not matter where you are running them from.
To list the ACL (Access Control Lists) for a directory, type :
fs la directory name
For example, typing fs la ~chilly should give you :
Access list for /afs/psu.edu/users1/chilly is Normal rights: system:administrators rlidwka system:anyuser l chilly rlidwkaThis lists out the ACLs for my home directory. system:administrators and chilly would would pretty much leave alone. (Obviously, if you listed out your home directory, than chilly would be replaced with your user ID. Don't muck with it : you probably want to keep access to your files...)
(Check out the explanation of ACL in the FAQ from transarc.)
Now, because I set up a web page for myself, I added the system:anyuser acl. I gave it the l priviledge, meaning that I'm allowing anyone on the planet to access my directory -- not reading any of the files in it, but they can cd into it and list what I have inside. system:anyuser means anyone in AFS. system:authuser means only people with tokens in our cell, namely psu.edu. So if you only want people who have accounts on the machines in hammond to access your files, than use system:authuser. Unfortunatly, we are running the web server without a token, so if you want to have a home page, you need to give system:anyuser list access.
Now, if you want to create a web page, you will also need to make your
public_html directory world accessable and world readable. This can
be done by setting the ACL to rl, or read, which is a macro
for rl. Quick cookbook for setting the permissions on your
directory: