Well, it's official: Mandriva 2008.1 is now out and available. Time to start gearing up for the barrage of bugfix updates. =) On a similar note, 2007.0 is almost EOL.. you've got a few days left to upgrade to something newer before being left without security updates. April 13 is the day that 2007.0 support is terminated and 2007.1 goes into base/core update mode (essentially, all non-desktop-related stuff will get fixed, nothing else). The product lifetime map is here: http://www.mandriva.com/en/security/productlifetime.

On a side note... using udev with mdadm sucks. I don't know who changed it, but I had to reboot my sunfire about a dozen times yesterday to get it to boot properly... I have 7 md devices, and invariably on each boot, one or two would fail to assemble for some reason. Poking around in /etc/rc.d/rc.sysinit, the md initialization was completely removed and I suspect udev is supposed to take care of it instead. Well, after having to boot a dozen times to get the silly system up and running, I decided to put back the md initialization in rc.sysinit so that at least I know on subsequent reboots the system will actually come up fully.

Other than that, the only downside I've seen so far is installation on a fully md system (everything is RAID1 -- /boot, swap, you name it). Well, the installer is supposed to use LILO when /boot is a md device according to Pixel, but the installer doesn't actually install LILO, so you get bootloader install errors. Booting into rescue mode and doing the grub install manually fixes the problem (but you have to do the full grub install as not even the grub support files are installed in /boot/grub and no menu.lst is generated either). Then the system will come up. Note to developers: I've been using grub on fully-RAID1 systems for years. You do not need LILO for this. grub works just peachy.

There's still something wonky with my menu.lst tho as installkernel fails to update menu.lst when installing a new kernel. Not quite sure what the deal there is, seems like a pretty strange error:

[root@hades servers]# installkernel 2.6.24.4-server-1mnb
INTERNAL ERROR: hd0 has no mapping in device.map (when translating (hd0,0)/grub/annvix-splash.xpm.gz)
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/bootloader.pm:1564
bootloader::grub2dev_and_file() called from /usr/lib/libDrakX/bootloader.pm:1583
bootloader::grub2file() called from /usr/lib/libDrakX/bootloader.pm:284
bootloader::read_grub_menu_lst() called from /usr/lib/libDrakX/bootloader.pm:215
bootloader::read_grub() called from /usr/lib/libDrakX/bootloader.pm:168
bootloader::read() called from /usr/sbin/bootloader-config:64
[root@hades servers]# cat /boot/grub/device.map 
(hd0)   /dev/sda
(hd1)   /dev/sdb

As I can see, hd0 is definitely noted in the device.map, so I'm not sure what the deal is.