%includes; ]> &header;

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.

All host names in the FreeBSD.org domain

Host OS Purpose Owner(s)
builder 2.2.6-stable Build server admins
beast 4.0-current Alpha box for FreeBSD/alpha testing jkh
bento 3.0-stable 3.0-stable package building ports team
freefall 3.0-stable CVS master repository committers
hub 2.2.8-stable Mail & WWW services, tape changer post/webmaster
kickme 4.0-current Bleeding edge testing open
paddock 2.2.6-stable 2.2.x-stable package building ports team

Hardware configurations

Host Type Hardware
builder Intel x86 200Mhz Pentium Pro, 128MB mem, AHC 2940 PCI SCSI controller, 2GB Quantum SCSI drive, 3GB IDE drive, Intel EtherExpress Pro 10/100B NIC.
beast Alpha Durango 500MHz 21164A on DEC PCI64 MB, 128MB mem, NCR 53c875 SCSI controller, 2x4GB SCSI WIDE drives (one NetBSD/alpha, one FreeBSD/alpha), DEC 21140 NIC.
bento Intel x86 MP 2x300MHz Pentium II, 128MB mem, AHC 2940 PCI SCSI controller, 5x4GB SCSI WIDE drives, Intel EtherExpress Pro 10/100B NIC.
freefall Intel x86 400MHz Pentium II, 256MB mem, NCR 53c875 PCI SCSI controller, 4x4GB SCSI WIDE drives, Intel EtherExpress Pro 10/100B NIC.
hub Intel x86 400MHz Pentium II, 256MB mem, AHC 2940 PCI SCSI controller, 3x4GB SCSI WIDE drives, HP 6020i CDR, Intel EtherExpress Pro 10/100B NIC.
kickme AMD x86 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.
paddock Intel x86 200MHz Pentium Pro, 32MB mem, AHC 7880 on-board SCSI controller, 9GB SCSI WIDE drive, on-board Intel EtherExpress Pro 10/100B.

All machines, as a general rule, are connected at 100Mbits to the FreeBSD network (a 100Mbit network switch) unless some other reason requires that they communicate at 10Mbits.

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, admins@freebsd.org, 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.

Jordan Hubbard
jkh@freebsd.org

FreeBSD Internal Home &footer;