From owner-freebsd-hackers Sun Nov 26 07:57:23 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA15137 for hackers-outgoing; Sun, 26 Nov 1995 07:57:23 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA15128 for ; Sun, 26 Nov 1995 07:57:12 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id HAA12512; Sun, 26 Nov 1995 07:52:32 -0800 To: gvw@brainaid.oche.de (Guido von Walter) cc: hackers@FreeBSD.ORG Subject: Re: 210R Install Feedback In-reply-to: Your message of "Sun, 26 Nov 1995 14:09:24 +0100." Date: Sun, 26 Nov 1995 07:52:32 -0800 Message-ID: <12510.817401152@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > 1. I boot my 2.0.5R system and OS/2 from the OS/2 Bootmanager. I installed > 210R to sd2 and told sysinstall not to touch the bootblock. > Afterwards the bootmanager was deactivated, and the system booted the > old 205R partition by default. Hmm. This seems to be a problem, but neither Poul-Henning and I can figure out why. I literally don't write to a disk that's not selected, yet people are telling me the boot blocks are getting touched for their first drive anyway. I can't figure it out. > 2. The sd devices: The installation made the /dev entries for the new sd2 > devices (sd2s1e ...) and for the old partitions on sd0 (sd0s3e from the > 205r), but did not notice another FreeBSD partition on sd1. I made these > entries with MAKEDEV later, no big deal, but possibly a problem for others Hmmmm. If this is easy to fix, I will.