Contents
dev.vestasys.org User Information
If you're here, you probably have an account on dev.vestasys.org. This page has some basic information about your account.
Logging in
From the Internet at large, you can log into dev.vestasys.org using the ssh protocol.
You may send e-mail from dev.vestasys.org. Your e-mail address will appear as "<user>@vestasys.org".
You will not receive incoming e-mail on dev.vestasys.org. All e-mail sent to your @vestasys.org address will be forwarded to another e-mail address we have on file for you. (If you would like to change this forwarding address, ask someone in the VestaAdminGroup.)
Note that dev.vestasys.org is configured to send e-mail to the vesta-devel mailing list when you create a package, create a branch, or check in a new version. (This uses the trigger feature with the email-trigger.pl example trigger script.) If you're going to be actively working on dev.vestasys.org, you should subscribe your @vestasys.org e-mail address to the list. In the list preferences you can disable mail delivery if you normally read/post from a different address.
Vesta Repository
dev.vestasys.org runs the repository with mastership of /vesta/vestasys.org and /vesta/beta.vestasys.org. When logged in, you can perform local checkouts and checkins within those hierarchies. We ask that you create a branch for your changes rather than working directly in the main line so that others can review your work before making it official. Also, see DevelopingVesta for information and other resources for people working on the development of Vesta.
Proprietary Files
The repository on dev.vestasys.org contains some files which have licensing restrictions (such as those making up the Tru64 std_env). Please do not replicate or otherwise copy any files from dev's repository unless you are certain that they are not subject to redistribution restrictions, or that you have appropriate permission (e.g. a valid license of your own). (For example, all files used in the Linux std_env are available under a liberal license, so copying them is OK.)
If you run the replicator to explicitly move versions to the repository on pub.vestasys.org, please take care not to copy anything which should not be made available publicly.
Remote Repository Access
You cannot directly reach dev.vestasys.org's repository from the Internet at large. There is an automated replication which runs twice every hour (at :00 and :30) to copy new versions to pub.vestasys.org, from which you may then replicate them. If you are logged into dev, you can also explicitly run the replicator to push new versions to the pub.vestasys.org repository.
It is possible to replicate directly from dev.vestasys.org's repository using either ssh port-forwarding or the VestasysDotOrgVpn. Setting up either of these will require help from someone in the VestaAdminGroup. (Users with accounts to log into dev.vestasys.org probably won't need to do this, unless they need to replicate proprietary files.)
Building
dev.vestasys.org is an i386 Linux machine. You can perform Vesta builds on it for that target platform.
You may see tool invocations running on the host hive.vestasys.org. dev is a virtual machine using user-mode Linux. hive is the real host machine. Tools run faster on the host than on the virtual machine, so we want to configure dev to run tools on the host to provide better build performance. Unfortunately, we had a little problem with this that still needs to be fixed, so at the moment tools are running on dev.
Anything Else
If you need help (software installed, password reset, etc.), ask someone in the VestaAdminGroup.