Revision as of 16:21, 29 June 2007 by Teuben
Obvious and not so obvious User changes
- your new home directory will be /homes/$USER, and is limited to 100MB and lives on backed up computers in OIT. Note that your old $USER and new GLUE $USER name don't need to be the same, but you will not be able to share data between the two. They are completely different users on a completely different computer set. This means all data disks will need to have their user permissions changed.
- your web space is not in ~/public_html but ~/../pub. The URL would be http://www.glue.umd.edu/~teuben .
- from your $HOME directory, there are 4 directories above: home, backup, mail and pub.
- authentication is done via kerberos. I could ssh from everto to chara, and not need the ssh keys. But have not figured out how to setup the correct way with ssh keys to get from chara to everto. perhaps kerberos forbids this. Peter files a REQUEST on this FAQ.
- your mail is kept on glue.
Some system issues to be resolved
- there is no root access, each user that was given root permission can run "su"
- there is no rsync server running, which combined with the previous item, make our current RAID backup system a bit tedious to re-implement.
- where can things like /astromake go.
- cross-mounting all astro disks (the /n map, as well as the /backup map)
- mysql (for mediawiki and other things?)
- convert astro $USER to glue $USER permission. Kevin has a perl script.
- users who want to keep a special local home directory on a given machine?
Things we can keep
- mail server
- web server (but you cannot use $HOME/public_html, on the webserver we'll need some $USER space)
System things to remember
- partition tables on the boot disk need to be edited, but any data disks on that boot disk will need to be preserved in whatever partition type (physical vs. logical) they were initially. GLUE will use hda1/sda1 to populate with all logical partitions. The 3 remaining physical partitions are free to be used.