From owner-freebsd-current Thu Jan 7 18:22:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14715 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:22:10 -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 SAA14705 for ; Thu, 7 Jan 1999 18:22:06 -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 VAA07956 for ; Thu, 7 Jan 1999 21:20:27 -0500 (EST) Date: Thu, 7 Jan 1999 21:20:27 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: new boot and OLD kernel 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 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? ----------------------------+----------------------------------------------- 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