Re: [systemd-devel] [WIP PATCH 2/4] ACPI: button: remove the LID input node when the state is unknown

On Tue, Jun 06, 2017 at 12:22:09PM +0200, Benjamin Tissoires wrote: [...] > > This is because the aml table puts many Notify(LID, 0x80) in various > > control methods. > > And not one of them but multiple of them will be invoked by various OS > > drivers during suspend/resume period. > > I think

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

On Tue, Jun 06 2017, Steve Dickson wrote: > Hello, > > On 05/29/2017 06:19 PM, NeilBrown wrote: >> >> Systemd does not, and will not, support "bg" correctly. >> It has other, better, ways to handle "background" mounting. > The only problem with this is bg mounts still work at least > up to 4.11

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

2017-06-06 20:07 GMT+02:00 Steve Dickson : > Finally, the whole idea of systemd randomly/silently > strip off mount options is crazy... IMHO... Personally, I would prefer if systemd simply logged a warning/error message but would *not* strip the bg option. -- Why is it that

Re: [systemd-devel] About stable network interface names

06.06.2017 16:20, Martin Wilck пишет: > As others have remarked already, PCI bus-device-function is subject to > change. > Can device and function really change? My understanding is that device part is determined by bus physical wiring and function by PCI card design; this leaves bus as volatile

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

Hello, On 05/29/2017 06:19 PM, NeilBrown wrote: > > Systemd does not, and will not, support "bg" correctly. > It has other, better, ways to handle "background" mounting. The only problem with this is bg mounts still work at least up to 4.11 kernel... It appears there is a problem with a 4.12

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Tue, Jun 06, 2017 at 04:33:11PM +0200, Krzysztof Jackiewicz wrote: > Hi, > > I noticed that when systemd is configured with libcryptsetup option enabled > it will link to libcryptsetup which is distributed under GPL 2.0. It seems > like a license conflict to me. Can anyone explain it? A

[systemd-devel] Systemd license vs. libcryptsetup license

Hi, I noticed that when systemd is configured with libcryptsetup option enabled it will link to libcryptsetup which is distributed under GPL 2.0. It seems like a license conflict to me. Can anyone explain it? Thanks in advance. Krzy ___ systemd-devel

Re: [systemd-devel] About stable network interface names

On Mon, 2017-05-29 at 02:35 +0200, Cesare Leonardi wrote: > I ask because I've done several tests, with different motherboards, > adding and removing PCI-express cards and that expectation was not > satisfied in many cases. > > For example, in one of those tests I initially had this setup: >

Re: [systemd-devel] [WIP PATCH 2/4] ACPI: button: remove the LID input node when the state is unknown

Hi Lv, On Jun 05 2017 or thereabouts, Zheng, Lv wrote: > Hi, Benjamin > > > From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com] > > Subject: [WIP PATCH 2/4] ACPI: button: remove the LID input node when the > > state is unknown > > > > Because of the variation of firmware

Re: [systemd-devel] [WIP PATCH 3/4] ACPI: button: Let input filter out the LID events

On Jun 05 2017 or thereabouts, Zheng, Lv wrote: > Hi, Benjamin > > > From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com] > > Subject: [WIP PATCH 3/4] ACPI: button: Let input filter out the LID events > > > > The input stack already filters out the LID events. So instead of > >

Re: [systemd-devel] [WIP PATCH 4/4] ACPI: button: Fix lid notification locks

On Jun 05 2017 or thereabouts, Zheng, Lv wrote: > Hi, > > > From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com] > > Subject: [WIP PATCH 4/4] ACPI: button: Fix lid notification locks > > > > From: Lv Zheng > > > > acpi/button.c now contains the logic to avoid