Index: head/en_US.ISO8859-1/htdocs/internal/machines.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/internal/machines.xml (revision 48113) +++ head/en_US.ISO8859-1/htdocs/internal/machines.xml (revision 48114) @@ -1,202 +1,146 @@ ]> &title; $FreeBSD$

This page documents, for those with accounts on the FreeBSD.org network, just what machine resources are currently available and the sorts of jobs they are being provided for.

For a list of SSH host keys and their fingerprints for the public FreeBSD.org machines, please see this file.

Developer FreeBSD.org hosts

These systems are available for FreeBSD developer / committer use. Reference systems can be used for build tests etc.

Host OS Type Purpose
eris 10-STABLE ia64 Reference machine.
flame 10-STABLE sparc64 Reference machine.
freefall 11-CURRENT amd64 Shell Logins.
pluto 10-STABLE ia64 Reference machine.
ref[11|10|9]-amd64 X-STABLE amd64 Reference machine.
ref[11|10]-i386 X-STABLE i386 Reference machine.
universe[11|10|9][a|b] X-STABLE amd64 Universe build machine.
-

Administrative FreeBSD.org hosts

- -

These systems perform various administrative services. Most have - restricted access.

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
HostPurpose
ftp-masterFTP Master (stage server).
skunkworksPerforce server.
svnSubversion master repository.
- -

Ports building cluster

- -

The ports building cluster is primarily managed by the Ports - Management team (portmgr).

- - - - - - - - - - - - - - - - - -
HostPurpose
beefy[1-8]Package building machines
-

Hardware configurations

Host Hardware
freefall Check dmesg(8).
ref[8-11]-amd64 Check dmesg(8).
ref[10-11]-i386 Check dmesg(8).

Machines are generally connected at 1Gbit/sec full-duplex to a dedicated switch with redundant gigabit uplinks. All systems have logged serial consoles and remote power management.

Administrative Policies

If the machine in question is "owned" by someone specific, please direct queries to them first when asking about administrative issues, this includes changes to user accounts or filesystem layout.

All new user accounts must be cleared with the admin staff, and are given only to FreeBSD developers, either in the docs, ports or general src hacking category. Accounts may be given to non-project developers if they have a specific need to test something of a truly experimental nature and need access to a FreeBSD machine for the purpose. See New Account Creation Procedure page for details on new accounts. Accounts are not given to the general public for "vanity domain" mail or other such uses. It would be a waste of time to ask. Thanks.

FreeBSD Internal Home