From owner-freebsd-current Thu Jan 7 18:26:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15041 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:26:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15036 for ; Thu, 7 Jan 1999 18:26:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02823; Thu, 7 Jan 1999 18:22:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901080222.SAA02823@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: new boot and OLD kernel In-reply-to: Your message of "Thu, 07 Jan 1999 21:20:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jan 1999 18:22:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm moving another system, aout to elf. I have been syncing the > userland move with the kernel move ... but if I put in the new boot > blocks, can I still use the old aout kernel (at least for one more > boot), or is it elf only with the new bootblocks? > > I know I have to be careful about the userland stuff (and the userland > linking issues), this is just about the new bootblocks ability to handle > the aout kernel. Does it still work? As has been stated slightly fewer than one million times 8), the new bootblocks will boot a.out kernels just fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message