On Thu, Oct 17, 2013 at 11:13:17PM +0200, Olaf Hering wrote:
On Thu, Oct 17, Michal Vyskocil wrote:
there is a new request [1] for mkinitrd fixing few bugs for openSUSE Factory. However there was a big effort to replace dracut as a default initrd tool, which seems to be turned on in Factory (see This will replace mkinitrd with dracut as the default initrd generator. in dracut.changes).
Hi Olaf,
Not too long ago we had this sort of "throw it in and see if it also swims" approach with another core component of the system. As said earlier, before going that route people have to sit down and compare features/code one by one to avoid regressions.
There was advocating and some code was written, but I'm sure its fulltime job to replace one core component with another.
I can only agree with ya, even if I am not sure that such strong feature/code check is needed.
So I would expect all development and fixing effort should go into dracut instead of mkinitrd (which is hard as even 13.1 won't have it as a default, so most reports are for mkinitrd). So atm the best we can do is to port mkinitrd fixes to dracut (and vice-versa?).
Are all interested people aware about the intended switch and is there a process to forward bugs/feature requests from one group to an another?
We better had a process, and a fulltimer to do the work.
Yes, that would be ideal.
In the meantime mkinitrd bugs have to be fixed once they are known.
I was not arguing about bugfixing of mkinitrd. If my email can be interpreted such way, then I am sorry and have to be more carefull about my text in the future. All I wanted is to let both* parties know about each other and think about some way how to change fixes bug reports. Otherwise all past efforts regarding dracut will became pointless. And as mkinitrd is the curent default, the most probable route is mkinitrd->dracut. * note that I am not a part of any such party, so please don't shoot the messenger. IOW better to reply to factory ML than to me. Best regards Michal Vyskocil