Re: [PATCH 1/2] elf loader support for auxvec base platform string

Roland McGrath [off-list ref] writes:

There are 32 bits free now.  One can anticipate that reassigning a bit
would come up only after these are exhausted.  With prudent use, this
will take a very long time to happen.  Then the oldest CPU type string
might be retired to reuse its bit.  It seems unlikely that there will
be a single installation (root directory) that really needs to have
installed both a kernel optimized for the oldest CPU model known and a
kernel optimized for the newest CPU model known.

The kernel does not have to come from the same place as the root
filesystem.  You may want to run a new kernel with an old filesystem, or
vice-versa.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

On Mon, 2008-07-07 at 12:01 +0200, Andreas Schwab wrote:

Roland McGrath [off-list ref] writes:

quoted

There are 32 bits free now.  One can anticipate that reassigning a bit
would come up only after these are exhausted.  With prudent use, this
will take a very long time to happen.  Then the oldest CPU type string
might be retired to reuse its bit.  It seems unlikely that there will
be a single installation (root directory) that really needs to have
installed both a kernel optimized for the oldest CPU model known and a
kernel optimized for the newest CPU model known.

The kernel does not have to come from the same place as the root
filesystem.  You may want to run a new kernel with an old filesystem, or
vice-versa.

I agree, I'm pretty dubious here...

Cheers,
Ben.