From owner-freebsd-current Wed Nov 11 06:05:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18232 for freebsd-current-outgoing; Wed, 11 Nov 1998 06:05:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18224 for ; Wed, 11 Nov 1998 06:04:56 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id JAA21493; Wed, 11 Nov 1998 09:02:11 -0500 (EST) Date: Wed, 11 Nov 1998 09:02:11 -0500 (EST) From: Chuck Robey To: "Jordan K. Hubbard" cc: Julian Elischer , Peter Wemm , Mike Smith , current@FreeBSD.ORG Subject: Re: Is it soup yet? :-) In-Reply-To: <9940.910772319@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Nov 1998, Jordan K. Hubbard wrote: > > the ability to run on old bootblocks is how shall I say... > > "required". > > Well, you have and have always had just two options the minute we pull > the elf kernel switch: You switch customers to the 3-stage boot by > dropping a /boot.conf file into place which calls /boot/loader (which > you also install along with the 3.0 upgrade) or you relabel them so > they look just like freshly installed 3.0.x systems; it's your choice > whether you want to go for minimal impact or minimal difference. Trouble is, with old bootblocks, that "drop boot.conf" trick doesn't work, it just hangs. To get the elf kernel booted, you have to update the bootblocks, *then* they can use both. Julian's request is dead as it stands, you can't do that. To get the elf kernel, you need newer bootblocks, which is why I suggested detecting the old ones, and maybe refusing to install an elf kernel. My own kernel, which I tested it on, didn't use klms or klds. Linking doesn't matter, it's loading that's affected. Once the kernel gets into place, that's when linking becomes an issue (if it is at all) right? Not sure how to detect sufficiently new bootblocks ... it might not be possible. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message