From owner-freebsd-current Fri May 3 21:22:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA07875 for current-outgoing; Fri, 3 May 1996 21:22:22 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA07870 for ; Fri, 3 May 1996 21:22:19 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id OAA31451; Sat, 4 May 1996 14:15:54 +1000 Date: Sat, 4 May 1996 14:15:54 +1000 From: Bruce Evans Message-Id: <199605040415.OAA31451@godzilla.zeta.org.au> To: asami@CS.Berkeley.EDU, bde@zeta.org.au Subject: Re: ccd offset, please review + test Cc: ccd@stampede.cs.berkeley.edu, current@freebsd.org, rgrimes@GndRsh.aac.dev.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * Grep for RAW_PART in /sys to see where sdXc is special. It's special > * before a label exists (then it's the only partition than can be opened) > * and after a label exists (then the label on it is write protected ...). >Ok, but does that mean anything in terms of using sdXc as a regular >filesystem or as part of a ccd? It means that it's only suitable for a file system if there are no other file systems on the disk, and only suitable for concatenation if it's at the front. > * I use /dev/rsds1 partitioned normally and /dev/rsds[2-4] essentially > * unpartitioned (I have to put a label on them to keep newfs happy but > * mount handles arbitrary block devices with a supported file system > * on them). >So you are saying it's ok to use sdXc, right? Only for one (ufs) file system per disk. Bruce