From owner-freebsd-alpha Fri Jul 21 14:12: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BDC1437C02D for ; Fri, 21 Jul 2000 14:12:02 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05179; Fri, 21 Jul 2000 14:12:56 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: mjacob@feral.com Cc: "Jordan K. Hubbard" , Dirk Kleinhesselink , alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 14:01:05 PDT." Date: Fri, 21 Jul 2000 14:12:56 -0700 Message-ID: <5176.964213976@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The presumption here is that sysinstall is mounting the wrong disk. This has > nothing to do with preservation of old data. Well, I'm still not sure how sysinstall could "mount the wrong disk" unless you explicitly told it to do so or major/minor devices are broken so badly that /dev/sd0a actually points to SCSI disk #2 rather than #1 on your system (which I kinda doubt). When you actually come up, mounting the right disk as root is more of a loader issue and setting your root device properly; it has nothing to do with sysinstall. > On isaac.nas.nasa.gov, putting boot.flp on the *second* disk, I ran into the > 'going nowhere w/o my init' problem as soon as I selected a terminal type. > NetBSD was installed on the first && third disks. I really don't know what you mean by "putting boot.flp on the second disk" - you mean you dd'd the boot.flp image straight onto the beginning of your SCSI drive? I'm getting even more confused. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message