On 19 October 2011 15:20, Colin Guthrie <mag...@colin.guthr.ie> wrote: > In testing a more extensive use of systemd (i.e. using it to mount > filesystems etc. rather than using rc.sysinit) I've run into a few > problems regarding the fact that my LVM is activated in the initrd. > > Due to this, various entries in the udev db are not set. systemd uses > these missing bits to launch the local-fs.target and thus fails (even if > it's just my /home that is broken which won't really be needed). > > I've been told in various discussions with upstream that ultimately we > need to use udev in the initrd. It seems that fedora and suse at least > do this. > > I can work around it of course (we do so just now) but I'd like to get > things working as "natively" as possible with systemd if possible. > > So should we: > > a) Try to incorporate udev into our mkinitrd? > b) Switch to dracut > > I'm not an expert at this stuff, but I know that Mandriva has started > using dracut more and I think it's likely the best solution overall > seeing as it's Fedora's preferred mechanism too. > > But I didn't want to start looking at it until there is some consensus > on this - hence this email.
I think we shall not support the mkinitrd burden only by ourselves If all other are switching to dracut, we may have to too At some point, we'd extensive changes (by Luca?) for detecting MD/DM/LV, dunno if drakcut is ready to replace?
