From owner-freebsd-hackers Mon Dec 11 08:35:34 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA25926 for hackers-outgoing; Mon, 11 Dec 1995 08:35:34 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA25915 Mon, 11 Dec 1995 08:35:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id IAA15559; Mon, 11 Dec 1995 08:33:59 -0800 To: Bruce Evans cc: phk@freebsd.org, hackers@freebsd.org Subject: Re: sysinstall considered harmful! In-reply-to: Your message of "Tue, 12 Dec 1995 03:13:12 +1100." <199512111613.DAA16770@godzilla.zeta.org.au> Date: Mon, 11 Dec 1995 08:33:59 -0800 Message-ID: <15557.818699639@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org Precedence: bulk > I tried installing on fd1. The message > > "Writing partition information to drive 0" > > was printed and the MBR was clobbered (from all 0's to all 0's except > for 0xaa55 at the end) so devs[0]->enabled must have been set. I've just committed a fix that may clobber this bug to sysinstall in 2.1 and -current - could I possibly prevail upon you to grab the latest sysinstall and try your test scenario again? I'm not exactly sure what you did, but I did find something that might just have caused the symptoms. If so, I owe Poul-Henning a nice Czech pilsner. I also tried out your suggestion of checking errno for EACCES in the deviceTry() code. Thanks!! Jordan