From owner-svn-doc-all@freebsd.org Fri Aug 25 19:38:45 2017 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17549DDFF56; Fri, 25 Aug 2017 19:38:45 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E589D6E1A6; Fri, 25 Aug 2017 19:38:44 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v7PJcirL039132; Fri, 25 Aug 2017 19:38:44 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v7PJciGM039131; Fri, 25 Aug 2017 19:38:44 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201708251938.v7PJciGM039131@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Fri, 25 Aug 2017 19:38:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50720 - head/en_US.ISO8859-1/htdocs/internal X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/internal X-SVN-Commit-Revision: 50720 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Aug 2017 19:38:45 -0000 Author: gjb Date: Fri Aug 25 19:38:43 2017 New Revision: 50720 URL: https://svnweb.freebsd.org/changeset/doc/50720 Log: Conform to FDP style guidelines. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/internal/machines.xml Modified: head/en_US.ISO8859-1/htdocs/internal/machines.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/machines.xml Fri Aug 25 19:28:32 2017 (r50719) +++ head/en_US.ISO8859-1/htdocs/internal/machines.xml Fri Aug 25 19:38:43 2017 (r50720) @@ -5,142 +5,139 @@ ]> - - &title; + + &title; - $FreeBSD$ - + $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.

+

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.

+

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

-

Developer FreeBSD.org hosts

+

Developer FreeBSD.org hosts

-

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

+

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

- - - - - - - - - +
HostOSTypePurpose
+ + + + + + + + - + + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + - - - - - - + + + + + + + +
HostOSTypePurpose
eris10-STABLEia64Reference machine.
eris10-STABLEia64Reference machine.
flame11-STABLEsparc64Reference machine.
flame11-STABLEsparc64Reference machine.
freefall12-CURRENTamd64Shell Logins.
freefall12-CURRENTamd64Shell Logins.
ref[12|11|10]-amd64X-STABLEamd64Reference machine.
ref[12|11|10]-amd64X-STABLEamd64Reference machine.
ref[11|10]-i386X-STABLEi386Reference machine.
ref[11|10]-i386X-STABLEi386Reference machine.
ref[12|11]-aarch64X-STABLEarm64/aarch64Reference machine.
ref[12|11]-aarch64X-STABLEarm64/aarch64Reference machine.
universe[12|11|10][a|b]X-STABLEamd64Universe build machine.
- -universe[12|11|10][a|b] -X-STABLE -amd64 -Universe build machine. - +

Hardware configurations

- - + + + + + + + -

Hardware configurations

+ + + + + -
HostHardware
freefallCheck dmesg(8).
- - - - - - + + + + - + + + + + +
HostHardware
ref[10-12]-amd64Check dmesg(8).
ref[10-11]-i386Check dmesg(8).
- -freefall -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.

- -ref[10-12]-amd64 -Check dmesg(8). - +

Administrative Policies

- -ref[10-11]-i386 -Check dmesg(8). - +

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.

-

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 - +

FreeBSD Internal Home +