(a.) Significant changes to hardware and software configuration of

every internal FreeBSD machine.

(b.) Removal of references to kickme.FreeBSD.org as an available
     non-developer machine.  This was replaced with a vague reference
     to an as-need basis.

Submitted by:	msmith (a.)
This commit is contained in:
Bill Fumerola 1999-06-01 02:34:39 +00:00
parent c060260cec
commit a789699e24
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=5004

View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-01-28 06:59:23 $">
<!ENTITY date "$Date: 1999-06-01 02:34:39 $">
<!ENTITY title "The FreeBSD.org Network">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: machines.sgml,v 1.10 1999-01-28 06:59:23 mbarkah Exp $ -->
<!-- $Id: machines.sgml,v 1.11 1999-06-01 02:34:39 billf Exp $ -->
<html>
&header;
@ -25,9 +25,9 @@ available and the sorts of jobs they are being provided for.</p>
<tr>
<td>builder</td>
<td>2.2.6-stable</td>
<td>Build server</td>
<td>admins</td>
<td>4.0-current</td>
<td>Build server for -current packages</td>
<td>ports team</td>
</tr>
<tr>
@ -39,36 +39,29 @@ available and the sorts of jobs they are being provided for.</p>
<tr>
<td>bento</td>
<td>3.0-stable</td>
<td>3.0-stable package building</td>
<td>3-stable</td>
<td>3-stable package building</td>
<td>ports team</td>
</tr>
<tr>
<td>freefall</td>
<td>3.0-stable</td>
<td>3-stable</td>
<td>CVS master repository</td>
<td>committers</td>
</tr>
<tr>
<td>hub</td>
<td>2.2.8-stable</td>
<td>Mail & WWW services, tape changer</td>
<td>3-stable</td>
<td>Mail & WWW services</td>
<td>post/webmaster</td>
</tr>
<tr>
<td>kickme</td>
<td>4.0-current</td>
<td>Bleeding edge testing</td>
<td>open</td>
</tr>
<tr>
<td>paddock</td>
<td>2.2.6-stable</td>
<td>2.2.x-stable package building</td>
<td>node82-89</td>
<td>3-stable</td>
<td>Ports build cluster</td>
<td>ports team</td>
</tr>
@ -87,14 +80,14 @@ available and the sorts of jobs they are being provided for.</p>
<tr valign="top">
<td>builder</td>
<td>Intel x86</td>
<td>200Mhz Pentium Pro, 128MB mem, AHC 2940 PCI SCSI controller, 2GB Quantum
SCSI drive, 3GB IDE drive, Intel EtherExpress Pro 10/100B NIC.</td>
<td>400Mhz Pentium II, 128MB mem, NCR 53c875, 9GB IBM
SCSI drive, Winbond 100bTX NIC.</td>
</tr>
<tr valign="top">
<td>beast</td>
<td>Alpha Durango</td>
<td> 500MHz 21164A on DEC PCI64 MB, 128MB mem, NCR 53c875 SCSI
<td>Aspen Durango</td>
<td>500MHz Alpha 21164A on DEC PCI64 MB, 128MB mem, NCR 53c875 SCSI
controller, 2x4GB SCSI WIDE drives (one NetBSD/alpha, one
FreeBSD/alpha), DEC 21140 NIC.</td>
</tr>
@ -109,34 +102,25 @@ FreeBSD/alpha), DEC 21140 NIC.</td>
<tr valign="top">
<td>freefall</td>
<td>Intel x86</td>
<td>400MHz Pentium II, 256MB mem, NCR 53c875 PCI SCSI
controller, 4x4GB SCSI WIDE drives, Intel EtherExpress Pro
10/100B NIC.</td>
<td>400MHz Pentium II, 256MB mem, Adaptec AHA2940U2W PCI SCSI
controller, 2x4GB SCSI WIDE drives, 3x9GB SCSI U2W drives,
Intel EtherExpress Pro 10/100B NIC.</td>
</tr>
<tr valign="top">
<td>hub</td>
<td>Intel x86</td>
<td>400MHz Pentium II, 256MB mem, AHC 2940 PCI SCSI controller,
3x4GB SCSI WIDE drives, HP 6020i CDR, Intel EtherExpress Pro
3x4GB SCSI WIDE drives, Intel EtherExpress Pro 10/100B NIC.</td>
</tr>
<tr valign="top">
<td>node82-89</td>
<td>AMD x86</td>
<td>300MHz AMD K6/2, 64MB mem, 3GB IDE disk, Intel EtherExpress Pro
10/100B NIC.</td>
</tr>
<tr valign="top">
<td>kickme</td>
<td>AMD x86</td>
<td>187MHz K6, 64MB mem, AHC 2940 PCI SCSI controller, 4 GB SCSI
WIDE, 2GB SCSI drives, Archive Python 4-DAT changer drive,
Intel EtherExpress Pro 10/100B NIC.</td>
</tr>
<tr valign="top">
<td>paddock</td>
<td>Intel x86</td>
<td>200MHz Pentium Pro, 32MB mem, AHC 7880 on-board SCSI
controller, 9GB SCSI WIDE drive, on-board Intel EtherExpress Pro
10/100B.</td>
</tr>
</table>
<p>All machines, as a general rule, are connected at 100Mbits to the
@ -152,13 +136,11 @@ this includes changes to user accounts or filesystem layout.</p>
<p>All new user accounts must be cleared with the admin staff, <a
href="mailto:admins@freebsd.org">admins@freebsd.org</a>, and are given
only to FreeBSD developers, either in the docs, ports or general
src hacking category. The sole exception to this rule is the
testing machine, kickme.freebsd.org, for which 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. Accounts are also not given
to the general public for "vanity domain" mail or other such
uses, so please don't ask. Thanks.</p>
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. Accounts
are not given to the general public for "vanity domain" mail or
other such uses, so please don't ask. Thanks.</p>
<p>Jordan Hubbard<br>
<a href="mailto:jkh@freebsd.org">jkh@freebsd.org</a></p>