> How about raw reads/writes?  Wouldn't you want bounds checking which I
> assume is available through the disklabeling?  I'm not the best for
> examples, but possibly for backing up nonBSD partitions from BSD?
> 
	The 'bsd partion' idea is nice enough but how does it work with a
	disk arranged as:

	+----------+
	| Non BSD  |
	+----------+
	| BSD      |
	+----------+
	| Non BSD  |
	+----------+
	| BSD	   |
	+----------+
	| Non BSD  |
	+----------+

	What does the 'bsd partition' cover? Its not general enough to
	cover all cases. Maybe it covers from the start of the first BSD area
	to the end of the last, or maybe just the boot block and disklabel
	area.

	If you are using raw read/writes then I would assume you could
	iterate through the appropriate partitions (excluding 'b' in some
	cases).

	That leaves boot blocks and disklabel access.

	iff partitiona 'a' is at the start of your BSD area then all is
	OK - you can use its offset as the basis for the disklabel and
	bootblocks.

	If not, then maybe we do need another partition for 'boot block
	and disklabel area'...

		David/absolute

Q:  Why do ducks have flat feet?	Q:  Why do elephants have flat feet?
A:  To stamp out forest fires.		A:  To stamp out flaming ducks.

On Mon, 16 Aug 1999, Erich Enke wrote: