Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Sep 1998 08:24:31 +1000 (EST)
From:      John Birrell  <jb@cimlogic.com.au>
To:        eivind@yes.no (Eivind Eklund)
Cc:        jb@cimlogic.com.au, max@wide.ad.jp, committers@FreeBSD.ORG
Subject:   Re: some optimazation to make aout-to-elf-build
Message-ID:  <199809022224.IAA00229@cimlogic.com.au>
In-Reply-To: <19980902235524.57041@follo.net> from Eivind Eklund at "Sep 2, 98 11:55:24 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund wrote:
> Have you tried ELF releases?  If an ELF release works 100% (ie, allow
> a build of another release...), there shouldn't be a problem with a
> not build all of a.out, I think.  If you loose some bits, they will be
> the same bits you'll loose with an actual ELF system.

I have an elf release running now.

I often see reports of people updating to -current from either 2.2.X
or an out-of-date -current. Leaving out bits in the new build (even
just an aout->aout update) leaves us open to the "I shot myself in
the foot and it hurts" type of questions that make it look like -current
is a difficult beast to handle when it isn't really.

[Those who want to be reminded about how problematic it is following
-current on a free operating system without an adequate build process
should try NetBSD. Try asking NetBSD for a source upgrade procedure
that handles three releases and a change of executable format in a
single command!].

Once people have upgraded to elf, they can leave aout in the past by
setting NOAOUT, then a `make world' will behave like it always has.

Just before we go for a 3.0-RELEASE, I'll remove the legacy cruft from
the `make world' process, and set the default object format to elf.
Hopefully by then kld will be complete, the new boot loader will
be in use and we'll be running ELF kernels.

-- 
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809022224.IAA00229>