On Thu, Dec 01, 2005 at 02:12:20AM -0500, The Anarcat wrote: > On Thu Dec 01, 2005 at 07:58:32AM +0100, Sven Luther wrote: > > > > Well, yaird cannot install from a 2.4 kernel, which is why you see this > > failure. The correct upgrade way using yaird is to first upgrade to the > > sarge > > (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a > > reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once > > you are at the partitioning step, go to console 2, mount your root > > partition, > > chroot into it, mount /proc and /sys, and dpkg-reconfigure > > linux-image-2.6.14-2-k7. The other alternative is to install > > initramfs-tools, > > which knows how to install from a 2.4 kernel. I prefer using yaird myself > > though. > > Is this what the upgrade path from sarge will look like for etch > (assuming here that etch will go up to 2.6.14, or will that not happen > at all?).
No, but we are still far from the sarge release (which is scheduled for december 2006, with freeze in july or so), and we probably will have to move to having initramfs-tools the first default for it. Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. > In general, why not simply change the depends to have the whole thing > Just Work in the general case? Well, at 2.6.14 release time, initramfs-tools, and his klibc dependency, had some maturation problems, and is also regularly broken by udev, so for now, yaird, provided it works, is still the more solid solution, and at least it will fail cleanly, and give you an error message or such, while initramfs-tools may or not fail during boot time. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
