On Tue, Sep 3, 2013 at 6:46 AM, Frank Steinmetzger <war...@gmx.de> wrote: > Hey list > > after the many discussions here about systemd I had a flash of > objectivity (“Who cares if people rant about Lennart, the concept seems > sound and I don’t care about separate /usr”). So I wanted to try systemd > on my netbook. > > I cloned the / partition from sda2 to sda7 and chrooted into it. In > there I followed the systemd Gentoo wiki¹, i.e. I configured the kernel, > installed systemd, added "-consolekit systemd" to my use flags, rebuilt > world with --new-use and added init=/usr/lib/systemd/systemd to the > kernel cmdline. > > Rebooting works until the point of mounting /home, which is a LUKS > container. I get the message: > "A start job is running for dev-mapper-home.service" > and eventually a timeout and prompt for root password or Ctrl-D. > > The wiki references a bug report that /etc/crypttab was ignored. Well, I > didn’t have one, but apparently my old crypt setup was heeded (because > systemd knew that I wanted sda5 mounted as home).
Mmmh. I don't use LUKS, but from what I understand, systemd generates the unit files necessary to mount encrypted partitions, and to do this it needs /etc/crypttab, in the same manner that it needs /etc/fstab to generate the unit files for the normal partitions. http://www.freedesktop.org/software/systemd/man/systemd-cryptsetup-generator.html > I tried researching the problem. One I found was a Gentoo forum thread > about LVM. I found out that I was missing CONFIG_DM_UEVENT. But enabling > it didn’t help either. I found files in the partition’s /dev directory, > which hinted that DEVTMPFS_MOUNT was not set. But I don’t suppose that’s > really a problem. I would add it anyway. > Does any of you have experience with this combination and would like to > share it? Thanks. > > ¹ http://gentoo-en.vfose.ru/wiki/Systemd > > > > On a sidenote, for some reason, grub2 doesn’t find the kernel if I keep > the menuentry’s search commands which are created by grub2-mkconfig. > Only if I remove all the search --uuid...yadda yadda..., the entry > boots. > The boot partition (where the grub files lie) is still my normal / on > sda2. It then boots the systemd installation on sda7 which was detected > by os_prober. Are you sure it's not under the "advanced" submenu? One question: how is the /etc/fstab file in the systemd installation? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
