From owner-freebsd-arch Tue Oct 24 11: 7:37 2000 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7F5D037B479 for ; Tue, 24 Oct 2000 11:07:31 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9OI7Tn87688; Tue, 24 Oct 2000 12:07:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA17271; Tue, 24 Oct 2000 12:07:29 -0600 (MDT) Message-Id: <200010241807.MAA17271@harmony.village.org> To: Marcel Moolenaar Subject: Re: PLEASE REVIEW: buildworld fix for 3.x->RELENG_4 upgrades Cc: arch@freebsd.org In-reply-to: Your message of "Tue, 24 Oct 2000 13:57:59 EDT." <39F5CDA7.67288AD@cup.hp.com> References: <39F5CDA7.67288AD@cup.hp.com> <39F532B2.BDE29048@cup.hp.com> <39F5185C.62A92866@cup.hp.com> <39F4ADC9.920A9BB5@sftw.com> <39F39B57.8726A8BA@quack.kfu.com> <39F1A95B.86116571@quack.kfu.com> <20001022094114.A14613@dragon.nuxi.com> <200010230405.WAA04356@harmony.village.org> <200010232354.RAA11591@harmony.village.org> <200010240540.XAA13044@harmony.village.org> <200010241254.GAA15044@harmony.village.org> Date: Tue, 24 Oct 2000 12:07:29 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ Moved to arch@ since this isn't a developers only issue ]] : So, either we need to install the boot stuff when we install the kernel : or put the device hints back into GENERIC (and removing the logic as : illustrated by the patch). I see the problem now. It is one of ordering. We could easily install a default device.hints and a corrected boot.conf file as part of the upgrade process, but we make it needlessly complex due to this check. This makes it harder to do the upgrade path. I see a couple of ways around this. One is to add a check to see if you are running 4.x or older and be helpful by doing an implicit copy of GENERIC.hints to /boot/device.hints as well as doing an install of the new boot loader in /boot (since really that what the checks you are proposing removing effectively check for). That is to say these things would be implied if there was no /boot/device.hint file pre-existing (we don't want to clobber it) (and that might be a better check than an OS version, come to think of it). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message