On Sunday 27 August 2006 21:32, H. Peter Anvin wrote:
> Andi Kleen wrote:
> >
> > Just increasing that constant caused various lilo setups to not boot
> > anymore. I don't know who is actually to blame, just wanting to
> > point out that this "obvious" patch isn't actually that obvious.
> >
>
> How would that even be possible (unless you recompiled LILO with the new
> headers)? There would be no difference in the memory image at the point
> LILO hands off to the kernel.
AFAIK the problem was that some EDD data got overwritten.
>
> In order to reproduce this we need some details about your "various LILO
> setups", or this will remain as a source of cargo cult programming.
You can search the mailing list archives, it's all in there if you don't
belive me.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
