Re: [systemd-devel] [PATCH v5 3/3] udev: input_id - use ABS_MT_SLOT{-1} to exclude non touch screen devices

On Mon, Jun 01, 2015 at 10:43:39PM +0200, Andreas Pokorny wrote: > Peek at the ABS_MT_SLOT-1 axis. Expect that touch screens only > have axes inside the MT range. > --- > src/udev/udev-builtin-input_id.c | 4 > 1 file changed, 4 insertions(+) > > diff --git a/src/udev/udev-builtin-input_id.c

Re: [systemd-devel] [systemd-commits] load-fragment: use UNESCAPE_RELAX flag to parse exec directives

Hi, Not sure I agree with the commit below. (In particular as I'm looking at converting this code into using unquote_first_word.) On Mon, Jun 1, 2015 at 9:10 AM, Daniel Mack wrote: > commit 22874a348fb1540c1a2b7907748fc57c9756a7ed > Author: Daniel Mack > Date: Mon Jun 1 17:49:04 2015 +0200 >

Re: [systemd-devel] Visible pull requests on github? [was: [PATCH] mount-setup: create /run/systemd/netif/links/ before accessing]

02.06.2015 6:56, Martin Pitt пишет: Hello all, systemd github import bot [2015-06-01 20:06 -]: Patchset imported to github. Pull request: I've see

[systemd-devel] Visible pull requests on github? [was: [PATCH] mount-setup: create /run/systemd/netif/links/ before accessing]

Hello all, systemd github import bot [2015-06-01 20:06 -]: > Patchset imported to github. > Pull request: > I've seen these "imported into github" mess

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

Hey David, David Herrmann [2015-06-01 20:12 +0200]: > As of today we've disabled git-push to fd.o. The official development > git repository is now at github [1]. Can you copy the committer list from fd.o? Right now it seems the only person that can actually push to systemd-devs/systemd is you (h

Re: [systemd-devel] Starting up service after my openvpn connection turns up

В Mon, 1 Jun 2015 16:36:38 -0400 Matthew Karas пишет: > I am trying to start a dropbear service after my openvpn service starts up. > > --- > [Unit] > Description=SSH Per-Connection Server > Wants=dropbearkey.service > After=syslog.target dropbearkey.service > Wan

Re: [systemd-devel] [PATCH] Partially revert "ma-setup: simplify"

On Mon, Jun 01, 2015 at 12:36:25PM -0400, Mimi Zohar wrote: > On Mon, 2015-06-01 at 11:57 -0400, Mimi Zohar wrote: > > On Mon, 2015-06-01 at 10:36 -0400, Zbigniew Jędrzejewski-Szmek wrote: > > > --- > > > OK, that's strange. Because the error message comes from copy_bytes() > > > failing, > > > an

Re: [systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

On 06/01/2015 10:11 PM, Ian Pilcher wrote: > Is this going to make nspawn/networkd fundamentally incompatible with > distributions that use iptables-based tools (such as firewalld)? No, nftables and iptables can peacefully coexist. With nftables though, systemd can have a table of its own, and hen

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

2015-06-01 20:12 GMT+02:00 David Herrmann : > Hi > > As of today we've disabled git-push to fd.o. The official development > git repository is now at github [1]. What about the bug tracker? Will it remain at fdo's bugzilla. I have to admit I'm not a huge fan of github's bug tracker. Michael --

[systemd-devel] [PATCH v5 3/3] udev: input_id - use ABS_MT_SLOT{-1} to exclude non touch screen devices

Peek at the ABS_MT_SLOT-1 axis. Expect that touch screens only have axes inside the MT range. --- src/udev/udev-builtin-input_id.c | 4 1 file changed, 4 insertions(+) diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin-input_id.c index 0f9f021..7fa7d1a 100644 --- a/src/ude

[systemd-devel] Starting up service after my openvpn connection turns up

I am trying to start a dropbear service after my openvpn service starts up. --- [Unit] Description=SSH Per-Connection Server Wants=dropbearkey.service After=syslog.target dropbearkey.service Wants=openvpn@equipment.service After=openvpn@equipment.service ---

[systemd-devel] [PATCH v4 3/3] udev: input_id - use ABS_MT_SLOT{-1} to exclude non touch screen devices

Peek at the ABS_MT_SLOT-1 axis. Expect that touch screens only have axes inside the MT range. --- src/udev/udev-builtin-input_id.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin-input_id.c index 0f9f021..59616c8 100644

Re: [systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

Is this going to make nspawn/networkd fundamentally incompatible with distributions that use iptables-based tools (such as firewalld)? -- Ian Pilcher arequip...@gmail.com "I g

Re: [systemd-devel] [PATCH] mount-setup: create /run/systemd/netif/links/ before accessing

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel

Re: [systemd-devel] [ANNOUNCE] Separating gudev from systemd

On Tue, May 19, 2015, at 11:06 AM, David Herrmann wrote: > Hi > > We're about to remove gudev from the systemd repository, as it is in > no way related to the systemd code-base, nor used by the systemd > project. To preserve backwards compatibility, gudev was extracted into > a separate repository

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

On Mon, Jun 1, 2015 at 11:20 AM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Mon, Jun 01, 2015 at 08:12:37PM +0200, David Herrmann wrote: > > [1] https://github.com/systemd-devs/systemd > Is there a particular reason not to use the existing > https://github.com/systemd/systemd ? >

[systemd-devel] [PATCH] mount-setup: create /run/systemd/netif/links/ before accessing

systemd-timesyncd breaks with Starting Network Time Synchronization... [FAILED] Failed to start Network Time Synchronization. when we have timesyncd activated and systemd-networkd not. Create directory before using it. --- src/core/mount-setup.c | 2 ++ 1 file changed, 2 insertions(+) diff

Re: [systemd-devel] Revert commit "ma-setup: simplify"

On Mon, 2015-06-01 at 10:05 -0400, Mimi Zohar wrote: > On Mon, 2015-06-01 at 14:02 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, Jun 01, 2015 at 08:57:57AM -0400, Mimi Zohar wrote: > > > The original systemd IMA module loaded the IMA policy by mmaping the > > > file into memory and then wri

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

On Mon, Jun 1, 2015 at 8:12 PM, David Herrmann wrote: > Hi > > As of today we've disabled git-push to fd.o. The official development > git repository is now at github [1]. The old repository will still be > back-synced, but we had to disable push-access to avoid getting > out-of-sync with github.

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

Nice! On Mon, Jun 1, 2015 at 2:20 PM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Mon, Jun 01, 2015 at 08:12:37PM +0200, David Herrmann wrote: > > [1] https://github.com/systemd-devs/systemd > Is there a particular reason not to use the existing > https://github.com/systemd/syste

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

On Mon, Jun 01, 2015 at 08:12:37PM +0200, David Herrmann wrote: > [1] https://github.com/systemd-devs/systemd Is there a particular reason not to use the existing https://github.com/systemd/systemd ? Zbyszek ___ systemd-devel mailing list systemd-devel@

[systemd-devel] [ANNOUNCE] Git development moved to github

Hi As of today we've disabled git-push to fd.o. The official development git repository is now at github [1]. The old repository will still be back-synced, but we had to disable push-access to avoid getting out-of-sync with github. In recent months, keeping up with the mailing-list has become mor

Re: [systemd-devel] How many times is the root mounted in boot up?

On Mon, Jun 1, 2015 at 5:56 PM, cee1 wrote: > Hi all, > > In case of no initrd and mounting the root by specifying > "root=/dev/sdaN" in kernel command line, how many time is the root > mounted in systemd? > It's only mounted once, by the kernel. systemd won't mount it again, it doesn't need to.

Re: [systemd-devel] [ANNOUNCE] Separating gudev from systemd

Hi On Mon, Jun 1, 2015 at 6:51 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Jun 01, 2015 at 05:48:15PM +0100, Bastien Nocera wrote: >> On Sun, 2015-05-31 at 02:24 +, Zbigniew Jędrzejewski-Szmek wrote: >> > Hi Bastien, >> > >> > do you have any plans for the package in Fedora? >> >> I don'

Re: [systemd-devel] [ANNOUNCE] Separating gudev from systemd

On Mon, 2015-06-01 at 16:51 +, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Jun 01, 2015 at 05:48:15PM +0100, Bastien Nocera wrote: > > On Sun, 2015-05-31 at 02:24 +, Zbigniew Jędrzejewski-Szmek > > wrote: > > > On Wed, May 27, 2015 at 11:21:06AM +0200, Bastien Nocera wrote: > > > > On Wed

Re: [systemd-devel] [ANNOUNCE] Separating gudev from systemd

On Mon, Jun 01, 2015 at 05:48:15PM +0100, Bastien Nocera wrote: > On Sun, 2015-05-31 at 02:24 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Wed, May 27, 2015 at 11:21:06AM +0200, Bastien Nocera wrote: > > > On Wed, 2015-05-20 at 12:01 +0200, David Herrmann wrote: > > > > Hi > > > > > > > > On W

Re: [systemd-devel] [ANNOUNCE] Separating gudev from systemd

On Sun, 2015-05-31 at 02:24 +, Zbigniew Jędrzejewski-Szmek wrote: > On Wed, May 27, 2015 at 11:21:06AM +0200, Bastien Nocera wrote: > > On Wed, 2015-05-20 at 12:01 +0200, David Herrmann wrote: > > > Hi > > > > > > On Wed, May 20, 2015 at 8:46 AM, Tom Gundersen > > > wrote: > > > > On Wed, Ma

Re: [systemd-devel] [PATCH] Partially revert "ma-setup: simplify"

On Mon, 2015-06-01 at 11:57 -0400, Mimi Zohar wrote: > On Mon, 2015-06-01 at 10:36 -0400, Zbigniew Jędrzejewski-Szmek wrote: > > --- > > OK, that's strange. Because the error message comes from copy_bytes() > > failing, > > and in copy_bytes() EINVAL could only originate in loop_write(), unless >

Re: [systemd-devel] [PATCH] Partially revert "ma-setup: simplify"

On Mon, 2015-06-01 at 10:36 -0400, Zbigniew Jędrzejewski-Szmek wrote: > --- > OK, that's strange. Because the error message comes from copy_bytes() failing, > and in copy_bytes() EINVAL could only originate in loop_write(), unless > I'm missing something. Can you check the following patch, which es

Re: [systemd-devel] [PATCHi V4] cryptsetup: craft a unique ID with the source device

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing

Re: [systemd-devel] [PATCH 7/7] journal: Try getting journal fd from machined

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel ma

[systemd-devel] [PATCH 2/7] nspawn: Close unneeded sockets in outer child

--- src/nspawn/nspawn.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c index bd7532c..28b79c4 100644 --- a/src/nspawn/nspawn.c +++ b/src/nspawn/nspawn.c @@ -4348,6 +4348,8 @@ static int outer_child( } pid_socket = safe_close(pid_

[systemd-devel] [PATCH 4/7] machined: Add getter for machine's journal directory descriptor

Sometimes machine's journal is not accessible by path, so we can ask machined to provide a descriptor to it. --- src/machine/machined-dbus.c| 112 + src/machine/org.freedesktop.machine1.policy.in | 10 +++ 2 files changed, 122 insertions(+) diff --git

[systemd-devel] [PATCH 6/7] journal: Open JournalFile by dirfd and filename instead of path

That way we can have access to a file that is not accessible by path, for example to a file in overlayfs in different mount namespace (which is the case for rkt pods). --- src/journal-remote/journal-remote-write.c | 12 +- src/journal-remote/journal-remote.c | 34 ++-- src/journal/journal-

[systemd-devel] [PATCH 0/7] Make "journalctl -M" work with journals inside overlayfs

Hi, When having a container that keeps its journal inside overlayfs, journalctl from host can't access them anymore. The way to fix, as proposed by Lennart, was basically journalctl to get file descriptor of journal directory from machined and go from there. This situation happens inside rkt conta

[systemd-devel] [PATCH 3/7] nspawn, machined: Fix comments and error messages related to child failures

--- src/machine/machine-dbus.c | 18 +- src/nspawn/nspawn.c| 4 ++-- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/src/machine/machine-dbus.c b/src/machine/machine-dbus.c index 0892479..12f7961 100644 --- a/src/machine/machine-dbus.c +++ b/src/machine/ma

[systemd-devel] [PATCH 5/7] journal: Add JournalDirectory

This ref-counted struct holds a path and a descriptor to a directory. The descriptor should be used for "real" work (openat, renameat and others) and the path should be used for logging/debugging. --- Makefile.am | 2 + src/journal/journal-dir.c | 141 ++

[systemd-devel] [PATCH 7/7] journal: Try getting journal fd from machined

--- Makefile.am | 2 +- src/journal/sd-journal.c | 52 +++- 2 files changed, 52 insertions(+), 2 deletions(-) diff --git a/Makefile.am b/Makefile.am index 32e7ca3..ee9c29b 100644 --- a/Makefile.am +++ b/Makefile.am @@ -4399,8 +4399,8 @@ sy

[systemd-devel] [PATCH 1/7] nspawn, shared: Factor out sending and receiving fd

Right now it can be used to sent rtnl and kmsg descriptors. These functions will be used later to send journal directory descriptor in machined. --- src/nspawn/nspawn.c | 66 +++-- src/shared/util.c | 56

[systemd-devel] [PATCHi V4] cryptsetup: craft a unique ID with the source device

From: Harald Hoyer If cryptsetup is called with a source device as argv[3], then craft the ID for the password agent with a unique device path. If possible "/dev/block/:" is used, otherwise the original argv[3] is used. This enables password agents like petera [1] to provide a password accordin

Re: [systemd-devel] [PATCH] mount: use libmount to monitor mountinfo & utab

Hi Karel, On Mon, Jun 1, 2015 at 2:07 PM, Karel Zak wrote: > The current implementation directly monitor /proc/self/mountinfo and > /run/mount/utab files. It's really not optimal because utab file is > private libmount stuff without any official guaranteed semantic. > > The libmount since v2.26 p

Re: [systemd-devel] [PATCH] Partially revert "ma-setup: simplify"

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing

[systemd-devel] How many times is the root mounted in boot up?

Hi all, In case of no initrd and mounting the root by specifying "root=/dev/sdaN" in kernel command line, how many time is the root mounted in systemd? I find: 1. systemd will generate a "-.mount" unit from /proc/self/mountsinfo 2. systemd will generate a "-.mount" unit by systemd-fstab-generator

Re: [systemd-devel] systemctl disable not working as expected

Hi Lennart Thanks a lot for the reply. I believe it is off-topic here and I should rather post on the pulseaudio mailing list but please answer the below and I will come over to the pulse mailing list if need be. I have autospawn = no and daemon-binary = /bin/true in my client.conf but I still

[systemd-devel] [PATCH] Partially revert "ma-setup: simplify"

--- OK, that's strange. Because the error message comes from copy_bytes() failing, and in copy_bytes() EINVAL could only originate in loop_write(), unless I'm missing something. Can you check the following patch, which essentially reverts to the old copy method? Zbyszek src/core/ima-setup.c | 17

Re: [systemd-devel] Revert commit "ma-setup: simplify"

On Mon, 2015-06-01 at 10:05 -0400, Mimi Zohar wrote: > On Mon, 2015-06-01 at 14:02 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, Jun 01, 2015 at 08:57:57AM -0400, Mimi Zohar wrote: > > > The original systemd IMA module loaded the IMA policy by mmaping the > > > file into memory and then wri

Re: [systemd-devel] Revert commit "ma-setup: simplify"

On Mon, 2015-06-01 at 14:02 +, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Jun 01, 2015 at 08:57:57AM -0400, Mimi Zohar wrote: > > The original systemd IMA module loaded the IMA policy by mmaping the > > file into memory and then writing the entire file to > > /ima/policy. By changing this be

Re: [systemd-devel] Revert commit "ma-setup: simplify"

On Mon, Jun 01, 2015 at 08:57:57AM -0400, Mimi Zohar wrote: > The original systemd IMA module loaded the IMA policy by mmaping the > file into memory and then writing the entire file to > /ima/policy. By changing this behavior of writing the > entire file, commit 4dfb18922d5d "ima-setup: simplify

Re: [systemd-devel] [PATCH] shared: Drop 'name=' prefix from SYSTEMD_CGROUP_CONTROLLER define.

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-deve

Re: [systemd-devel] [PATCH] mount: use libmount to monitor mountinfo & utab

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing l

[systemd-devel] Revert commit "ma-setup: simplify"

The original systemd IMA module loaded the IMA policy by mmaping the file into memory and then writing the entire file to /ima/policy. By changing this behavior of writing the entire file, commit 4dfb18922d5d "ima-setup: simplify" broke IMA policy loading. Please revert commit 4dfb18922d5d1efb1

[systemd-devel] [PATCH] shared: Drop 'name=' prefix from SYSTEMD_CGROUP_CONTROLLER define.

In cgtop,mount-setup,nspawn the name= prefix is hard-coded in the mount options, and the define is not used. Everywhere else, we explicitly white-list allow 'name=' prefix to be used with all controllers, and strip it out to 'normalise' the controller name. That work is mostly inflicted on us due

[systemd-devel] [PATCH] mount: use libmount to monitor mountinfo & utab

The current implementation directly monitor /proc/self/mountinfo and /run/mount/utab files. It's really not optimal because utab file is private libmount stuff without any official guaranteed semantic. The libmount since v2.26 provides API to monitor mount kernel & userspace changes. This patch re

Re: [systemd-devel] Cleaning up transient scopes

On tis, 2015-05-19 at 19:00 +0200, Lennart Poettering wrote: > On Thu, 05.03.15 10:12, Alexander Larsson (al...@redhat.com) wrote: > > > See, even when the sleep command died the scope still exists, and is > > even ACTIVE. > > This appears to work fine here on git. There were some fixes to > syst

Re: [systemd-devel] sd-device: fix invalid property strv pointers

Hey Tom, Tom Gundersen [2015-06-01 11:52 +0200]: > Thanks for figuring this out Martin. The patch looks good to me, > though maybe we should use NULSTR_FOREACH for the second loop? Thanks for pointing out, these little utilities haven't made it yet into my finger memory.. Applied with this chang

Re: [systemd-devel] sd-device: fix invalid property strv pointers

On Mon, Jun 1, 2015 at 11:39 AM, Martin Pitt wrote: > With our 220 package I still get a broken environment in udev > callouts, even with Tom's recent fix 0e3e605 applied. > > Curiously it works for devices like "lo" which don't have a lot of > properties, but for "real" wlan devices I get invalid

Re: [systemd-devel] bcache broke in udev 220

Hey David, David Mohr [2015-05-31 15:57 -0600]: > udev 220 arrived in Debian sid and this update broke bcache support [1]: no > /dev/disk/by-uuid/ symlink is being created for the filesystem on top of > /dev/bcache*. That's because 60-persistent-storage now uses a whitelist > instead of blacklist.

[systemd-devel] sd-device: fix invalid property strv pointers

Hello all, With our 220 package I still get a broken environment in udev callouts, even with Tom's recent fix 0e3e605 applied. Curiously it works for devices like "lo" which don't have a lot of properties, but for "real" wlan devices I get invalid environment variables. With some debugging applie

Re: [systemd-devel] [PATCH v2] cgroup-util: fix is_valid check to pass for unified cgroup hierchy.

On 1 June 2015 at 09:03, Umut Tezduyar Lindskog wrote: > On Fri, May 29, 2015 at 12:25 PM, Lennart Poettering > wrote: >> On Fri, 29.05.15 00:24, Dimitri John Ledkov (dimitri.j.led...@intel.com) >> wrote: >> >>> On 28 May 2015 at 18:08, Lennart Poettering wrote: >>> > On Thu, 28.05.15 16:42, Di

Re: [systemd-devel] [PATCH v2] cgroup-util: fix is_valid check to pass for unified cgroup hierchy.

On Fri, May 29, 2015 at 12:25 PM, Lennart Poettering wrote: > On Fri, 29.05.15 00:24, Dimitri John Ledkov (dimitri.j.led...@intel.com) > wrote: > >> On 28 May 2015 at 18:08, Lennart Poettering wrote: >> > On Thu, 28.05.15 16:42, Dimitri John Ledkov (dimitri.j.led...@intel.com) >> > wrote: >> >