Date: Mon, 02 Aug 1999 08:49:53 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Mike Smith <mike@smith.net.au> Cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" Message-ID: <23040.933576593@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 01 Aug 1999 23:39:48 PDT." <199908020639.XAA01900@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199908020639.XAA01900@dingo.cdrom.com>, Mike Smith writes: >> 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. Disk error #1 while trying to load boot/loader. I think the bios in this case trust the 50000 in the length field of the mbr. We really need commandline tools that can do this... And without too much magic please... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! 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?23040.933576593>