From owner-freebsd-alpha Fri Jul 21 14: 9: 9 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 A19C237BCFC for ; Fri, 21 Jul 2000 14:09:05 -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 OAA05136; Fri, 21 Jul 2000 14:09:53 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: Dirk Kleinhesselink Cc: "Jordan K. Hubbard" , mjacob@feral.com, alpha@FreeBSD.ORG Subject: Re: 4.1-20000719-RC#2 In-reply-to: Your message of "Fri, 21 Jul 2000 13:57:08 PDT." Date: Fri, 21 Jul 2000 14:09:53 -0700 Message-ID: <5133.964213793@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > At least for myself and several others who had this problem: > > you will never get to the install setup up if your system already has a > BSD (Tru64/NetBSD/Linux (using BSD disk label) and from Matt's example, a > FreeBSD disk with the /sbin/init clobbered) or OpenVMS system disk. > FreeBSD will load the kernel, load the install MFS but then will fail to > find the MFS init routine -- I guess it will try to look for it on the > BSD/VMS disk and will fail to find it. Erm, if that's the case, something seriously does not make sense or is broken in a very fundamental way. When the md driver is compiled in with MD_ROOT set, this happens: SYSINIT(md_root, SI_SUB_MOUNT_ROOT, SI_ORDER_FIRST, md_takeroot, NULL); Which should put the MFS root *first* in the root mount list. Any existing partitions should have no effect on this. - Jordan > > On Fri, 21 Jul 2000, Jordan K. Hubbard wrote: > > > > > > > > > > > Seems like it would be an easy thing to try to reproduce: just put a > > > > couple of disks on the system and install Tru64/NetBSD/Linux/OpenVMS on > > > > one of them and then try to install FreeBSD on the other disk... > > > > > > You don't even have to do that. Just take a previous FreeBSD installation and > > > move /sbin/init aside and create a zero length /sbin/init. > > > > I'm still not sure I understand how that should have any effect. > > You're doing an install here, right? And the install is going to > > newfs the root filesystem and repopulate it with distribution bits, > > right? > > > > If you're somehow electing to preserve the existing root partition > > and/or not extract, at a minimum, bindist then this isn't an > > installation at all, this is some sort of "you must know what you're > > doing well enough not to shoot your feet off" quasi-upgrade operation. > > Please clarify. Thanks. > > > > - Jordan > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message