The latest systemd upgrade got me into some reading about systemd hook. I have quickly gone over the wiki and the man pages. I was wondering if it safe to add systemd and remove udev from mkinitcpio.conf.
My current mkinitcpio.conf hook list.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck resume"
Remove udev and add systemd.
HOOKS="base systemd autodetect modconf block filesystems keyboard fsck resume"
Last edited by donniezazen (2013-09-19 02:57:48)
Yes, this is safe. I have been running with systemd in my initramfs for a few months now, and all is well. You just have to be careful if you use some of the other hooks as not all of them have been ported yet. I think that there has already been significant work on this, but I don't think any of it has actually made it into a released version of mkinitpcio. These would be things like the encrypt hook and maybe the mdadm hook (though you should probably be using mdadm_udev anyway if you need that).
But as far as your setup goes, it should be fine.
The help for the hook still mentions other things may go haywire with it, so I'm steering clear (but I rely on encrypt, lvm2, resume and shutdown - while I could delete resume without much worry, the others I need to work).
Yeah, in your case cfr, you should stay away from this.
Here is the mailing list discussion about the topic: http://www.mail-archive.com/arch-projec … 03348.html
I removed it in my primary initramfs. But I use a separate mkinitpcio.conf for my fallback. Since I use btrfs, and have had problems in the past (though nothing severe), I have the fallback include all the btrfs tools and the 'base' hook so that I have a minimal filesystem and tools to fix my shit. So then I just have 'break=premount' in my kernel command line, and I can get to a system with which I can fix my system if necessary.