From owner-freebsd-current  Fri Aug  6  0:18: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 4063714E9C
	for <current@FreeBSD.ORG>; Fri,  6 Aug 1999 00:18:03 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA09944;
	Fri, 6 Aug 1999 17:18:01 +1000
Date: Fri, 6 Aug 1999 17:18:01 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199908060718.RAA09944@godzilla.zeta.org.au>
To: imp@village.org, phk@critter.freebsd.dk
Subject: Re: junior-hacker task: "prepdisk"
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>: It seems that our new boot blocks doesn't like the taste of disks
>>: prepared according to the meagre information we have in the handbook.
>>
>>How does this script differ from 'disklabel -w wd0 auto'?  It does do
>>the fdisk stuff (your script, not the disklabel command).
>
>It differs in that you can boot from the disk afterwards with my script,
>you cant with disklabel -w wd0 auto.

That may be because you forgot to supply the -r or -B args to disklabel,
or forgot to edit the label using disklabel -e.  I think no editing is
required to boot from the 'c' partition (the missing d_type initialisation
doesn't matter because the `d_type != DTYPE_SCSI' case defaults to
DTYPE_ESDI (aka IDE)).  The 'a' partition produced by
`disklabel -Brw wd0 auto ' is obviosuly unbootable and unnewfsable,
etc., since it is empty.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message