*BSD News Article 80349


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!cs.mu.OZ.AU!munnari.OZ.AU!spool.mu.edu!agate!asami
From: asami@freebsd.org (Satoshi Asami)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: ccd configuration woes
Date: 09 Oct 1996 20:50:31 GMT
Organization: CS Div. - EECS, The University of California, Berkeley, CA 94720
Lines: 30
Message-ID: <ASAMI.96Oct9135031@sunrise.cs.berkeley.edu>
References: <52ra4s$ed7@service3.uky.edu> <55e0pf.5rl.rtaylor@bbs.mpcs.com>
NNTP-Posting-Host: sunrise.cs.berkeley.edu
In-reply-to: rtaylor@bbs.mpcs.com's message of 5 Oct 1996 16:54:07 PST

In article <55e0pf.5rl.rtaylor@bbs.mpcs.com>
        rtaylor@bbs.mpcs.com (Rob Taylor) writes:

 *  CCD what a nightmare, I know how you feel.  We went through the same 
 * thing a few weeks ago.  Trying to retrace my steps.   First off the 
 * slices have to be pre-created as a UFS file system.   Once you have done 
 * that, you can then use the ccdconfig to bind them together, but before 
 * you can use them you will need to do a newfs on them COMBINED.
 * 
 * 
 * 
 * On 1 Oct 1996 14:34:04 GMT, John Soward <soward@neworder.cc.uky.edu> wrote:
 *  : I know this must be a common problem, with a simple fix, I read several  
 *  : messages from people with similar problems -- only thing is I never found an  
 *  : answer in the FAQs or mailing list archives....
 *  : currently I'm getting 
 *  : ccdconfig: ioctl(CCDIOCSET): /dev/ccd0c: Invalid Argument
 *  : but I've gotten various other complaints concerning /dev/ccd0c as well...

Sorry you couldn't find this in a FAQ, I sent a submission for entries 
for this a long time ago and kinda forgot about it.

Anyway, what you need is to use disklabel to mark the underlying
partitions as "4.2BSD".  No need to create filesystems on them
individually, but as Rob says, you need to run newfs on them after
ccdconfig.

I should probably write a handbook chapter on this too.... ;)

Satoshi