Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI

Hi, > From: Bastien Nocera [mailto:had...@hadess.net] > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch > exported by ACPI > > On Tue, 2017-06-20 at 02:45 +, Zheng, Lv wrote: > > Hi, > > > > > From: Bastien Nocera [mailto:had...@hadess.net] > > > Subject: Re:

[systemd-devel] [ANNOUNCE] All Systems Go! 2017 CfP is now open!

Hi! The All Systems Go! 2017 Call for Participation is now open! https://cfp.all-systems-go.io/en/ASG2017/cfp/session/new This year All Systems Go! 2017 will take the place of systemd.conf where the systemd community meets! ASG! 2017 is run by the same people as systemd.conf 2015 and 2016, but

Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI

On Tue, 2017-06-20 at 02:45 +, Zheng, Lv wrote: > Hi, > > > From: Bastien Nocera [mailto:had...@hadess.net] > > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable > > LID switch exported by ACPI > > > > On Mon, 2017-06-19 at 01:43 +, Zheng, Lv wrote: > > > > > > > > > >

Re: [systemd-devel] Systems-nspawn host-only networking?

To summarise my email response from yesterday, Is there a way within the .nspawn unit file to explicitly set host networking without removing --network-veth from the systems-nspawn@.service unit file. Many thanks, Sam > On 20 Jun 2017, at 19:13, Samuel Taylor wrote:

[systemd-devel] [RFC PATCH v6 2/5] ACPI: button: Add an optional workaround to fix an event missing issue for old userspace

There are platform variations implementing ACPI lid device in different ways: 1. Some platforms send "open" events to OS and the events arrive before button driver is resumed; 2. Some platforms send "open" events to OS, but the events arrive after button driver is resumed, ex., Samsung

[systemd-devel] [RFC PATCH v6 1/5] ACPI: button: Add a workaround to fix an order issue for old userspace

There are platform variations implementing ACPI lid device in different ways: 1. Some platforms send "open" events to OS and the events arrive before button driver is resumed; 2. Some platforms send "open" events to OS, but the events arrive after button driver is resumed, ex., Samsung

[systemd-devel] [RFC PATCH v6 3/5] ACPI: button: Rework lid_init_state=ignore mode

There are platform variations implementing ACPI lid device in different ways: 1. Some platforms send "open" events to OS and the events arrive before button driver is resumed; 2. Some platforms send "open" events to OS, but the events arrive after button driver is resumed, ex., Samsung

Re: [systemd-devel] systemd-networkd different static ip and dhcp in different networks

On Wed, Jun 21, 2017 at 10:55 AM, Jakob Schürz wrote: > Hi! > > I'm fiddeling around with network, to find out, how it works. I know, > it's not made for use in Laptops moving in different networks. > > But there is a solution with wpa_supplicant to connect to

[systemd-devel] systemd-networkd different static ip and dhcp in different networks

Hi! I'm fiddeling around with network, to find out, how it works. I know, it's not made for use in Laptops moving in different networks. But there is a solution with wpa_supplicant to connect to different WLANs. I also found a Solution when i connect to my mobile phone, using usb-thetering for