>On Sun, Feb 27, 2005 at 02:05:45PM -0500, Harry Cochran wrote: >> 8.1 Check your 2.4 partition scheme >> >> It is relatively easy to set up a partition scheme that will "work" for >> a while, but then stop working when root starts to fill up. For example:
On Sun, Feb 27, 2005 at 07:36:45PM -0500, Stuart Brady wrote: >This was due to using an incorrect partition scheme in the first place. >I'm not sure that this belongs in a HOWTO that explains how to upgrade >from 2.4 to 2.6. >Documentation explaining how to use the palo partition as the /boot >partition seems worth having, but it's surely a separate issue. >From a newbie point of view, I think it's important to know that you might have a partition scheme where you are booting something like 3/boot/vmlinux that might just stop working if root starts to fill up and because of format-as=2 you have a chance to fix it on a 2.6 upgrade. >> I'm the conservative type, so I don't load from "testing". At the time >> of this writing, the 2.6 kernels in "unstable" are 2.6.8-2-32, >> 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. >I don't get this -- testing is safer than unstable. Thanks Stuart, I finally sat down and read the explanation of unstable and testing. Someone else told me that unstable was more reliable that testing which clearly isn't the case. Sorry for putting my misunderstanding in the document. Regards, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]