Messages in this thread | | | Date | Thu, 8 Aug 2002 09:37:56 +0200 (CEST) | From | Ingo Molnar <> | Subject | Re: [bug, 2.5.29, (not IDE)] partition table (not) corruption? |
| |
On Thu, 8 Aug 2002, Marcin Dalecki 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.
this particular testbox has seen *thousands* of development kernels of all sizes, and i often have filled up the complete /boot partition. It is very unlikely that this harmless (and not too big) 2.5.29 kernel would have been the first one to trigger a 'wrong' CHS combination. Especially since 2.4 kernels with exactly the *same* bzImage (and same lilo) work just fine.
Ingo
- 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/
| |