>>> 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...
What's a problem with one cylinder ? I use one cylinder and not seen any
problems...
-
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/