From owner-p4-projects@FreeBSD.ORG Sun Nov 30 16:28:51 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id F229A1065672; Sun, 30 Nov 2008 16:28:50 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E510106564A for ; Sun, 30 Nov 2008 16:28:50 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 8A7398FC17 for ; Sun, 30 Nov 2008 16:28:50 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id mAUGSo38062947 for ; Sun, 30 Nov 2008 16:28:50 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id mAUGSojI062945 for perforce@freebsd.org; Sun, 30 Nov 2008 16:28:50 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 30 Nov 2008 16:28:50 GMT Message-Id: <200811301628.mAUGSojI062945@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Cc: Subject: PERFORCE change 153831 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2008 16:28:51 -0000 http://perforce.freebsd.org/chv.cgi?CH=153831 Change 153831 by rene@rene_self on 2008/11/30 16:28:02 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#7 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#13 integrate .. //depot/projects/docproj_nl/share/pgpkeys/tabthorpe.key#2 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd.ent#6 integrate .. //depot/projects/docproj_nl/www/en/cgi/man.cgi#5 integrate .. //depot/projects/docproj_nl/www/en/platforms/amd64/motherboards.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/Makefile#3 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/announce.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/relnotes-alpha.html#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/relnotes-amd64.html#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/relnotes-i386.html#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/relnotes-pc98.html#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/relnotes-sparc64.html#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/relnotes.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/releases/6.4R/schedule.sgml#9 integrate .. //depot/projects/docproj_nl/www/en/releases/index.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#7 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/cvsweb.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/man.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/markmail.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/message-id.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/ports.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/query-pr.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/rambler.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/web-all.xml#2 integrate .. //depot/projects/docproj_nl/www/en/search/opensearch/web.xml#2 integrate .. //depot/projects/docproj_nl/www/en/security/security.sgml#3 integrate .. //depot/projects/docproj_nl/www/share/sgml/events.xml#8 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#19 integrate .. //depot/projects/docproj_nl/www/share/sgml/release.ent#6 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#11 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -176,7 +176,7 @@ the /boot/loader.conf file and the system restarted: - vm.kmem_slze="330M" + vm.kmem_size="330M" vm.kmem_size_max="330M" vfs.zfs.arc_max="40M" vfs.zfs.vdev.cache.size="5M" ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#5 (text+ko) ==== @@ -1,6 +1,6 @@ @@ -30,7 +30,7 @@ This chapter covers the use of disks under the GEOM framework in &os;. This includes the major RAID + role="Redundant Array of Inexpensive Disks">RAID control utilities which use the framework for configuration. This chapter will not go into in depth discussion on how GEOM handles or controls I/O, the underlying subsystem, or code. @@ -50,12 +50,11 @@ How to use the base utilities to configure, maintain, - and manipulate the various RAID - levels. + and manipulate the various RAID levels. - How to mirror, stripe, encrypt, and remotely connect disk + How to mirror, stripe, encrypt, and remotely connect disk devices through GEOM. @@ -93,19 +92,19 @@ - - - - Tom - Rhodes - Written by - - - Murray - Stokely - - - + + + + Tom + Rhodes + Written by + + + Murray + Stokely + + + RAID0 - Striping @@ -134,90 +133,92 @@ the same size, since I/O requests are interleaved to read or write to multiple disks in parallel. - - - - + + + + - - Disk Striping Illustration - - + + Disk Striping Illustration + + Creating a stripe of unformatted ATA disks - Load the geom_stripe.ko - module: + + Load the geom_stripe.ko + module: - &prompt.root; kldload geom_stripe - + &prompt.root; kldload geom_stripe + - Ensure that a suitable mount point exists. If this - volume will become a root partition, then temporarily use - another mount point such as /mnt: + + Ensure that a suitable mount point exists. If this + volume will become a root partition, then temporarily use + another mount point such as /mnt: - &prompt.root; mkdir /mnt + &prompt.root; mkdir /mnt - Determine the device names for the disks which will - be striped, and create the new stripe device. For example, - to stripe two unused and unpartitioned ATA disks, - for example /dev/ad2 and - /dev/ad3: + + Determine the device names for the disks which will + be striped, and create the new stripe device. For example, + to stripe two unused and unpartitioned ATA disks, + for example /dev/ad2 and + /dev/ad3: - &prompt.root; gstripe label -v st0 /dev/ad2 /dev/ad3 + &prompt.root; gstripe label -v st0 /dev/ad2 /dev/ad3 Metadata value stored on /dev/ad2. Metadata value stored on /dev/ad3. Done. - - Write a standard label, also known as a partition - table, on the new volume and install the default - bootstrap code: + + Write a standard label, also known as a partition + table, on the new volume and install the default + bootstrap code: - &prompt.root; bsdlabel -wB /dev/stripe/st0 - + &prompt.root; bsdlabel -wB /dev/stripe/st0 - This process should have created two other devices - in the /dev/stripe - directory in addition to the st0 device. - Those include st0a and - st0c. At this point a file system may be created - on the st0a device with the - newfs utility: + + This process should have created two other devices + in the /dev/stripe + directory in addition to the st0 device. + Those include st0a and + st0c. At this point a file system may be + created on the st0a device with the + newfs utility: - &prompt.root; newfs -U /dev/stripe/st0a + &prompt.root; newfs -U /dev/stripe/st0a - Many numbers will glide across the screen, and after a few - seconds, the process will be complete. The volume has been - created and is ready to be mounted. - - + Many numbers will glide across the screen, and after a few + seconds, the process will be complete. The volume has been + created and is ready to be mounted. + + - To manually mount the created disk stripe: + To manually mount the created disk stripe: - &prompt.root; mount /dev/stripe/st0a /mnt + &prompt.root; mount /dev/stripe/st0a /mnt - To mount this striped file system automatically during the boot - process, place the volume information in - /etc/fstab file. For this purpose, a permanent mount - point, named stripe, is - created: + To mount this striped file system automatically during the boot + process, place the volume information in + /etc/fstab file. For this purpose, a permanent + mount point, named stripe, is + created: - &prompt.root; mkdir /stripe + &prompt.root; mkdir /stripe &prompt.root; echo "/dev/stripe/st0a /stripe ufs rw 2 2" \ >> /etc/fstab - The geom_stripe.ko module must also be automatically loaded during - system initialization, by adding a line to - /boot/loader.conf: + The geom_stripe.ko module must also be + automatically loaded during system initialization, by adding a line to + /boot/loader.conf: - &prompt.root; echo 'geom_stripe_load="YES"' >> /boot/loader.conf - + &prompt.root; echo 'geom_stripe_load="YES"' >> /boot/loader.conf @@ -237,8 +238,7 @@ important aspect is that information on one disk or partition is being replicated. Later, that information could be more easily restored, backed up without causing service or access - interruption, and even be physically stored in a data - safe. + interruption, and even be physically stored in a data safe. To begin, ensure the system has two disk drives of equal size, these exercises assume they are direct access (&man.da.4;) @@ -291,20 +291,21 @@ Edit the /etc/fstab file, replacing references to the old da0 with the - new device nodes of the gm0 mirror device. + new device nodes of the gm0 mirror + device. If &man.vi.1; is your preferred editor, the following is an easy way to accomplish this task: - &prompt.root; vi /etc/fstab + &prompt.root; vi /etc/fstab - In &man.vi.1; back up the current contents of - fstab by typing - :w /etc/fstab.bak. Then - replace all old da0 references - with gm0 by typing - :%s/da/mirror\/gm/g. + In &man.vi.1; back up the current contents of + fstab by typing + :w /etc/fstab.bak. Then + replace all old da0 references + with gm0 by typing + :%s/da/mirror\/gm/g. The resulting fstab file should look @@ -314,10 +315,12 @@ gm regardless. # Device Mountpoint FStype Options Dump Pass# -/dev/mirror/gm0s2b none swap sw 0 0 -/dev/mirror/gm0s2a / ufs rw 1 1 -#/dev/mirror/gm0s2d /store ufs rw 2 2 -/dev/mirror/gm0s2e /usr ufs rw 2 2 +/dev/mirror/gm0s1b none swap sw 0 0 +/dev/mirror/gm0s1a / ufs rw 1 1 +/dev/mirror/gm0s1d /usr ufs rw 0 0 +/dev/mirror/gm0s1f /home ufs rw 2 2 +#/dev/mirror/gm0s2d /store ufs rw 2 2 +/dev/mirror/gm0s1e /var ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Reboot the system: @@ -366,6 +369,7 @@ Troubleshooting + System refuses to boot @@ -537,7 +541,7 @@ specific, and will be created in the /dev/label directory. - A temporary label will go away with the next reboot. These + A temporary label will go away with the next reboot. These labels will be created in the /dev/label directory and are perfect for experimentation. A temporary label can be @@ -655,7 +659,7 @@ UFS Journaling Through GEOM - + GEOM @@ -672,7 +676,7 @@ What is journaling? Journaling capability stores a log of file system transactions, i.e.: changes that make up a complete disk write operation, before meta-data and file writes are - committed to the disk proper. This transaction log can later + committed to the disk proper. This transaction log can later be replayed to redo file system transactions, preventing file system inconsistencies. @@ -680,9 +684,8 @@ loss and inconsistencies of the file system. Unlike Soft Updates which tracks and enforces meta-data updates and Snapshots which is an image of the file system, an actual log is stored in disk - space specifically reserved for this task, - and in some cases may be stored on another disk - entirely. + space specifically reserved for this task, and in some cases may be + stored on another disk entirely. Unlike other file system journaling implementations, the gjournal method is block based and not @@ -718,8 +721,8 @@ At this point, there should be a /dev/da4 device node and a - /dev/da4.journal device node. A - file system may now be created on this device: + /dev/da4.journal device node. + A file system may now be created on this device: &prompt.root; newfs -O 2 -J /dev/da4.journal @@ -734,11 +737,12 @@ In the case of several slices, a journal will be created - for each individual slice. For instance, if ad4s1 and ad4s2 + for each individual slice. For instance, if + ad4s1 and ad4s2 are both slices, then gjournal will create - ad4s1.journal and ad4s2.journal. In the case of the command - being run twice, the result will be - journals. + ad4s1.journal and + ad4s2.journal. In the case of the command + being run twice, the result will be journals. Under some circumstances, keeping the journal on another disk @@ -749,8 +753,7 @@ before attempting to alter a file system. In most cases, the gjournal will fail if it is unable to create the actual journal but this does not protect against data loss - incurred as a result of misusing - tunefs. + incurred as a result of misusing tunefs. It is also possible to journal the boot disk of a &os; system. Please refer to the article @@ -231,9 +231,9 @@ page: Alternatively, to load the driver as a module at boot time, place the - following line in &man.loader.conf.5: +following line in &man.loader.conf.5: - if_ath_load="YES" + if_ath_load="YES" As instructed, adding the if_ath_load="YES" line to the /boot/loader.conf file will ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -2441,6 +2441,15 @@ + RELENG_6_4 + + + The release branch for FreeBSD-6.4, used only for + security advisories and other critical fixes. + + + + RELENG_6_3 @@ -2678,6 +2687,14 @@ + RELENG_6_4_0_RELEASE + + + FreeBSD 6.4 + + + + RELENG_6_3_0_RELEASE ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#13 (text+ko) ==== @@ -1,7 +1,7 @@ 800053 + + 8.0-CURRENT after the addition of Intel™ + Core, Core2, and Atom support to &man.hwpmc.4;. + 800055 + + + 8.0-CURRENT after the introduction of + multi-/no-IPv4/v6 jails. + 800056 + ==== //depot/projects/docproj_nl/share/pgpkeys/tabthorpe.key#2 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -6,13 +6,13 @@ pub 1024D/D069F2A0 2005-07-06 Key fingerprint = 62EB 68F5 C1A4 8FCE 5A87 BE22 E469 BF8C D069 F2A0 uid Thomas Abthorpe (FreeBSD Committer) -uid Thomas Abthorpe +uid Thomas Abthorpe uid Thomas Abthorpe uid Thomas Abthorpe +uid Thomas Abthorpe +uid Thomas Abthorpe +uid Thomas Abthorpe uid Thomas Abthorpe -uid Thomas Abthorpe -uid Thomas Abthorpe -uid Thomas Abthorpe sub 2048g/16752D82 2005-07-06 ]]> ==== //depot/projects/docproj_nl/share/sgml/freebsd.ent#6 (text+ko) ==== @@ -1,7 +1,7 @@ - - + + ==== //depot/projects/docproj_nl/www/en/cgi/man.cgi#5 (text+ko) ==== @@ -34,7 +34,7 @@ # Dual CGI/Plexus mode and new interface by sanders@bsdi.com 9/22/1995 # # $Id: man.cgi,v 1.172 2007/11/28 18:51:29 hrs Exp $ -# $FreeBSD: www/en/cgi/man.cgi,v 1.224 2008/11/09 18:29:53 wosch Exp $ +# $FreeBSD: www/en/cgi/man.cgi,v 1.225 2008/11/29 14:47:06 wosch Exp $ ############################################################################ # !!! man.cgi is stale perl4 code !!! @@ -164,8 +164,8 @@ %manPath = ( 'FreeBSD 7.0-RELEASE and Ports', "$manLocalDir/FreeBSD-7.0-RELEASE/man:$manLocalDir/FreeBSD-7.0-RELEASE/openssl/man:$manLocalDir/FreeBSD-ports", - 'FreeBSD 6.3-RELEASE and Ports', -"$manLocalDir/FreeBSD-6.3-RELEASE/man:$manLocalDir/FreeBSD-6.3-RELEASE/openssl/man:$manLocalDir/FreeBSD-ports", + 'FreeBSD 6.4-RELEASE and Ports', +"$manLocalDir/FreeBSD-6.4-RELEASE/man:$manLocalDir/FreeBSD-6.4-RELEASE/openssl/man:$manLocalDir/FreeBSD-ports", 'FreeBSD 8-current', "$manLocalDir/FreeBSD-8-current", @@ -174,7 +174,9 @@ "$manLocalDir/FreeBSD-7.0-RELEASE/man:$manLocalDir/FreeBSD-7.0-RELEASE/openssl/man", 'FreeBSD Ports 7.0-RELEASE', "$manLocalDir/FreeBSD-ports-7.0-RELEASE", - 'FreeBSD 6.3-stable', "$manLocalDir/FreeBSD-6.3-stable", + 'FreeBSD 6.4-stable', "$manLocalDir/FreeBSD-6.4-stable", + 'FreeBSD 6.4-RELEASE', +"$manLocalDir/FreeBSD-6.4-RELEASE/man:$manLocalDir/FreeBSD-6.4-RELEASE/openssl/man", 'FreeBSD 6.3-RELEASE', "$manLocalDir/FreeBSD-6.3-RELEASE/man:$manLocalDir/FreeBSD-6.3-RELEASE/openssl/man", @@ -464,7 +466,7 @@ 'freebsd-stable', 'FreeBSD 7.0-stable', 'freebsd-stable7', 'FreeBSD 7.0-stable', - 'freebsd-stable6', 'FreeBSD 6.3-stable', + 'freebsd-stable6', 'FreeBSD 6.4-stable', 'freebsd-current', 'FreeBSD 8-current', 'freebsd-release-ports', 'FreeBSD 7.0-RELEASE and Ports', @@ -1373,7 +1375,7 @@ } local $id = - '$FreeBSD: www/en/cgi/man.cgi,v 1.224 2008/11/09 18:29:53 wosch Exp $'; + '$FreeBSD: www/en/cgi/man.cgi,v 1.225 2008/11/29 14:47:06 wosch Exp $'; return qq{\ 
 Copyright (c) 1996-2008 Wolfram Schneider

==== //depot/projects/docproj_nl/www/en/platforms/amd64/motherboards.sgml#3 (text+ko) ====

@@ -1,6 +1,6 @@
 
-
+
 
 
 
@@ -15,8 +15,10 @@
     know about it.  Please submit new entries or correction of existing
     entries using
     send-pr(1)
-    or web form.  Please set category
-    to www.

+    or web form.  Please give details
+    on which peripherals have been tested (network, sound etc), provide
+    the output of pciconf -lv and dmesg, and set the
+    PR category to www.

 
   
@@ -632,6 +634,27 @@
     
+      
+      
+      
+      
+      
+    
+    
+      
+      
+      
+      
+      
+      
+    
+    
+      
+      
+      
+      
+      
+      
+    
+    
+      
@@ -1133,6 +1166,16 @@
     
+      
+      
+      
+      
+      
+    
+    
+      
+      
+      
+      
+      
+      
+    
+    

==== //depot/projects/docproj_nl/www/en/releases/6.4R/Makefile#3 (text+ko) ====

@@ -1,4 +1,4 @@
-# $FreeBSD: www/en/releases/6.4R/Makefile,v 1.2 2008/11/06 15:47:57 hrs Exp $
+# $FreeBSD: www/en/releases/6.4R/Makefile,v 1.5 2008/11/28 18:08:16 hrs Exp $
 
 .if exists(../Makefile.conf)
 .include "../Makefile.conf"
@@ -7,13 +7,13 @@
 .include "../Makefile.inc"
 .endif
 
-#DOCS=	announce.sgml
-DOCS=	relnotes.sgml
+DOCS=	announce.sgml
+DOCS+=	relnotes.sgml
 DOCS+=	hardware.sgml
 DOCS+=	installation.sgml
 DOCS+=	schedule.sgml
 
-DATA+=	errata.html
+DATA=	errata.html
 DATA+=	hardware-alpha.html
 DATA+=	hardware-amd64.html
 DATA+=	hardware-i386.html
@@ -34,6 +34,6 @@
 DATA+=	relnotes-powerpc.html
 DATA+=	relnotes-sparc64.html
 
-DATA=	docbook.css
+DATA+=	docbook.css
 
 .include "${WEB_PREFIX}/share/mk/web.site.mk"

==== //depot/projects/docproj_nl/www/en/releases/6.4R/announce.sgml#2 (text+ko) ====

@@ -1,13 +1,327 @@
 
-
+
 ]>
 
 &header;
 
-
Not yet announced.

+  
The FreeBSD Release Engineering Team is pleased to announce the availability
+    of FreeBSD 6.4-RELEASE.  At this time 6.4-RELEASE is expected to be the
+    last of the 6-STABLE releases.  Some of the highlights:

+
+  
    
+    
  • New and much-improved NFS Lock Manager (NLM)
+      client
    • 
+    
  • Support for the Camellia cipher
    • 
+    
  • boot loader changes allow, among other things, booting
+      from USB devices and booting from GPT-labeled devices with
+      GPT-enabled BIOSes
    • 
+    
  • DVD install ISO images for amd64/i386
    • 
+    
  • KDE updated to 3.5.10, GNOME updated to 2.22.3
    • 
+    
  • Updates for BIND, sendmail, OpenPAM, and others
    • 
+  

+
+  
For a complete list of new features and known problems, please see the
+    online release notes and errata list, available at:

+
+  
+
+  
For more information about FreeBSD release engineering activities,
+    please see:

+
+  
http://www.FreeBSD.org/releng/

+
+  
The FreeBSD Security Team intends to support 6.4-RELEASE until
+    November 30th, 2010.

+
+  
Availability

+
+  
FreeBSD 6.4-RELEASE is now available for the amd64, i386, pc98, and sparc64
+    architectures.  The builds for the alpha architecture have not completed
+    yet and will be announced later.  FreeBSD 6.4-RELEASE can be installed
+    from bootable ISO images or over the network; the required files can be
+    downloaded via FTP or BitTorrent as described in the sections below.
+    While some of the smaller FTP mirrors may not carry all architectures,
+    they will all generally contain the more common ones, such as i386 and
+    amd64.

+
+  
MD5 and SHA256 hashes for the release ISO images are included at the
+    bottom of this message.

+
+  
The contents of the ISO images provided as part of the release has changed
+    for most of the architectures.  Using the i386 architecture as an example,
+    there are ISO images named "bootonly", "disc1", "disc2", "disc3", "docs",
+    and "dvd1".  The "bootonly" image is suitable for booting a machine to do
+    a network based installation using FTP or NFS.  The "disc1", "disc2", and
+    "disc3" images are CDROM-sized (700MB media) and are used to do a full
+    installation that includes a basic set of packages and does not require
+    network access to an FTP or NFS server during the installation.  In addition,
+    "disc1" supports booting into a "live CD-based filesystem" and system rescue
+    mode.  The "docs" image has all of the documentation for all supported
+    languages.  The "dvd1" image is DVD-sized and includes everything that is
+    on the CDROM discs.  So "dvd1" can be used to do a full installation that
+    includes a basic set of packages, it has all of the documentation for all
+    supported languages, and it can be used for booting into a "live CD-based
+    filesystem" and system rescue mode.  Most people will find that "disc1",
+    "disc2" and "disc3" are all that are needed if their machine does not have
+    a DVD-capable drive.  For people with machines that do have a DVD-capable
+    drive "dvd1" should be all that is required.  If you intend to install ports
+    from source instead of using the pre-built packages included with the release
+    only "disc1" is needed.

+
+  
FreeBSD 6.4-RELEASE can also be purchased on CD-ROM from several
+    vendors.  One of the vendors that will be offering FreeBSD 6.4-based
+    products is:

+
+  
    

>>> TRUNCATED FOR MAIL (1000 lines) <<<



     

     

       GigabyteGA-MA790X-DS4AMD 790X / Socket AM2Terry R. Friedrichsen
+	  (dmesg)7.0-RELEASETested with Quad-core AMD Phenom (9750), 4Gb RAM.  SATA and IDE works,
+	 on-board Ethernet flaky but additional PCI network card works fine.
+	 Sound, serial, USB, Firewire and RAID untested.
GigabyteGA-P35-DS3LIntel P35 / Socket 775Ben Kaduk
+	  (dmesg, pciconf)7.0-STABLE (May 2008)Tested with 4Gb RAM and Intel Q6600 Core 2 quad core CPU.
+          SATA/PATA and onboard network card work well, sound untested.
Gigabyte
       GA-P35-DS4
       Intel P35 / Socket 775
       Torsten Hantzsche
@@ -970,6 +993,16 @@
     

     

       SunFire X2100 M2nVidia nForce 4 / Socket 939Markus Fröhlich
+	  (dmesg, pciconf)7.0-RELEASENo problems reported.  hw.bge.allow_asf=1 needs to be added to
+	  /boot/loader.conf for the eLOM to work.
Sun
       Fire X4100
       AMD 8111/8131 / Socket 940 - 2x Opteron
       Vivek Khera

     

       TyanTiger K9HE (S3970)ServerWorks BCM5785 (HT1000) / AMD Socket F (1207)Chris Shenton
+	  (dmesg, pciconf)7.0-RELEASE and 7-STABLE (June 2008)On board NICs, video and SATA work well.  Tested in a Tyan Transport GT20
+	  (B3970-U) server.
Tyan
       Tomcat h1000S (S3950)
       Broadcom HT-1000 / Socket AM2
       Philipp Wuensche
@@ -1214,6 +1257,17 @@
 	  supported under ndis.  Modem and flash card reader not supported.
     

     
SonyVaio VGN-TZ31WN/BGavin Atkinson
+	  (dmesg, pciconf)7.0-STABLE-200807Wired network, sound and video work fine, Xorg works nicely.  Camera,
+	  bluetooth, fingerprint reader and built in modems untested.  Wireless
+	  network card works with iwn(4) driver from CURRENT so should work in
+	  7.x when the driver is MFC'd.

       Toshiba
       A135-S4517
       Jeff Palmer