>> mv /usr/src/v2.3.9/linux/arch/i386/boot/zImage /vmlinuz239 will
>> internally copy the file to the root to new sectors, than delete
>> the old kernel. Result: The new image will be placed beyond
>> the magic limit. The boot will fail
> The easiest way around this whole issue is to make a separate
> /boot directory (small, about 8MB) partition that is physically
> located below the 1024 cyl limit. Always place your boot images
> here. Once you've done this, you will never have to worry about
> such things-
I normally allocate 16M to /boot since on most of the drives I use,
that corresponds to two [logical] cylinders, and that's the smallest
number of cylinders that all versions of fdisk can reliably allocate
to a partition...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/