From owner-freebsd-doc  Wed Aug 14 20:18:07 1996
Return-Path: owner-doc
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA18918
          for doc-outgoing; Wed, 14 Aug 1996 20:18:07 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA18901
          for <doc@freebsd.org>; Wed, 14 Aug 1996 20:18:02 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id UAA11795; Wed, 14 Aug 1996 20:17:39 -0700 (PDT)
Date: Wed, 14 Aug 1996 20:17:39 -0700 (PDT)
Message-Id: <199608150317.UAA11795@silvia.HIP.Berkeley.EDU>
To: doc@freebsd.org
Subject: Two new entries (ccd) for the FAQ
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-doc@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello docmasters,

I added answers to the two most (un-)popular questions on the ccd list.
Please review and commit at your leisure (or I'll do it if they're ok).

Thanks
Satoshi
-------
Index: freebsd-faq.sgml
===================================================================
RCS file: /usr/cvs/src/share/doc/FAQ/freebsd-faq.sgml,v
retrieving revision 1.60
diff -u -r1.60 freebsd-faq.sgml
--- freebsd-faq.sgml	1996/08/05 17:18:03	1.60
+++ freebsd-faq.sgml	1996/08/15 03:09:24
@@ -2500,6 +2500,49 @@
               </verb>
          </enum>
 
+      <sect1>
+	<heading>What's inappropriate about my ccd?</heading>
+	<p>
+	  The symptom of this is:
+	  <verb>
+	    host# ccdconfig -C
+	    ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format
+	    host#
+	  </verb>
+
+	<p>
+	  This usually happens when you are trying to concatenate the
+	  `c' partitions, which default to type `unused'.  The ccd
+	  driver requires the underlying partition type to be
+	  FS_BSDFFS.  Edit the disklabel of the disks you are trying
+	  to concatenate and change the types of partitions to
+	  `4.2BSD'.
+
+      <sect1>
+        <heading>Why can't I edit the disklabel on my ccd?</heading>
+	<p>
+	  The symptom of this is:
+	  <verb>
+	    host# disklabel ccd0
+	    (it prints something sensible here, so let's try to edit it)
+	    host# disklabel -e ccd0
+	    (edit, save, quit)
+	    disklabel: ioctl DIOCWDINFO: No disk label on disk;
+	    use "disklabel -r" to install initial label
+	    host#
+	  </verb>
+
+        <p>
+	  This is because the disklabel returned by ccd is actually a
+	  `fake' one that is not really on the disk.  You can solve
+	  this problem by writing it back explicitly, as in:
+	  <verb>
+	    host# disklabel ccd0 > /tmp/disklabel.tmp
+	    host# disklabel -Rr ccd0 /tmp/disklabel.tmp
+	    host# disklabel -e ccd0
+	    (this will work now)
+	  </verb>
+
     <sect>
       <heading>Networking</heading>