Date: Fri, 3 May 1996 17:23:14 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: bde@zeta.org.au Cc: rgrimes@GndRsh.aac.dev.com, ccd@stampede.cs.berkeley.edu, current@FreeBSD.ORG Subject: Re: ccd offset, please review + test Message-ID: <199605040023.RAA01288@sunrise.cs.berkeley.edu> In-Reply-To: <199605032204.IAA19156@godzilla.zeta.org.au> (message from Bruce Evans on Sat, 4 May 1996 08:04:39 %2B1000)
next in thread | previous in thread | raw e-mail | index | archive | help
* >For the whole slice, or with an offset? In other words, is sdXc * >special because of its name, or because it is the only partition that * >starts at the beginning? * * sdXc is conventionally the whole slice. Making it smaller than the whole * slice is fairly harmless and fairly useless. Well I'm not mentioning to change sdXc to mean anything else, just trying to make it able to use it in ccd (like it can be used for regular BSD filesystems).... * 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? * >Anyway, I just tried creating a regular filesystem on /dev/sd237c * >(actually sd1c, but who's counting) on our FreeBSD machine. It seems * >to work, are you sure it isn't supposed to? * * 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? Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605040023.RAA01288>