From owner-freebsd-current Thu Aug 27 15:57:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20935 for freebsd-current-outgoing; Thu, 27 Aug 1998 15:57:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20909 for ; Thu, 27 Aug 1998 15:57:27 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id JAA09047 for current@freebsd.org; Fri, 28 Aug 1998 09:08:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808272308.JAA09047@cimlogic.com.au> Subject: HEADS UP: 3 days to E-day To: current@FreeBSD.ORG Date: Fri, 28 Aug 1998 09:08:09 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day, In about 3 days from now, we'll be committing the last of the bits that will enable people to convert from aout to elf. Satoshi has started calling this E-day. This message is advance warning of a significant emotional event in the life of your -current system. Whether this turns out to be a _traumatic_ event will remain to be seen. For those who want to continue to update -current after E-day, you will have the choice as to when you convert. You will still be able to build and run an aout system like you always have. E-day is not the day that the big switch is thrown and you wake up with elves at the foot of the bed. Instead, what E-day really means is elf _enable_ day. To convert to elf, the brave will be able to do a make aout_to_elf and the world will automagically update all those things that a make world normally updates. There are some things that need to stay in aout format for the time being (kernel, lkms, etc since these rely on the completion of other projects). For the not-so-brave, a make aout_to_elf_build will do everything except touch the installed system. This is like a buildworld - in fact it is the equivalent of two buildworlds. At some point though, you will have to decide to bite the bullet and install the elf world using a make aout_to_elf_install. Once the upgrade procedure has been performed, the next make world you do will default to elf. Be warned that the upgrade to elf will break ports. It will take some time for the ports crew to update all the ports makefiles to cater for the elf system. We hope that moving the installed libs from /usr/local/lib to /usr/local/lib/aout will not break the installed ports. There are too many combinations to test this out though. I have tested the upgrade procedure on 2.2.5 and 2.2.6, and I'll do a final test on 2.2.7 before committing the makefile changes. I'm confident that the procedure works on a clean system like you get when you install from CD. On a non-clean system, YMMV. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message