From owner-freebsd-stable Sat Jan 23 15:47:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03147 for freebsd-stable-outgoing; Sat, 23 Jan 1999 15:47:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03141 for ; Sat, 23 Jan 1999 15:47:03 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxew.lx.ehu.es [158.227.99.226]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id XAA05282; Sat, 23 Jan 1999 23:54:10 +0100 (MET) Message-ID: <36AA5310.A4A41C1E@we.lc.ehu.es> Date: Sat, 23 Jan 1999 23:54:08 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: Matthew Hagerty CC: freebsd-stable@FreeBSD.ORG Subject: Re: 3.0 to Stable and ELF Kernel References: <4.1.19990123161158.009e7970@firebat.wolfepub.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Hagerty wrote: > I just CVSUPed my 3.0-Release with the RELENG_3 tag. Then I did a > makeworld and makeinstall. I also compiled a custom kernel. All the steps > went fine, no errors of any kind, but when I typed make install (for the > kernel) I received a message that said I should ensure my /boot/loader can > handle ELF kernels. I went ahead and did the make -DFORCE install and > rebooted. Needless to say, I cannot boot with the kernel I made, however I > can boot kernel.GENERIC. > > Is 3.0 an ELF system? I was under the impression that it was. Also, is > the system I just made buy CVSUPing and rebuilding an ELF system? Just out > curiosity I made a simple C program and compiled it. I got an a.out binary. > > I have seen many references on the web site to commands like aout-to-elf > and such. Is this a step I have to perform? > If you are upgrading from a 2.2.x system, you must make the world using the "aout-to-elf" target. From /usr/src/Makefile: # ---------------------------------------------------------------------------- # # Upgrading an i386 system from a.out to elf format # # # The aout->elf transition build is performed by doing a `make aout-to-elf' # or a `make aout-to-elf-build' followed by a `make aout-to-elf-install'. # You need to have at least 320 Mb of free space for the object tree. # # The upgrade process checks the installed release. If this is 3.0-CURRENT, # it is assumed that your kernel contains all the syscalls required by the # current sources. # # For installed systems where `uname -r' reports something other than # 3.0-CURRENT, the upgrade process expects to build a kernel using the # kernel configuration file sys/i386/conf/GENERICupgrade. This file is # defaulted to the GENERIC kernel configuration file on the assumption that # it will be suitable for most systems. Before performing the upgrade, # replace sys/i386/conf/GENERICupgrade with your own version if your # hardware requires a different configuration. # # The upgrade procedure will stop and ask for confirmation to proceed # several times. On each occasion, you can type Ctrl-C to abort the # upgrade. # # At the end of the upgrade procedure, /etc/objformat is created or # updated to contain OBJFORMAT=elf. From then on, you're elf by default. # # ---------------------------------------------------------------------------- Hope that helps, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message