Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jan 2014 18:11:24 +0000 (UTC)
From:      Manolis Kiagias <manolis@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r43640 - in head/el_GR.ISO8859-7/books/handbook: . disks preface
Message-ID:  <201401241811.s0OIBOuW058994@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: manolis
Date: Fri Jan 24 18:11:24 2014
New Revision: 43640
URL: http://svnweb.freebsd.org/changeset/doc/43640

Log:
  Update more parts of the Greek Handbook to the latest versions
  
  Highlights:
  - 'vinum' chapter removed from build
  - Mostly untranslated 'disks' chapter replaced with the latest
    en_US version
  
  Note that the 'users' chapter still remains in the Greek Handbook
  for reference until it is updated and merged with 'basics'
  
  New revisions:
  
  	preface		r43126
  	disks		r43449
  	book.xml	r43566
  	chapters.ent	r43126
  	Makefile	r43126
  
  Obtained From:	The FreeBSD Greek Documentation Project

Modified:
  head/el_GR.ISO8859-7/books/handbook/Makefile
  head/el_GR.ISO8859-7/books/handbook/book.xml
  head/el_GR.ISO8859-7/books/handbook/chapters.ent
  head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml
  head/el_GR.ISO8859-7/books/handbook/preface/preface.xml

Modified: head/el_GR.ISO8859-7/books/handbook/Makefile
==============================================================================
--- head/el_GR.ISO8859-7/books/handbook/Makefile	Fri Jan 24 17:03:57 2014	(r43639)
+++ head/el_GR.ISO8859-7/books/handbook/Makefile	Fri Jan 24 18:11:24 2014	(r43640)
@@ -4,7 +4,7 @@
 # Μορφοποίηση του Εγχειριδίου του FreeBSD
 #
 # %SOURCE%	en_US.ISO8859-1/books/handbook/Makefile
-# %SRCID%	1.119
+# %SRCID%	43126
 #
 
 # ------------------------------------------------------------------------
@@ -50,6 +50,7 @@ IMAGES_EN = advanced-networking/isdn-bus
 IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps
 IMAGES_EN+= advanced-networking/natd.eps
 IMAGES_EN+= advanced-networking/net-routing.pic
+IMAGES_EN+= advanced-networking/pxe-nfs.png
 IMAGES_EN+= advanced-networking/static-routes.pic
 IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png
 IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png
@@ -179,13 +180,6 @@ IMAGES_EN+= security/ipsec-network.pic
 IMAGES_EN+= security/ipsec-crypt-pkt.pic
 IMAGES_EN+= security/ipsec-encap-pkt.pic
 IMAGES_EN+= security/ipsec-out-pkt.pic
-IMAGES_EN+= vinum/vinum-concat.pic
-IMAGES_EN+= vinum/vinum-mirrored-vol.pic
-IMAGES_EN+= vinum/vinum-raid10-vol.pic
-IMAGES_EN+= vinum/vinum-raid5-org.pic
-IMAGES_EN+= vinum/vinum-simple-vol.pic
-IMAGES_EN+= vinum/vinum-striped-vol.pic
-IMAGES_EN+= vinum/vinum-striped.pic
 IMAGES_EN+= virtualization/parallels-freebsd1.png
 IMAGES_EN+= virtualization/parallels-freebsd2.png
 IMAGES_EN+= virtualization/parallels-freebsd3.png
@@ -283,8 +277,8 @@ SRCS+= preface/preface.xml
 SRCS+= printing/chapter.xml
 SRCS+= security/chapter.xml
 SRCS+= serialcomms/chapter.xml
+# Users chapter stays in the Greek Build until merged with basics
 SRCS+= users/chapter.xml
-SRCS+= vinum/chapter.xml
 SRCS+= virtualization/chapter.xml
 SRCS+= x11/chapter.xml
 
@@ -316,12 +310,12 @@ DOC_PREFIX?=	${.CURDIR}/../../..
 # rules generating lists of mirror site from XML database.
 #
 XMLDOCS=	lastmod:::mirrors.lastmod.inc \
-		mirrors-ftp:::mirrors.xml.ftp.inc \
 		mirrors-ftp-index:::mirrors.xml.ftp.index.inc \
-		mirrors-cvsup:::mirrors.xml.cvsup.inc \
+		mirrors-ftp:::mirrors.xml.ftp.inc \
 		mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \
-		eresources:::eresources.xml.www.inc \
-		eresources-index:::eresources.xml.www.index.inc
+		mirrors-cvsup:::mirrors.xml.cvsup.inc \
+		eresources-index:::eresources.xml.www.index.inc \
+		eresources:::eresources.xml.www.inc
 DEPENDSET.DEFAULT=	transtable mirror
 XSLT.DEFAULT=		${XSL_MIRRORS}
 XML.DEFAULT=		${XML_MIRRORS}

Modified: head/el_GR.ISO8859-7/books/handbook/book.xml
==============================================================================
--- head/el_GR.ISO8859-7/books/handbook/book.xml	Fri Jan 24 17:03:57 2014	(r43639)
+++ head/el_GR.ISO8859-7/books/handbook/book.xml	Fri Jan 24 18:11:24 2014	(r43640)
@@ -5,9 +5,8 @@
 %chapters;
 <!ENTITY % txtfiles SYSTEM "txtfiles.ent">
 %txtfiles;
-
-
 ]>
+
 <!--
 
   Το Εγχειρίδιο του FreeBSD: Οργάνωση Κεφαλαίων
@@ -17,12 +16,12 @@
   $FreeBSD$
 
   %SOURCE%      en_US.ISO8859-1/books/handbook/book.xml
-  %SRCID%       38826
+  %SRCID%       43566
 
 -->
+
 <book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="el">
   <info><title>Εγχειρίδιο του FreeBSD</title>
-    
 
     <author><orgname>Ομάδα Τεκμηρίωσης του FreeBSD</orgname></author>
 
@@ -49,6 +48,8 @@
       <year>2010</year>
       <year>2011</year>
       <year>2012</year>
+      <year>2013</year>
+      <year>2014</year>
       <holder>Ομάδα Τεκμηρίωσης του FreeBSD</holder>
     </copyright>
 
@@ -62,7 +63,6 @@
       &tm-attrib.adaptec;
       &tm-attrib.adobe;
       &tm-attrib.apple;
-      &tm-attrib.corel;
       &tm-attrib.creative;
       &tm-attrib.cvsup;
       &tm-attrib.heidelberger;
@@ -73,18 +73,12 @@
       &tm-attrib.linux;
       &tm-attrib.lsilogic;
       &tm-attrib.m-systems;
-      &tm-attrib.macromedia;
       &tm-attrib.microsoft;
-      &tm-attrib.netscape;
-      &tm-attrib.nexthop;
       &tm-attrib.opengroup;
       &tm-attrib.oracle;
-      &tm-attrib.powerquest;
       &tm-attrib.realnetworks;
       &tm-attrib.redhat;
-      &tm-attrib.sap;
       &tm-attrib.sun;
-      &tm-attrib.symantec;
       &tm-attrib.themathworks;
       &tm-attrib.thomson;
       &tm-attrib.usrobotics;
@@ -113,8 +107,9 @@
 	<uri xlink:href="http://docs.FreeBSD.org/doc/">http://docs.FreeBSD.org/doc/</uri>).  Μπορείτε
 	επίσης να μεταφορτώσετε στον υπολογιστή σας το ίδιο βιβλίο σε
 	άλλες μορφές αρχείου και με διάφορες μορφές συμπίεσης από
-	τον <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">εξυπηρετητή
-	FTP του &os;</link> ή ένα από τα
+	τον <link
+	  xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">εξυπηρετητή
+	  FTP του &os;</link> ή ένα από τα
 	πολλά <link linkend="mirrors-ftp">mirror sites</link>.  Αν
 	προτιμάτε ένα τυπωμένο αντίτυπο, μπορείτε να αγοράσετε ένα
 	αντίγραφο του Εγχειριδίου, από το
@@ -171,8 +166,8 @@
     </partintro>
 
     &chap.introduction;
-    &chap.install;
     &chap.bsdinstall;
+    &chap.install;
     &chap.basics;
     &chap.ports;
     &chap.x11;
@@ -252,6 +247,8 @@
 
     &chap.config;
     &chap.boot;
+    <!-- Note: users chapter will stay in the Greek build until merged
+	 basics -->
     &chap.users;
     &chap.security;
     &chap.jails;
@@ -260,7 +257,6 @@
     &chap.disks;
     &chap.geom;
     &chap.filesystems;
-    &chap.vinum;
     &chap.virtualization;
     &chap.l10n;
     &chap.cutting-edge;

Modified: head/el_GR.ISO8859-7/books/handbook/chapters.ent
==============================================================================
--- head/el_GR.ISO8859-7/books/handbook/chapters.ent	Fri Jan 24 17:03:57 2014	(r43639)
+++ head/el_GR.ISO8859-7/books/handbook/chapters.ent	Fri Jan 24 18:11:24 2014	(r43640)
@@ -13,7 +13,7 @@
      $FreeBSD$
 
      %SOURCE%	en_US.ISO8859-1/books/handbook/chapters.ent
-     %SRCID%	1.40
+     %SRCID%	43126
 
 -->
 
@@ -38,6 +38,7 @@
 <!-- Part Three -->
   <!ENTITY chap.config		SYSTEM "config/chapter.xml">
   <!ENTITY chap.boot		SYSTEM "boot/chapter.xml">
+<!-- users chapter stays in the Greek build until merged with basics -->
   <!ENTITY chap.users		SYSTEM "users/chapter.xml">
   <!ENTITY chap.security	SYSTEM "security/chapter.xml">
   <!ENTITY chap.jails		SYSTEM "jails/chapter.xml">
@@ -46,7 +47,6 @@
   <!ENTITY chap.disks		SYSTEM "disks/chapter.xml">
   <!ENTITY chap.geom		SYSTEM "geom/chapter.xml">
   <!ENTITY chap.filesystems	SYSTEM "filesystems/chapter.xml">
-  <!ENTITY chap.vinum		SYSTEM "vinum/chapter.xml">
   <!ENTITY chap.virtualization	SYSTEM "virtualization/chapter.xml">
   <!ENTITY chap.l10n		SYSTEM "l10n/chapter.xml">
   <!ENTITY chap.cutting-edge	SYSTEM "cutting-edge/chapter.xml">

Modified: head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml
==============================================================================
--- head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml	Fri Jan 24 17:03:57 2014	(r43639)
+++ head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml	Fri Jan 24 18:11:24 2014	(r43640)
@@ -8,7 +8,7 @@
   $FreeBSD$
 
   %SOURCE%	en_US.ISO8859-1/books/handbook/disks/chapter.xml
-  %SRCID%	1.1
+  %SRCID%	43449
 
 -->
 <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="disks">
@@ -52,17 +52,10 @@
           στο &os;.</para>
       </listitem>
       <listitem>
-        <para>Τα διάφορα διαθέσιμα μέσα αποθήκευσης για αντίγραφα
-          ασφαλείας.</para>
-      </listitem>
-      <listitem>
         <para>Πως να χρησιμοποιήσετε προγράμματα λήψης αντιγράφων
           ασφαλείας στο &os;.</para>
       </listitem>
       <listitem>
-        <para>Πως να πάρετε αντίγραφα ασφαλείας σε δισκέττες.</para>
-      </listitem>
-      <listitem>
         <para>Τι είναι οι εικόνες (snapshots) σε ένα σύστημα αρχείων και πως
           να τις χρησιμοποιήσετε αποδοτικά.</para>
       </listitem>
@@ -72,19 +65,17 @@
 
     <itemizedlist>
       <listitem>
-        <para>Να ξέρετε πως θα ρυθμίσετε και θα εγκαταστήσετε ένα νέο πυρήνα
-           του &os; (<xref linkend="kernelconfig"/>).</para>
+        <para>Να ξέρετε πως να <link linkend="kernelconfig">ρυθμίσετε και
+	   να εγκαταστήσετε ένα νέο πυρήνα του &os;</link>.</para>
       </listitem>
     </itemizedlist>
-
   </sect1>
 
   <sect1 xml:id="disks-naming">
     <title>Device Names</title>
 
     <para>The following is a list of physical storage devices
-      supported in FreeBSD, and the device names associated with
-      them.</para>
+      supported in &os; and their associated device names.</para>
 
     <table xml:id="disk-naming-physical-table" frame="none">
       <title>Physical Disk Naming Conventions</title>
@@ -96,45 +87,70 @@
 	    <entry>Drive device name</entry>
 	  </row>
 	</thead>
+
 	<tbody>
 	  <row>
 	    <entry>IDE hard drives</entry>
-	    <entry><literal>ad</literal></entry>
+	    <entry><literal>ad</literal> or
+	      <literal>ada</literal></entry>
+	  </row>
+
+	  <row>
+	    <entry>IDE CD-ROM drives</entry>
+	    <entry><literal>acd</literal> or
+	      <literal>cd</literal></entry>
+	  </row>
+
+	  <row>
+	    <entry>SATA hard drives</entry>
+	    <entry><literal>ad</literal> or
+	      <literal>ada</literal></entry>
 	  </row>
+
 	  <row>
-	    <entry>IDE CDROM drives</entry>
-	    <entry><literal>acd</literal></entry>
+	    <entry>SATA CD-ROM drives</entry>
+	    <entry><literal>acd</literal> or
+	      <literal>cd</literal></entry>
 	  </row>
+
 	  <row>
-	    <entry>SCSI hard drives and USB Mass storage devices</entry>
+	    <entry>SCSI hard drives and USB Mass storage
+	      devices</entry>
 	    <entry><literal>da</literal></entry>
 	  </row>
+
 	  <row>
-	    <entry>SCSI CDROM drives</entry>
+	    <entry>SCSI CD-ROM drives</entry>
 	    <entry><literal>cd</literal></entry>
 	  </row>
+
 	  <row>
-	    <entry>Assorted non-standard CDROM drives</entry>
+	    <entry>Assorted non-standard CD-ROM drives</entry>
 	    <entry><literal>mcd</literal> for Mitsumi CD-ROM and
-	      <literal>scd</literal> for Sony CD-ROM devices
-	    </entry>
+	      <literal>scd</literal> for Sony CD-ROM devices</entry>
 	  </row>
+
 	  <row>
 	    <entry>Floppy drives</entry>
 	    <entry><literal>fd</literal></entry>
 	  </row>
+
 	  <row>
 	    <entry>SCSI tape drives</entry>
 	    <entry><literal>sa</literal></entry>
-            </row>
+	  </row>
+
 	  <row>
 	    <entry>IDE tape drives</entry>
 	    <entry><literal>ast</literal></entry>
 	  </row>
+
 	  <row>
 	    <entry>Flash drives</entry>
-	    <entry><literal>fla</literal> for &diskonchip; Flash device</entry>
+	    <entry><literal>fla</literal> for &diskonchip; Flash
+	      device</entry>
 	  </row>
+
 	  <row>
 	    <entry>RAID drives</entry>
 	    <entry><literal>aacd</literal> for &adaptec; AdvancedRAID,
@@ -150,618 +166,142 @@
   </sect1>
 
   <sect1 xml:id="disks-adding">
-    <info><title>Adding Disks</title>
+    <info>
+      <title>Adding Disks</title>
+
       <authorgroup>
-	<author><personname><firstname>David</firstname><surname>O'Brien</surname></personname><contrib>Originally contributed by </contrib></author>
+	<author>
+	  <personname>
+	    <firstname>David</firstname>
+	    <surname>O'Brien</surname>
+	  </personname>
+	  <contrib>Originally contributed by </contrib>
+	</author>
       </authorgroup>
-      
     </info>
 
-    
-
     <indexterm>
       <primary>disks</primary>
       <secondary>adding</secondary>
     </indexterm>
 
-    <para>Lets say we want to add a new SCSI disk to a machine that
-      currently only has a single drive.  First turn off the computer
-      and install the drive in the computer following the instructions
-      of the computer, controller, and drive manufacturer.  Due to the
-      wide variations of procedures to do this, the details are beyond
-      the scope of this document.</para>
-
-    <para>Login as user <systemitem class="username">root</systemitem>.  After you have installed the
-      drive, inspect <filename>/var/run/dmesg.boot</filename> to ensure the new
-      disk was found.  Continuing with our example, the newly added drive will
-      be <filename>da1</filename> and we want to mount it on
-      <filename>/1</filename> (if you are adding an IDE drive, the device name
-      will be <filename>ad1</filename>).</para>
+    <para>This section describes how to add a new
+      <acronym>SATA</acronym> disk to a machine that currently only
+      has a single drive.  First, turn off the computer and install
+      the drive in the computer following the instructions of the
+      computer, controller, and drive manufacturers.  Reboot the
+      system and become
+      <systemitem class="username">root</systemitem>.</para>
+
+    <para>Inspect <filename>/var/run/dmesg.boot</filename> to ensure
+      the new disk was found.  In this example, the newly added
+      <acronym>SATA</acronym> drive will appear as
+      <filename>ada1</filename>.</para>
 
     <indexterm><primary>partitions</primary></indexterm>
-    <indexterm><primary>slices</primary></indexterm>
     <indexterm>
-      <primary><command>fdisk</command></primary>
+      <primary><command>gpart</command></primary>
     </indexterm>
 
-    <para>FreeBSD runs on IBM-PC compatible computers, therefore it must
-      take into account the PC BIOS partitions.  These are different
-      from the traditional BSD partitions.  A PC disk has up to four
-      BIOS partition entries.  If the disk is going to be truly
-      dedicated to FreeBSD, you can use the
-      <emphasis>dedicated</emphasis> mode.  Otherwise, FreeBSD will
-      have to live within one of the PC BIOS partitions.  FreeBSD
-      calls the PC BIOS partitions <emphasis>slices</emphasis> so as
-      not to confuse them with traditional BSD partitions.  You may
-      also use slices on a disk that is dedicated to FreeBSD, but used
-      in a computer that also has another operating system installed.
-      This is a good way to avoid confusing the <command>fdisk</command> utility of
-      other, non-FreeBSD operating systems.</para>
-
-    <para>In the slice case the drive will be added as
-      <filename>/dev/da1s1e</filename>.  This is read as: SCSI disk,
-      unit number 1 (second SCSI disk), slice 1 (PC BIOS partition 1),
-      and <filename>e</filename> BSD partition.  In the dedicated
-      case, the drive will be added simply as
-      <filename>/dev/da1e</filename>.</para>
-
-    <para>Due to the use of 32-bit integers to store the number of sectors,
-      &man.bsdlabel.8; is
-      limited to 2^32-1 sectors per disk or 2TB in most cases.  The
-      &man.fdisk.8; format allows a starting sector of no more than
-      2^32-1 and a length of no more than 2^32-1, limiting partitions to
-      2TB and disks to 4TB in most cases.  The &man.sunlabel.8; format
-      is limited to 2^32-1 sectors per partition and 8 partitions for
-      a total of 16TB. For larger disks, &man.gpt.8; partitions may be
-      used.</para>
-
-    <sect2>
-      <title>Using &man.sysinstall.8;</title>
-      <indexterm>
-        <primary><application>sysinstall</application></primary>
-        <secondary>adding disks</secondary>
-      </indexterm>
-      <indexterm>
-	<primary>su</primary>
-      </indexterm>
-      <procedure>
-	<step>
-	  <title>Navigating <application>Sysinstall</application></title>
-
-	  <para>You may use <command>sysinstall</command> to
-	    partition and label a new disk using its easy to use menus.
-	    Either login as user <systemitem class="username">root</systemitem> or use the
-	    <command>su</command> command.  Run
-	    <command>sysinstall</command> and enter the
-	    <literal>Configure</literal> menu.  Within the
-	    <literal>FreeBSD Configuration Menu</literal>, scroll down and
-	    select the <literal>Fdisk</literal> option.</para>
-	</step>
-
-	<step>
-	  <title><application>fdisk</application> Partition Editor</title>
-	  <para>Once inside <application>fdisk</application>, typing <userinput>A</userinput> will
-	    use the entire disk for FreeBSD.  When asked if you want to
-	    <quote>remain cooperative with any future possible operating
-	      systems</quote>, answer <literal>YES</literal>.  Write the
-	    changes to the disk using <userinput>W</userinput>.  Now exit the
-	    FDISK editor by typing <userinput>q</userinput>.  Next you will be
-	    asked about the <quote>Master Boot Record</quote>.  Since you are adding a
-	    disk to an already running system, choose
-	    <literal>None</literal>.</para>
-	</step>
-
-	<step>
-	  <title>Disk Label Editor</title>
-	  <indexterm><primary>BSD partitions</primary></indexterm>
-
-	  <para>Next, you need to exit <application>sysinstall</application>
-            and start it again.  Follow the directions above, although this
-            time choose the <literal>Label</literal> option. This will
-	    enter the <literal>Disk Label Editor</literal>.  This
-	    is where you will create the traditional BSD partitions.  A
-	    disk can have up to eight partitions, labeled
-	    <literal>a-h</literal>.
-	    A few of the partition labels have special uses.  The
-	    <literal>a</literal> partition is used for the root partition
-	    (<filename>/</filename>).  Thus only your system disk (e.g,
-	    the disk you boot from) should have an <literal>a</literal>
-	    partition.  The <literal>b</literal> partition is used for
-	    swap partitions, and you may have many disks with swap
-	    partitions.  The <literal>c</literal> partition addresses the
-	    entire disk in dedicated mode, or the entire FreeBSD slice in
-	    slice mode.  The other partitions are for general use.</para>
-
-	  <para><application>sysinstall</application>'s Label editor
-	    favors the <literal>e</literal>
-	    partition for non-root, non-swap partitions.  Within the
-	    Label editor, create a single file system by typing
-	    <userinput>C</userinput>.  When prompted if this will be a FS
-	    (file system) or swap, choose <literal>FS</literal> and type in a
-	    mount point (e.g, <filename>/mnt</filename>).  When adding a
-	    disk in post-install mode, <application>sysinstall</application>
-	    will not create entries
-	    in <filename>/etc/fstab</filename> for you, so the mount point
-	    you specify is not important.</para>
-
-	  <para>You are now ready to write the new label to the disk and
-	    create a file system on it.  Do this by typing
-	    <userinput>W</userinput>.  Ignore any errors from
-	    <application>sysinstall</application> that
-	    it could not mount the new partition.  Exit the Label Editor
-	    and <application>sysinstall</application> completely.</para>
-	</step>
-
-	<step>
-	  <title>Finish</title>
-
-	  <para>The last step is to edit <filename>/etc/fstab</filename>
-	    to add an entry for your new disk.</para>
-	</step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>Using Command Line Utilities</title>
-
-      <sect3>
-	<title>Using Slices</title>
-
-	<para>This setup will allow your disk to work correctly with
-	  other operating systems that might be installed on your
-	  computer and will not confuse other operating systems'
-	  <command>fdisk</command> utilities.  It is recommended
-	  to use this method for new disk installs.  Only use
-	  <literal>dedicated</literal> mode if you have a good reason
-	  to do so!</para>
-
-	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
-&prompt.root; <userinput>fdisk -BI da1</userinput> #Initialize your new disk
-&prompt.root; <userinput>bsdlabel -B -w -r da1s1 auto</userinput> #Label it.
-&prompt.root; <userinput>bsdlabel -e da1s1</userinput> # Edit the bsdlabel just created and add any partitions.
-&prompt.root; <userinput>mkdir -p /1</userinput>
-&prompt.root; <userinput>newfs /dev/da1s1e</userinput> # Repeat this for every partition you created.
-&prompt.root; <userinput>mount /dev/da1s1e /1</userinput> # Mount the partition(s)
-&prompt.root; <userinput>vi /etc/fstab</userinput> # Add the appropriate entry/entries to your <filename>/etc/fstab</filename>.</screen>
-
-	<para>If you have an IDE disk, substitute <filename>ad</filename>
-	  for <filename>da</filename>.</para>
-      </sect3>
-
-      <sect3>
-	<title>Dedicated</title>
-	<indexterm><primary>OS/2</primary></indexterm>
-
-	<para>If you will not be sharing the new drive with another operating
-	  system, you may use the <literal>dedicated</literal> mode.  Remember
-	  this mode can confuse Microsoft operating systems; however, no damage
-	  will be done by them.  IBM's &os2; however, will
-	  <quote>appropriate</quote> any partition it finds which it does not
-	  understand.</para>
-
-	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
-&prompt.root; <userinput>bsdlabel -Brw da1 auto</userinput>
-&prompt.root; <userinput>bsdlabel -e da1</userinput>				# create the `e' partition
-&prompt.root; <userinput>newfs -d0 /dev/da1e</userinput>
-&prompt.root; <userinput>mkdir -p /1</userinput>
-&prompt.root; <userinput>vi /etc/fstab</userinput>				# add an entry for /dev/da1e
-&prompt.root; <userinput>mount /1</userinput></screen>
-
-	<para>An alternate method is:</para>
-
-	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 count=2</userinput>
-&prompt.root; <userinput>bsdlabel /dev/da1 | bsdlabel -BrR da1 /dev/stdin</userinput>
-&prompt.root; <userinput>newfs /dev/da1e</userinput>
-&prompt.root; <userinput>mkdir -p /1</userinput>
-&prompt.root; <userinput>vi /etc/fstab</userinput>					# add an entry for /dev/da1e
-&prompt.root; <userinput>mount /1</userinput></screen>
-
-      </sect3>
-    </sect2>
-  </sect1>
-
-  <sect1 xml:id="raid">
-    <title>RAID</title>
-
-    <sect2 xml:id="raid-soft">
-      <title>Software RAID</title>
-
-      <sect3 xml:id="ccd">
-	<info><title>Concatenated Disk Driver (CCD) Configuration</title>
-	  <authorgroup>
-	    <author><personname><firstname>Christopher</firstname><surname>Shumway</surname></personname><contrib>Original work by </contrib></author>
-	  </authorgroup>
-	  <authorgroup>
-	    <author><personname><firstname>Jim</firstname><surname>Brown</surname></personname><contrib>Revised by </contrib></author>
-	  </authorgroup>
-	</info>
-
-	
-
-<indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
-<indexterm>
-  <primary>RAID</primary><secondary>CCD</secondary>
-</indexterm>
-
-	<para>When choosing a mass storage solution the most important
-	  factors to consider are speed, reliability, and cost.  It is
-	  rare to have all three in balance; normally a fast, reliable mass
-	  storage device is expensive, and to cut back on cost either speed
-	  or reliability must be sacrificed.</para>
-
-          <para>In designing the system described below, cost was chosen
-          as  the most important factor, followed by speed, then reliability.
-          Data transfer speed for this system is ultimately
-          constrained by the network.  And while reliability is very important,
-          the CCD drive described below serves online data that is already
-          fully backed up on CD-R's and can easily be replaced.</para>
-
-          <para>Defining your own requirements is the first step
-          in choosing a mass storage solution.  If your requirements prefer
-          speed or reliability over cost, your solution will differ from
-          the system described in this section.</para>
-
-
-	<sect4 xml:id="ccd-installhw">
-	  <title>Installing the Hardware</title>
-
-	  <para>In addition to the IDE system disk, three Western
-            Digital 30GB, 5400 RPM IDE disks form the core
-            of the CCD disk described below providing approximately
-	    90GB of online storage.  Ideally,
-	    each IDE disk would have its own IDE controller
-	    and cable, but to minimize cost, additional
-	    IDE controllers were not used.  Instead the disks were
-	    configured with jumpers so that each IDE controller has
-            one master, and one slave.</para>
-
-	  <para>Upon reboot, the system BIOS was configured to
-	    automatically detect the disks attached.  More importantly,
-	    FreeBSD detected them on reboot:</para>
-
-	  <programlisting>ad0: 19574MB &lt;WDC WD205BA&gt; [39770/16/63] at ata0-master UDMA33
-ad1: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata0-slave UDMA33
-ad2: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-master UDMA33
-ad3: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlisting>
-
- 	  <note><para>If FreeBSD does not detect all the disks, ensure
- 	    that you have jumpered them correctly.  Most IDE drives
- 	    also have a <quote>Cable Select</quote> jumper.  This is
- 	    <emphasis>not</emphasis> the jumper for the master/slave
- 	    relationship.  Consult the drive documentation for help in
- 	    identifying the correct jumper.</para></note>
-
- 	  <para>Next, consider how to attach them as part of the file
- 	    system.  You should research both &man.vinum.8; (<xref linkend="vinum-vinum"/>) and &man.ccd.4;.  In this
- 	    particular configuration, &man.ccd.4; was chosen.</para>
-	</sect4>
-
-	<sect4 xml:id="ccd-setup">
-	  <title>Setting Up the CCD</title>
-
- 	  <para>The &man.ccd.4; driver allows you to take
-  	    several identical disks and concatenate them into one
-  	    logical file system.  In order to use
- 	    &man.ccd.4;, you need a kernel with
- 	    &man.ccd.4; support built in.
- 	    Add this line to your kernel configuration file, rebuild, and
- 	    reinstall the kernel:</para>
-
-	  <programlisting>device   ccd</programlisting>
-
-	  <para>The &man.ccd.4; support can also be
-	    loaded as a kernel loadable module.</para>
-
- 	  <para>To set up &man.ccd.4;, you must first use
- 	    &man.bsdlabel.8; to label the disks:</para>
-
-	  <programlisting>bsdlabel -r -w ad1 auto
-bsdlabel -r -w ad2 auto
-bsdlabel -r -w ad3 auto</programlisting>
-
- 	  <para>This creates a bsdlabel for <filename>ad1c</filename>, <filename>ad2c</filename> and <filename>ad3c</filename> that
-  	    spans the entire disk.</para>
-
- 	  <para>The next step is to change the disk label type.  You
- 	    can use &man.bsdlabel.8; to edit the
- 	    disks:</para>
-
-	  <programlisting>bsdlabel -e ad1
-bsdlabel -e ad2
-bsdlabel -e ad3</programlisting>
-
- 	  <para>This opens up the current disk label on each disk with
- 	    the editor specified by the <envar>EDITOR</envar>
- 	    environment variable, typically &man.vi.1;.</para>
-
-	  <para>An unmodified disk label will look something like
-	    this:</para>
-
-	  <programlisting>8 partitions:
-#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</programlisting>
-
- 	  <para>Add a new <literal>e</literal> partition for &man.ccd.4; to use. This
- 	    can usually be copied from the <literal>c</literal> partition,
- 	    but the <option>fstype</option> <emphasis>must</emphasis>
- 	    be <userinput>4.2BSD</userinput>.  The disk label should
- 	    now look something like this:</para>
-
-	  <programlisting>8 partitions:
-#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
-  e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)</programlisting>
-
-	</sect4>
-
-	<sect4 xml:id="ccd-buildingfs">
-	  <title>Building the File System</title>
-
-	  <para>Now that you have all the disks labeled, you must
-	    build the &man.ccd.4;.  To do that,
-	    use  &man.ccdconfig.8;, with options similar to the following:</para>
-
-	    <programlisting>ccdconfig ccd0<co xml:id="co-ccd-dev"/> 32<co xml:id="co-ccd-interleave"/> 0<co xml:id="co-ccd-flags"/> /dev/ad1e<co xml:id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting>
-
-	  <para>The use and meaning of each option is shown below:</para>
-
-          <calloutlist>
-            <callout arearefs="co-ccd-dev">
-	    <para>The first argument is the device to configure, in this case,
-	    <filename>/dev/ccd0c</filename>. The <filename>/dev/</filename>
-            portion is optional.</para>
-            </callout>
-
-            <callout arearefs="co-ccd-interleave">
-
-	    <para>The interleave for the file system.  The interleave
-	    defines the size of a stripe in disk blocks, each normally 512 bytes.
-	    So, an interleave of 32 would be 16,384 bytes.</para>
-            </callout>
-
-            <callout arearefs="co-ccd-flags">
-	    <para>Flags for &man.ccdconfig.8;.  If you want to enable drive
-	    mirroring, you can specify a flag here. This
-	    configuration does not provide mirroring for
-	    &man.ccd.4;, so it is set at 0 (zero).</para>
-            </callout>
-
-            <callout arearefs="co-ccd-devs">
-	    <para>The final arguments to &man.ccdconfig.8;
-	    are the devices to place into the array.  Use the complete pathname
-	    for each device.</para>
-            </callout>
-          </calloutlist>
-
-
-	  <para>After running &man.ccdconfig.8; the &man.ccd.4;
-          is configured. A file system can be installed. Refer to &man.newfs.8;
-          for options, or simply run: </para>
-
-	  <programlisting>newfs /dev/ccd0c</programlisting>
-
-
-	</sect4>
-
-	<sect4 xml:id="ccd-auto">
-	  <title>Making it All Automatic</title>
-
-	  <para>Generally, you will want to mount the
-	    &man.ccd.4; upon each reboot. To do this, you must
-	    configure it first.  Write out your current configuration to
-	    <filename>/etc/ccd.conf</filename> using the following command:</para>
-
-	  <programlisting>ccdconfig -g &gt; /etc/ccd.conf</programlisting>
-
-	  <para>During reboot, the script <command>/etc/rc</command>
-	    runs <command>ccdconfig -C</command> if <filename>/etc/ccd.conf</filename>
-	    exists. This automatically configures the
-	    &man.ccd.4; so it can be mounted.</para>
-
-	  <note><para>If you are booting into single user mode, before you can
-	    &man.mount.8; the &man.ccd.4;, you
-	    need to issue the following command to configure the
-	    array:</para>
-
-	  <programlisting>ccdconfig -C</programlisting>
-          </note>
-
-	  <para>To automatically mount the &man.ccd.4;,
-            place an entry for the &man.ccd.4; in
-	    <filename>/etc/fstab</filename> so it will be mounted at
-	    boot time:</para>
-
-	  <programlisting>/dev/ccd0c              /media       ufs     rw      2       2</programlisting>
-	</sect4>
-      </sect3>
-
-      <sect3 xml:id="vinum">
-	<title>The Vinum Volume Manager</title>
-
-<indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
-<indexterm>
-  <primary>RAID</primary>
-  <secondary>Vinum</secondary>
-</indexterm>
-
-	<para>The Vinum Volume Manager is a block device driver which
-	  implements virtual disk drives.  It isolates disk hardware
-	  from the block device interface and maps data in ways which
-	  result in an increase in flexibility, performance and
-	  reliability compared to the traditional slice view of disk
-	  storage.  &man.vinum.8; implements the RAID-0, RAID-1 and
-	  RAID-5 models, both individually and in combination.</para>
-
-	<para>See <xref linkend="vinum-vinum"/> for more
-	  information about &man.vinum.8;.</para>
-      </sect3>
-    </sect2>
-
-    <sect2 xml:id="raid-hard">
-      <title>Hardware RAID</title>
-
-      <indexterm>
-	<primary>RAID</primary>
-	<secondary>hardware</secondary>
-      </indexterm>
-
-      <para>FreeBSD also supports a variety of hardware <acronym>RAID</acronym>
-        controllers.  These devices control a <acronym>RAID</acronym> subsystem
-        without the need for FreeBSD specific software to manage the
-        array.</para>
-
-      <para>Using an on-card <acronym>BIOS</acronym>, the card controls most  of the disk operations
-	itself.  The following is a brief setup description using a Promise <acronym>IDE</acronym> <acronym>RAID</acronym>
-	controller.  When this card is installed and the system is started up, it
-	displays a prompt requesting information.  Follow the instructions
-	to enter the card's setup screen.  From here, you have the ability to
-	combine all the attached drives.  After doing so, the disk(s) will look like
-	a single drive to FreeBSD.  Other <acronym>RAID</acronym> levels can be set up
-	accordingly.
-      </para>
-    </sect2>
-
-    <sect2>
-      <title>Rebuilding ATA RAID1 Arrays</title>
-
-      <para>FreeBSD allows you to hot-replace a failed disk in an array. This requires
-	that you catch it before you reboot.</para>
-
-      <para>You will probably see something like the following in <filename>/var/log/messages</filename> or in the &man.dmesg.8;
-	output:</para>
+    <para>For this example, a single large partition will be created
+      on the new disk.  The <link
+	xlink:href="http://en.wikipedia.org/wiki/GUID_Partition_Table">;
+	<acronym>GPT</acronym></link> partitioning scheme will be
+      used in preference to the older and less versatile
+      <acronym>MBR</acronym> scheme.</para>
 
-      <programlisting>ad6 on monster1 suffered a hard error.
-ad6: READ command timeout tag=0 serv=0 - resetting
-ad6: trying fallback to PIO mode
-ata3: resetting devices .. done
-ad6: hard error reading fsbn 1116119 of 0-7 (ad6 bn 1116119; cn 1107 tn 4 sn 11)\\
-status=59 error=40
-ar0: WARNING - mirror lost</programlisting>
-
-      <para>Using &man.atacontrol.8;, check for further information:</para>
-
-      <screen>&prompt.root; <userinput>atacontrol list</userinput>
-ATA channel 0:
-	Master:      no device present
-	Slave:   acd0 &lt;HL-DT-ST CD-ROM GCR-8520B/1.00&gt; ATA/ATAPI rev 0
-
-ATA channel 1:
-	Master:      no device present
-	Slave:       no device present
-
-ATA channel 2:
-	Master:  ad4 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
-	Slave:       no device present
-
-ATA channel 3:
-	Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
-	Slave:       no device present
-
-&prompt.root; <userinput>atacontrol status ar0</userinput>
-ar0: ATA RAID1 subdisks: ad4 ad6 status: DEGRADED</screen>
-
-      <procedure>
-	<step>
-	  <para>You will first need to detach the ata channel with the failed
-	    disk so you can safely remove it:</para>
-
-	  <screen>&prompt.root; <userinput>atacontrol detach ata3</userinput></screen>
-	</step>
+    <note>
+      <para>If the disk to be added is not blank, old partition
+	information can be removed with
+	<command>gpart delete</command>.  See &man.gpart.8; for
+	details.</para>
+    </note>
 
-	<step>
-	  <para>Replace the disk.</para>
-	</step>
+    <para>The partition scheme is created, and then a single partition
+      is added:</para>
 
-	<step>
-	  <para>Reattach the ata channel:</para>
+    <screen>&prompt.root; <userinput>gpart create -s GPT ada1</userinput>
+&prompt.root; <userinput>gpart add -t freebsd-ufs ada1</userinput></screen>
 
-	  <screen>&prompt.root; <userinput>atacontrol attach ata3</userinput>
-Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
-Slave:   no device present</screen>
-	</step>
+    <para>Depending on use, several smaller partitions may be desired.
+      See &man.gpart.8; for options to create partitions smaller than
+      a whole disk.</para>
 
-	<step>
-	  <para>Add the new disk to the array as a spare:</para>
+    <para>A file system is created on the new blank disk:</para>
 
-	  <screen>&prompt.root; <userinput>atacontrol addspare ar0 ad6</userinput></screen>
-	</step>
+    <screen>&prompt.root; <userinput>newfs -U /dev/ada1p1</userinput></screen>
 
-	<step>
-	  <para>Rebuild the array:</para>
+    <para>An empty directory is created as a
+      <emphasis>mountpoint</emphasis>, a location for mounting the new
+      disk in the original disk's file system:</para>
 
-	  <screen>&prompt.root; <userinput>atacontrol rebuild ar0</userinput></screen>
-	</step>
+    <screen>&prompt.root; <userinput>mkdir /newdisk</userinput></screen>
 
-	<step>
-	  <para>It is possible to check on the progress by issuing the
-	    following command:</para>
+    <para>Finally, an entry is added to
+      <filename>/etc/fstab</filename> so the new disk will be mounted
+      automatically at startup:</para>
 
-	  <screen>&prompt.root; <userinput>dmesg | tail -10</userinput>
-[output removed]
-ad6: removed from configuration
-ad6: deleted from ar0 disk1
-ad6: inserted into ar0 disk1 as spare
+    <programlisting>/dev/ada1p1	/newdisk	ufs	rw	2	2</programlisting>
 
-&prompt.root; <userinput>atacontrol status ar0</userinput>
-ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed</screen>
-	</step>
+    <para>The new disk can be mounted manually, without restarting the
+      system:</para>
 
-	<step>
-	  <para>Wait until this operation completes.</para>
-	</step>
-      </procedure>
-    </sect2>
+    <screen>&prompt.root; <userinput>mount /newdisk</userinput></screen>
   </sect1>
 
   <sect1 xml:id="usb-disks">
-    <info><title>USB Storage Devices</title>
+    <info>
+      <title>USB Storage Devices</title>
+
       <authorgroup>
-	<author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author>
+	<author>
+	  <personname>
+	    <firstname>Marc</firstname>
+	    <surname>Fonvieille</surname>
+	  </personname>
+	  <contrib>Contributed by </contrib>
+	</author>
       </authorgroup>
-      
     </info>
 
-    
     <indexterm>
       <primary>USB</primary>
       <secondary>disks</secondary>
     </indexterm>
 
-    <para>A lot of external storage solutions, nowadays, use the
-      Universal Serial Bus (USB): hard drives, USB thumbdrives, CD-R
-      burners, etc.  &os; provides support for these devices.</para>
+    <para>Many external storage solutions, such as hard drives, USB
+      thumbdrives, and CD/DVD burners, use the Universal Serial Bus
+      (USB).  &os; provides support for these devices.</para>
 
     <sect2>
       <title>Configuration</title>
 
-      <para>The USB mass storage devices driver, &man.umass.4;,
-	provides the support for USB storage devices.  If you use the
-	<filename>GENERIC</filename> kernel, you do not have to change
-	anything in your configuration.  If you use a custom kernel,
-	be sure that the following lines are present in your kernel
-	configuration file:</para>
+      <para>The USB mass storage devices driver, &man.umass.4;, is
+	built into the <filename>GENERIC</filename> kernel and
+	provides support for USB storage devices.  For a custom
+	kernel, be sure that the following lines are present in the
+	kernel configuration file:</para>
 
       <programlisting>device scbus
 device da
 device pass
 device uhci
 device ohci
+device ehci
 device usb
 device umass</programlisting>
 

*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201401241811.s0OIBOuW058994>