Re: [systemd-devel] Slides for November USENIX/LISA tutorial on "systemd, the Next-Generation Linux System Manager"

Zbigniew Jędrzejewski-Szmek wrote: I don't understand one part: why do you say that creating a new target requires writing C++ code? Certainly new targets don't require C++ code, as systemd is written in C! But I was trying to say that new targets with naively expected synchronization

Re: [systemd-devel] how to bind to other drivers using systemd

On Sun, Sep 27, 2015 at 11:37 PM, Flavio Leitner wrote: > I am looking for guidance on how to properly resolve driver binding > with systemd (which seems to me the best place to do that). This seems to be a too exotic and niche use case, nothing general-purpose enough to

Re: [systemd-devel] how to bind to other drivers using systemd

On Mon, Sep 28, 2015 at 08:06:50PM +0200, Kay Sievers wrote: > On Sun, Sep 27, 2015 at 11:37 PM, Flavio Leitner wrote: > > I am looking for guidance on how to properly resolve driver binding > > with systemd (which seems to me the best place to do that). > > This seems to be a

Re: [systemd-devel] Slides for November USENIX/LISA tutorial on "systemd, the Next-Generation Linux System Manager"

On Mon, Sep 28, 2015 at 10:47:43AM -0700, Chaiken, Alison wrote: > Zbigniew Jędrzejewski-Szmek wrote: > >I don't understand one part: why do you say that creating a new target > >requires writing C++ code? > > If it is in fact possible to write a > new .target unit that will serve as a new

Re: [systemd-devel] how to bind to other drivers using systemd

On Mon, Sep 28, 2015 at 8:48 PM, Flavio Leitner wrote: > On Mon, Sep 28, 2015 at 08:06:50PM +0200, Kay Sievers wrote: >> On Sun, Sep 27, 2015 at 11:37 PM, Flavio Leitner wrote: >> > I am looking for guidance on how to properly resolve driver binding >> >

Re: [systemd-devel] how to bind to other drivers using systemd

I wonder if this could be handled with a generic Type=oneshot, ExecStart=driverctl bind foo... -- Mantas Mikulėnas On Sep 28, 2015 21:48, "Flavio Leitner" wrote: > On Mon, Sep 28, 2015 at 08:06:50PM +0200, Kay Sievers wrote: > > On Sun, Sep 27, 2015 at 11:37 PM, Flavio

Re: [systemd-devel] [HEADS-UP] Please register for systemd.conf 2015 now, only 14 tickets left!

On Wed, Sep 23, 2015, 18:14 Lennart Poettering wrote: > We are close to being sold out now, only 14 tickets are still > available now. If you intend to attend, make sure to register for the > conference *now*, before it's too late and all tickets are gone. > > Register

Re: [systemd-devel] systemd and hostname supplied by DHCP

On Mon, Sep 28, 2015 at 1:19 AM Alessio Igor Bogani < alessioigorbog...@gmail.com> wrote: > Hi systemd developers and users, > > The systemd 219 brought with Yocto "Fido" can't set hostname supplied > by DHCP on my Beaglebone: > > eth0: eth0: could not bring up interface:

Re: [systemd-devel] Git development moved to github

Am Donnerstag, den 06.08.2015, 09:07 +0200 schrieb Lennart Poettering: > On Wed, 05.08.15 22:42, Thomas Meyer (tho...@m3y3r.de) wrote: > > > Hi, > > > > Regarding > > http://lists.freedesktop.org/archives/systemd-devel/2015-June > > /032652.html > > > > "The official development > > git

[systemd-devel] systemd and hostname supplied by DHCP

Hi systemd developers and users, The systemd 219 brought with Yocto "Fido" can't set hostname supplied by DHCP on my Beaglebone: eth0: eth0: could not bring up interface: Invalid argument eth0: gained carrier eth0: DHCPv4 address 192.168.205.87/24

Re: [systemd-devel] Slides for November USENIX/LISA tutorial on "systemd, the Next-Generation Linux System Manager"

On Sun, Sep 27, 2015 at 09:57:14PM -0700, Chaiken, Alison wrote: > > > The slides: http://she-devel.com/LISA15/LISA15_systemd.pdf > > Slides in other formats and systemd-nspawn containers in which to > perform the exercises are available as well; tune to > http://she-devel.com/ and look for

Re: [systemd-devel] xorg uses 100% CPU after upgrading to 226

Hi On Mon, Sep 28, 2015 at 4:56 AM, Jin Liu wrote: [...] > I tried to start X the usual way - as root, via sddm display manager. It > works fine. Seems the problem only happens when X is running as normal user. > Any directions to investigate? TBH, it sounds like an Xorg

[systemd-devel] Simple oneshot service before switching root leads to no /var mount

I'm rolling my own initrd, and I'm trying to run a oneshot service in initrd just before the switch root happens. I added this unit to the initrd and enabled it. [Unit] Description=Test Unit Requires=initrd-fs.target After=initrd-fs.target [Service] Type=oneshot ExecStart=/bin/sh -c "echo