[systemd-devel] About systemd in initrd support

2014-08-23 Thread Luca Bruno
I'm going to do an experiment with NixOS: replace the whole current initrd process made of scripts and hooks with systemd. Before doing any work however I'd like to hear whether systemd in initrd is still wanted in the future, or there's any possible idea about dropping this support. Also, apart

Re: [systemd-devel] About systemd in initrd support

2014-08-25 Thread Luca Bruno
Thank you all for the replies. After the first answers I've ported the initrd to systemd (only the basic stuff, no luks, lvm, etc.) and works very fine. Except one thing, that I hoped to find in dracut but does not seem to do anything special about it. It just goes through switch-root it seems.

Re: [systemd-devel] About systemd in initrd support

2014-08-25 Thread Luca Bruno
As you already mentioned, you'd have to make sure you manage to pass through the state correctly. Thanks. Is there any docs I can read about this or just read the code? It appears that systemd dumps the state into a file, and afterwards it's passed to the new systemd instance.

[systemd-devel] Luks + lvm in initrd

2014-10-28 Thread Luca Bruno
Hi, I'm going on with my work to have systemd in initrd on NixOS (using dracut is a little complicated at the moment). Everything works fine, I've ported luks and lvm and both work separately. However I'm hitting a problem when using luks and lvm on top of luks. SETUP Software: systemd 212, lvm

Re: [systemd-devel] Luks + lvm in initrd, tracking the issue

2014-10-31 Thread Luca Bruno
I've tracked down the issue a little. sysroot.mount requires/after dev-vg-lv.device. System start, dev-vg-lv is inactive. vgchange -a y - dev-vg-lv active. vgchange -a n - dev-vg-lv inactive. At this point, unit-job of dev-vg-lv is NULL (sometimes also happens when I don't run vgchange, but I

Re: [systemd-devel] Luks + lvm in initrd, complete scenario

2014-10-31 Thread Luca Bruno
Sorry for the spam. Further tracking down the issue. I think I've come to a conclusion of the scenario: S1.service requires/after D.device and S2.service S1 is activating, thus starts D and S2 S2 starts, which activates D and deactivates D A can now start because D has no job running [1], but D

Re: [systemd-devel] Something wrong with sd_journal_add_match

2016-06-22 Thread Luca BRUNO
On Wednesday 22 June 2016 12:10:14 Dennis Semakin wrote: > The task is to obtain messages _only_ with specified fields (e.g. > MESSAGE_ID=bla-bla-bla). > And problem is that I can see incoming messages even when sending tool is > not running (no execution). Looks like I got all messages from