From owner-freebsd-current Mon Aug 2 10: 0:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 63A5614DD8 for ; Mon, 2 Aug 1999 10:00:41 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA75533; Mon, 2 Aug 1999 09:59:15 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 2 Aug 1999 09:59:15 -0700 (PDT) From: Doug White To: Poul-Henning Kamp Cc: Mike Smith , Bruce Evans , current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-Reply-To: <22942.933575936@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Aug 1999, Poul-Henning Kamp wrote: > In message <199908020630.XAA01845@dingo.cdrom.com>, Mike Smith writes: > >> In message <199908020207.MAA23787@godzilla.zeta.org.au>, Bruce Evans writes: > >> > >> >All of the above only work for the easy case where the whole disk is > >> >being labelled. In general, the disk size must be reduced to the slice > >> >size before applying a label to a slice. > >> > >> And that is the problem, it seems that "dangerously dedicated" doesn't > >> boot anymore... > > > >It never did, on many hardware variants. Use "truly dedicated" > >instead, which should still work fine. > > My semantics may be wrong on these two: what I'm talking about is > what is in handbook chapter 8 "Using command line utilities " gives > you a disk which doesn't boot. What BIOS do you have? Did you try the tutorial version? I know machines that won't boot disks missing MS partition tables. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message