Uz.ytkownik Ingo Molnar napisa?:
> On Wed, 7 Aug 2002 Andries.Brouwer@cwi.nl wrote:
>
>
>>LILO without "linear" or "lba32" is inherently broken: it will talk CHS
>>at boot time to the BIOS and hence needs a geometry and install time,
>>and nobody knows the geometry required. So, if LILO doesnt break, this
>>is pure coincidence.
>
>
> well, lilo without linear worked for like years on this box ...
You have to take in to account that by creating a new kernel image
you are storing it sometimes after a long long time at perhaps maybe
another block group far away. This is becouse ext2 suddenly may feel
like doing so...And surprisingly you have to teach lilo about the new
far away sectors becouse basic C/H/S addressing can't reach them
anylonger. Been there seen that frequently enough.
It would be maybe informative if you could actually provide the
first sector address used by the inode corresponding to vmlinuz.
At least this way one could resolve the issue definitively.
>>And you talk about corruption, and I am surprised again. Have you
>>verified that there really was a difference? Or do you only suspect
>>corruption because LILO has problem? (In that case I can assure you that
>>there was no corruption.)
>
>
> you are right, there was no corruption most likely. And the IDE subsystem
> is most definitely innocent.
I have told you :-).
BTW.> Please don't consider RH lilo "fairly standard" it *is* messing
with the geometry issues, since in esp. limbo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:15 EST