I’m probably far from being a good project leader. The lack of time is one of the reason, but I think I could do better anyway, as I was particularly quiet these 2 last months. So I use that time, where I’m waiting before driving to the airport to give a status.
I was quiet, but still working on it as time permitted, and willing to solve the Fedora 18-20 support issues I had for a very long time now. And it seems that with the latest patches pushed this week, I’m good on that side. I’ve been able to do a full backup/restore of my Fedora 20 VM in automatic mode without issue ! That’s the first time, and was particularly happy that after 9 months of development around 3.2, I could achieve that. The other good news, is that it is still working fine for RHEL 6 e.g. as I also did a full cycle this week.
Ok, so life is nice. Well, as you know, nothing’s perfect 😉 So I still have an issue with RHEL 7. In fully automatic mode, eveything works fine, except that the restored VM doesn’t start due to an issue on the UUID in the initramfs.
I’ll test by recreating that initramfs after restore, and hopfully, dracut will do the job for me. But as I’ll be travelling in the US all next week, I thought it was good to publish a last beta before leaving, so that the community could also test and report what happens on other distros or on other configurations.
Note that very few other bugs have been fixed. I’m more interested for this first 3.2 version to have it work finally on all new systemd distros as much as I can, even if some features are still not fully working (see trac for details).
Compared to my last post on the subject, some points have been improved:
- the network stack is now launched as long as a network backup has been done originally, even if you boot from the ISO image directly, and not through PXE. You may still choose from where to restore afterwards, but at least network is up
- solve some /bin vs /usr/bin issues for pre-fedora 18 and systemd distros which were not working anymore (Cf: #741)
- fix for a lack of keyboard discovery
- fix some perl issues in some cases (Cf: #755)
- force LV creation which on RHEL7 now asks a question in case something was already there before (Cf: #753)
- Optimize modules list computation between mindi and restore init script and do not load modules list twice anymore
- Force generation of hardlinks for busybox to avoid package build problem on some distro with inexistant links at build time (recent SLES)
- Fix busybox 1.21.1 to support back old distributions such as RHEL3 and RHEL4 or SLES9 by avoiding usage of the struct tpacket_auxdata
- Fix isolinux.bin and ldlinux.c32 locations for recent Debian distro
So maybe even more has been fixed than I considered initially in fact. Anyway, I’ll try to avoid to stay so long without publishing new versions to test. It’s a promise, but will be difficult to keep so don’t hold your breath !
The goal is to publish 3.2.0 final before Christmas, and to work on a hopefully final 3.0.5 version backporting some of the previously mentionned fixes coded in 3.2 for those of you who prefer to stay on that branch, which will be maintained a bit in parallel as long as 3.2 is not tested more. I think that you’ve been patient with me, so I also have to be patient myself before more users adopt the new stable branch.
Hopefully you’ll get a new blog article for the announce in less than a month !