Date: Sun, 01 Aug 1999 23:39:48 -0700 From: Mike Smith <mike@smith.net.au> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Mike Smith <mike@smith.net.au>, Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" Message-ID: <199908020639.XAA01900@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 02 Aug 1999 08:38:56 %2B0200." <22942.933575936@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. Ok; of those two examples, the first should give you a truly dedicated disk. (You can only generate a "dangerously dedicated" disk with sysinstall.) What fails? Can you be more specific? How recent are your boot1/boot2 blocks? I would be inclined to dd at least 8k over the front of the disk myself, but I don't think that's relevant in your case. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908020639.XAA01900>