From owner-freebsd-current Thu Dec 31 21:58:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06672 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:58:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06667 for ; Thu, 31 Dec 1998 21:58:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA18464; Thu, 31 Dec 1998 21:57:44 -0800 (PST) To: "Brian Haskin" cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Thu, 31 Dec 1998 14:30:31 EST." <000601be34f4$0789f9a0$0b00000a@brianjr.haskin.org> Date: Thu, 31 Dec 1998 21:57:44 -0800 Message-ID: <18460.915170264@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > new stable and current branch is the point I was trying to make. To state it > another way, will there be an easy (source not binary) route for people at > the end off the 2.2-stable branch to get to the beginning 3.0-stable branch? The answer to that question is fuzzy at the moment. It's being worked on and one hopes that it will be possible using only sources. If not, there will be some sort of binary transition kit provided. > Also I just upgraded to -current using the 12/24 snap and then cvsuping the > rest of the way. I see via /etc/objformat that I'm, by default, using elf > for the binary format. Are the elf boot blocks and kernel being used by > default also; how do I tell? file /kernel If it says it's ELF, it's elf, otherwise not. Check /etc/make.conf for other flags. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message