[systemd-devel] Kdbus - dbus daemon

Distro : Arch Systemd : 224 Kdbus AUR package installed (kdbus module is not in default Arch Kernel) nspawn container : Fedora 22, systemd 219 I want to give a try to kdbus. If I read correctly the kdbus[0] website: . Am I right to understand I will no more need dbus.service and I can disable it

[systemd-devel] [udev] Limitation of capturing remove events?

Is it a limitation or bug that I can only capture remove events with purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER? I unplugged and re-plugged the specific device once before each `cat test`: [tom@localhost ~]$ cat /etc/udev/rules.d/usb.rules KERNEL=="1-14",

Re: [systemd-devel] Access to encrypted partition fails

With an encrypted home partition and a tainted kernel, access to the home partition fails. U folks are upstream to scientific Linux 7. Is there any way to recover / access to an encrypted partition that suffered from a tainted kernel crash? Some logged messages: Failed to activate Input/Output

Re: [systemd-devel] udev event on usb unpluged

>By the way, Milasan asked you to use -u and -p for udevadm monitor. See attached the logs with -u and -p parameters (seem's that it's less than without). Christophe - Mail original - De: "Tom Yan" À: "christophe jalady" Cc: "Robert

Re: [systemd-devel] udev event on usb unpluged

>I do not think you can get a useful event from udev for filesystem unmounting. ok fine. >But you should be able to get events for device removal Could someone provide the simplest .rule to catch such event ?? Christophe - Mail original - De: "Tom Yan" À:

Re: [systemd-devel] Kdbus - dbus daemon

Hi On Mon, Aug 31, 2015 at 8:02 AM, arnaud gaboury wrote: > Distro : Arch > Systemd : 224 > Kdbus AUR package installed (kdbus module is not in default Arch Kernel) > nspawn container : Fedora 22, systemd 219 > > > I want to give a try to kdbus. If I read correctly the

[systemd-devel] question about sd_bus_slot_unref()

Hi, all     I wonder why  the sd_bus_slot_unref() always returns NULL?  I expect that I can check whether the slot->n_ref ==0 by checking its return value. That is     _public_ sd_bus_slot* sd_bus_slot_unref(sd_bus_slot *slot) { if (!slot) return NULL;

Re: [systemd-devel] [udev] Limitation of capturing remove events?

On Tue, Sep 1, 2015 at 6:32 AM, Tom Yan wrote: > Is it a limitation or bug that I can only capture remove events with > purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER? > AFAIK, the former two come from the uevent itself, but the latter are always read

Re: [systemd-devel] [udev] Limitation of capturing remove events?

Also attach a log of `udevadm monitor` for your reference. On 1 September 2015 at 11:32, Tom Yan wrote: > Is it a limitation or bug that I can only capture remove events with > purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER? > > I unplugged and

Re: [systemd-devel] Backport git notes

Lennart Poettering píše v Čt 27. 08. 2015 v 18:02 +0200: > Heya, > > I used to add "Backport: bugfix" style "git notes" to systemd commits > I deemed backport-worthy. These headers have not been added to any > commits since we moved to github (primarily, because the notes > weren't > ported over