Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS

[Norbert Tretkowski <tretkowski@inittab.de>]

* Steve Langasek wrote:
> On Sun, Aug 15, 2004 at 01:47:13PM +0200, Norbert Tretkowski wrote:
> > * Steve Langasek wrote:
> > > The DS15, DS25, DS45, and ES47 alpha systems require a kernel
> > > built with LEGACY_START_ADDRESS=n. Some MILO-based systems,
> > > however, can't boot *without* LEGACY_START_ADDRESS being set.
> > > Please add another kernel-image variant so that Debian can
> > > properly support both types of systems.
> 
> > > http://lists.debian.org/debian-alpha/2004/08/msg00012.html
> 
> > Should we fix this for sarge? I suppose the d-i people will kill
> > us when we introduce a new flavour for the 2.4.26 kernel-images.
[...]
> It's probably best to make this change coincide with a package name
> change so that systems don't break on upgrade -- either the
> introduction of 2.4.27, or the kernel flavor rename that I
> understand you have pending.

The flavor rename will be post-sarge, so I'm going to use
LEGACY_START_ADDRESS=n for the 2.4.27 images, which I'm currently
preparing.

Thanks, Norbert