Version freeze
Version freeze for 3.0-RELEASE is set for the 17th. A new beta ISO should also be available then which, barring any bugs, will be the last.
Also, having an interesting issue with upgrades. A simple change in /etc/apt/sources.list followed by “apt-get update && apt-get dist-upgrade” seems to take care of everything *except* the new IDE drivers. 2.6.17 has no concept of these, so kudzu and whatnot don’t look for or find them. Of course, if you’re booting off an IDE drive, the kernel will panic on reboot because there is no defined ide-controller module in /etc/modprobe.conf, which is where mkinitrd is pulling info from in order to build the initrd image when the new kernel gets installed.
So I’m at a bit of a loss here. How do you detect this without actually running the 2.6.22 kernel with the drivers? I.e. if there is no current module as “piix” in 2.6.16, but you need that to properly boot 2.6.22, how do you detect or figure that out, short of booting off an Annvix install CD, seeing what IDE modules are loaded, then rebooting back into Annvix, updating modprobe.conf, and then starting the upgrade?
That’s kind of a sucky way to have to do an upgrade, but I’m not sure how to do this detection. Anyone have any ideas? Of course, this is only a problem for people booting off IDE drives; SATA and SCSI boot drives should be fine (and even with IDE drives, they may not mount on boot, but then you’ll be able to take advantage of kudzu’s detection and modify /etc/modprobe.conf accordingly).
From what I can see right now, this is the *only* upgrade issue.
