Re: [systemd-devel] Is systemd-cryptsetup binary internal?

On Mon, 18 Sept 2023, 17:43 Nils Kattenbeck, wrote: > > Why was the decision taken to put these into /usr/lib/systemd instead of >> > /usr/libexec/systemd/? >> >> That's a Fedoraism. Why would one put something there? >> >> /usr/lib/ is where private arch-dependent package stuff goes. What's >>

Re: [systemd-devel] [PATCH 0/1] x86/kexec: UKI support

On Tue, 12 Sept 2023 at 11:38, Jarkko Sakkinen wrote: > > On Tue Sep 12, 2023 at 2:20 AM EEST, Neal Gompa wrote: > On Mon, Sep 11, 2023 > at 7:15 PM Jarkko Sakkinen wrote: > > > On Sat Sep 9, 2023 at 7:18 PM EEST, Jan Hendrik Farr wrote: > > > > Hello, > > > > > > > > this patch implements UKI

Re: [systemd-devel] Feedback sought: can we drop cgroupv1 support soon?

On Mon, 7 Aug 2023 at 17:26, Lennart Poettering wrote: > > On Do, 20.07.23 01:59, Dimitri John Ledkov (dimitri.led...@canonical.com) > wrote: > > > Some deployments that switch back their modern v2 host to hybrid or v1, are > > the ones that need to run old workloads

Re: [systemd-devel] Feedback sought: can we drop cgroupv1 support soon?

Some deployments that switch back their modern v2 host to hybrid or v1, are the ones that need to run old workloads that contain old systemd. Said old systemd only has experimental incomplete v2 support that doesn't work with v2-only (the one before current stable magick mount value).

Re: [systemd-devel] Support for unmerged-usr systems will be REMOVED in the second half of 2023

Hi, On Tue, 13 Jun 2023 at 16:01, Richard Purdie wrote: > > On Tue, 2023-06-13 at 15:56 +0100, Dimitri John Ledkov wrote: > > Nobody is retroactively changing existing systemd releases. > > > > Stay on a previously released systemd version which will continue to > >

Re: [systemd-devel] Support for unmerged-usr systems will be REMOVED in the second half of 2023

Nobody is retroactively changing existing systemd releases. Stay on a previously released systemd version which will continue to have features it used to have. On Tue, 13 Jun 2023, 15:53 Richard Purdie, < richard.pur...@linuxfoundation.org> wrote: > On Tue, 2023-06-13 at 15:31 +0100, Luca

Re: [systemd-devel] [RFC] Switching to OpenSSL 3?

On Tue, Nov 23, 2021 at 12:09 PM Lennart Poettering wrote: > > On Di, 23.11.21 11:53, Dimitri John Ledkov (dimitri.led...@canonical.com) > wrote: > > > Just an update from Ubuntu - for the upcoming release of Jammy (22.04 > > LTS targeting release in April 2022) we

Re: [systemd-devel] [RFC] Switching to OpenSSL 3?

Just an update from Ubuntu - for the upcoming release of Jammy (22.04 LTS targeting release in April 2022) we have started transition to OpenSSL 3 and currently upgrading to systemd v249. W.r.t. library choice usually GnuTLS APIs are nicer to use; however OpenSSL library tends to be the more

Re: [systemd-devel] Suppressing spam error messages in the system journal

I agree that i should have had much lower log level. This is now fixed properly upstream via https://github.com/systemd/systemd/pull/18638/files I will try to backport that to stable series or at least drop the log level to debug. On Mon, 19 Oct 2020 at 15:05, Michael Biebl wrote: > > Am Mo.,

Re: [systemd-devel] howto switch from grub2-bios to systemd-boot

On Mon, 22 Jun 2020 at 18:03, Reindl Harald wrote: > > > > Am 22.06.20 um 17:21 schrieb Mantas Mikulėnas: > > On Mon, Jun 22, 2020 at 5:01 PM Reindl Harald > > wrote: > > > > what is the best way to get a Fedora using legacy-boot to UEFI and at > > the same

Re: [systemd-devel] What is the point of making timesyncd bus-activatible?

On Tue, 19 May 2020 at 10:31, Arian Van Putten wrote: > > Hey list, > > systemd-timesyncd has an Alias=dbus-org.freedesktop.timesync1.service and an > accompanying dbus service file too. > > It is started in early boot; `Before=sysinit.target` so why would making it > dubs-activatible ever

[systemd-devel] initrd.target indirection no longer available

Hi, In v245 systemd started to default to `initrd.target`, instead of `default.target` in the initrd. However, unlike `default.target` in the running system, `initrd.target` is not an indirection symlink. Specifically, default.target is a symlink to like graphical.target or like

Re: [systemd-devel] Read-only /etc, machine-id with an overlay - journald failing

On Wed, 26 Feb 2020 at 09:59, Andreas Kempe wrote: > > Hello everyone, > > I'm working in a project with an embedded Linux system based on > Openembedded using Systemd version 241 as our init process. We're > using a read-only /etc. To facilitate development, we want to use a > writeable overlay

[systemd-devel] How does systemd (pid1) connect to system DBus?

I see that systemd pid1 manager is available on the system DBus. But when/how does it connect to it? I'm failing to trace it in both systemd & dbus code. I assume that systemd starts, eventually starts dbus.socket/service, dbus starts, and then something causes systemd to connect to the system

Re: [systemd-devel] RFC: luksSuspend support in sleep/sleep.c

On Thu, 10 Oct 2019 at 16:49, Mantas Mikulėnas wrote: > > On Thu, Oct 10, 2019 at 6:23 PM Jonas Meurer wrote: >> >> Hi Lennart, hi Tim, >> >> thanks a lot for your feedback, Lennart. It's much appreciated! >> >> Tim Dittler: >> > On 09.10.19 19:26, Lennart Poettering wrote: >> >> On Mi, 09.10.19

[systemd-devel] /cdrom mounted from initrd is stopped on boot, possibly confused about device-bound

Ubuntu installer images use initrd, which has udevd but no systemd. It mounts /dev/sr0 as /root/cdrom, then pivots to /root, meaning /root/cdrom becomes just /cdrom and exec systemd as pid 1. At this point cdrom.mount is stopped as it's bound to an inactive dev-sr0.device. Then sometime later

Re: [systemd-devel] On every 'sysctl enable/disable' Systemd Reload is happening

On Mon, 25 Feb 2019 at 19:05, Mahesh Mylarappa wrote: > > Hi, > > I am working on Linux host which has old 219 systemd build. We are trying to > create/enable/start multiple service instances at same time. Basically we > create 15 to 20 unit files in /etc/systemd/system directory and call >

Re: [systemd-devel] GithHub / private repos

On Sat, 26 Jan 2019 at 12:43, Lennart Poettering wrote: > > On Di, 15.01.19 21:21, Alex Dzyoba (a...@dzyoba.com) wrote: > > > When you create a new organization you can choose "Team For Open > > Source" plan. Here is the link > > https://github.com/account/organizations/new > > > > Though, I

Re: [systemd-devel] How to set `InitRDTimestampMonotonic` from console?

Hi, On 4 July 2018 at 10:22, Lennart Poettering wrote: > On Mi, 04.07.18 07:24, Paul Menzel (pmenzel+systemd-de...@molgen.mpg.de) > wrote: > >> Dear systemd folks, >> >> >> Debian uses a shell script as `/init` in initrd, and I like to extend that, >> to set the time stamps for the initrd

Re: [systemd-devel] Changed ordering of systemd-resolved.service

On 16 April 2018 at 18:20, Paul Menzel <pmenzel+systemd-de...@molgen.mpg.de> wrote: > Dear Dimitri, > > > On 04/16/18 18:51, Dimitri John Ledkov wrote: > >> On 16 April 2018 at 14:25, Paul Menzel wrote: > > >>> On 04/16/18 12:47, Dimitri John Ledkov wrote

Re: [systemd-devel] Changed ordering of systemd-resolved.service

On 16 April 2018 at 14:25, Paul Menzel <pmenzel+systemd-de...@molgen.mpg.de> wrote: > Dear Dimitri, > > > Thank you for your quick response. > > > On 04/16/18 12:47, Dimitri John Ledkov wrote: >> >> On 13 April 2018 at 16:40, Paul Menzel wrote: > >

Re: [systemd-devel] Changed ordering of systemd-resolved.service

On 13 April 2018 at 16:40, Paul Menzel wrote: > Dear Dimitri, dear systemd folks, > > > In commit 1f158013 (resolved.service: set DefaultDependencies=no) the > ordering of systemd-resolved.service was changed. (How do I find the merge > request to find

[systemd-devel] systemd-networkd-wait-online should know if there is anything to wait for

Hello, When systemd-networkd-wait-online was originally introduced, it was the only tool that correctly waited and blocked the boot, until after networking is configured. These days, however, all/most network configurations tools ship appropriate wait-online integration. E.g. there is

[systemd-devel] networkd dhcp client - serialize / run stand alone / inject or restart dhcp client

I have a request to start/stop/restart the dhcp lease client, and/or run networkd dhcp client stand alone, or somehow serialize dhcpclient lease and inject that for networkd-dhcp to pick that up and restart. For example, Ubuntu initramfs currently does not have networkd in it, but it can bring

Re: [systemd-devel] Keeping track of usage time

On 3 November 2015 at 06:27, Umut Tezduyar Lindskog wrote: > journalctl --list-boots seems great actually but wouldn't work for us. > We cannot keep lots of logs in our products. > You shouldn't need to keep lots of logs, just a timer unit that would query and store/transmit

Re: [systemd-devel] Keeping track of usage time

On 2 November 2015 at 14:46, Umut Tezduyar Lindskog wrote: > Hi, > > We would like to implement a feature to keep track of accumulated > values of uptimes in our products. Tracked time will give us the total > usage time of our product not just since last reboot (/proc/uptime).

Re: [systemd-devel] kernel and systemd boot sequence

Systemd is the init. /etc/fstab is optional. initramfs could be running systemd (e.g. dracut supports it), thus systemd would be beofre switch_root. However initramfs & switch_root are optional as well. Hence the bootflow on a modern linux distribution like Clear Linux is: kernel -> systemd

Re: [systemd-devel] startxfce4 vs logind

On 19 September 2015 at 23:05, Dimitri John Ledkov <dimitri.j.led...@intel.com> wrote: > Heya, > > I boot to tty1, and login as my normal user account. > > Session c1, is active and has type tty. And I can access devices which > are marked as uaccess. > > Then I d

[systemd-devel] startxfce4 vs logind

Heya, I boot to tty1, and login as my normal user account. Session c1, is active and has type tty. And I can access devices which are marked as uaccess. Then I do $ startxfce4 -> which starts graphical interface. However, at that time I "loose" the logind session. No new sessions are started,

Re: [systemd-devel] What I think is really wrong with systemd

On 16 September 2015 at 16:52, Kok, Auke-jan H wrote: > On Wed, Sep 16, 2015 at 8:38 AM, Reindl Harald wrote: >> Am 16.09.2015 um 17:13 schrieb Ahmed S. Darwish: >>> >>> Not to mention that the same rolling-release model was adopted by >>> the

Re: [systemd-devel] optional kdbus enablement

oh, it is. Excellent. Not sure how I missed that last time I was testing, never mind me. On 10 September 2015 at 16:53, Dimitri John Ledkov <dimitri.j.led...@intel.com> wrote: > Shouldn't the dbus1-generator disable the dbus.service & dbus.socket > by symlinking t

Re: [systemd-devel] bootctl: default mount point for the ESP partition.

On 1 September 2015 at 17:47, Simon McVittie wrote: > On 01/09/15 17:21, Goffredo Baroncelli wrote: >> I discovered that bootctl assume as default mount point for the ESP >> partition the /boot directory. Instead it seems to me that the most part >> of

Re: [systemd-devel] Looking for experiences formalizing an API for journal messages

On 29 July 2015 at 20:02, Anne Mulhern amulh...@redhat.com wrote: - Original Message - From: Lennart Poettering lenn...@poettering.net To: Anne Mulhern amulh...@redhat.com Cc: systemd-devel@lists.freedesktop.org Sent: Thursday, July 23, 2015 9:21:44 AM Subject: Re:

Re: [systemd-devel] socket activated services and correct dependency mapping

On 24 July 2015 at 10:38, James Hogarth james.hoga...@gmail.com wrote: I want a user to be able to systemctl start sslh and use listening addresses in /etc/sslh.cfg as always (so I'm reluctant to put a straight Sockets= in the service unit file) but as it stands the lazy You can write a

Re: [systemd-devel] How to properly write an umbrella unit

Heya, On 21 July 2015 at 12:43, Marc Haber mh+systemd-de...@zugschlus.de wrote: Hi, I am trying to systemd'ize a daemon which is useful to be run in two instances. It is usually the case that both instances need to be started and stopped simultaneously, and the local admin would want a

Re: [systemd-devel] systemd-tmpfiles for the user instance of systemd

Heya, On 1 July 2015 at 11:35, Daniel Tihelka dtihe...@gmail.com wrote: Hello, does anyone have an experience with the use of systemd-tmpfiles for the user instance of systemd. My question would be - what sort of files are you creating with tmpfiles? system stuff is known to use dynamic

Re: [systemd-devel] no tar balls at release time

On 23 June 2015 at 00:21, Kay Sievers k...@vrfy.org wrote: We currently considering to stop creating release tar balls. For build systems which still require them, they can be created locally from the upstream git repository with: git archive --format=tar --prefix=systemd-$(VERSION)/

[systemd-devel] networkd bridge masquerading

I'm trying to setup networking for containers/vms similar to e.g. docker0 bridge, or lxcbr0. But purely with networkd. That is a bridge that is NATed to provide internet access, and then attaching tap/veth devices to the bridge. I did this at first: br0.netdev: [NetDev] Name=br0 Kind=bridge

Re: [systemd-devel] [PATCH v2] Add support for transient presets, applied on every boot.

On 22 April 2015 at 19:30, Lennart Poettering lenn...@poettering.net wrote: On Sat, 21.02.15 02:38, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Sorry for the late review! Hello, blast from the past =) Can you please add a commit description to this, explaining the precise

Re: [systemd-devel] nss-myhostname: why don't loopback interfaces appear?

On 3 June 2015 at 06:40, Daurnimator q...@daurnimator.com wrote: I was playing around with nss, and found that my loopback interface ip doesn't appear from nss-myhostname. Rather, my other ones do. Furthermore, unless I request IPv4, link-local IPv6 addresses are returned. Is this expected?

Re: [systemd-devel] FR: different gcrypt options for joornald and importd

On 8 June 2015 at 16:12, Lennart Poettering lenn...@poettering.net wrote: On Mon, 08.06.15 16:12, Alexey Shabalin (a.shaba...@gmail.com) wrote: Hi! I want build journald without gcrypt support. But --disable-gcrypt disabled build importd. Can you add diiferent options for journald and

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

On 1 June 2015 at 19:12, David Herrmann dh.herrm...@gmail.com 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

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

On 2 June 2015 at 12:34, Jóhann B. Guðmundsson johan...@gmail.com wrote: On 06/02/2015 11:06 AM, David Herrmann wrote: Regarding the final github address: David Strauss kindly offered the 'systemd' user to us. Hence, we hope to move the repository to github.com/systemd/systemd this week.

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

On 2 June 2015 at 15:34, Martin Pitt martin.p...@ubuntu.com wrote: David Herrmann [2015-06-02 13:06 +0200]: Our preferred way to send future patches is the github way. This means sending pull-requests to the github repo. Furthermore, all feature patches should go through pull-requests and

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

On 2 June 2015 at 15:56, Daniel P. Berrange berra...@redhat.com wrote: On Tue, Jun 02, 2015 at 04:34:03PM +0200, Martin Pitt wrote: David Herrmann [2015-06-02 13:06 +0200]: Our preferred way to send future patches is the github way. This means sending pull-requests to the github repo.

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

On 2 June 2015 at 15:49, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Tue, Jun 02, 2015 at 04:34:03PM +0200, Martin Pitt wrote: David Herrmann [2015-06-02 13:06 +0200]: Our preferred way to send future patches is the github way. This means sending pull-requests to the github repo.

[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

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 u...@tezduyar.com wrote: On Fri, May 29, 2015 at 12:25 PM, Lennart Poettering lenn...@poettering.net 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 lenn

Re: [systemd-devel] systemctl as non-root

On 29 May 2015 at 01:21, aaron_wri...@selinc.com wrote: Brandon Philips bran...@ifup.co wrote on 05/28/2015 05:10:33 PM: Access to the system dbus is controlled by dbus policies. You will need to write a policy for giving this user access to the systemd1 object. I compiled systemd without

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

On 29 May 2015 at 11:25, Lennart Poettering lenn...@poettering.net 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 lenn...@poettering.net wrote: On Thu, 28.05.15 16:42, Dimitri John Ledkov (dimitri.j.led

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

On 29 May 2015 at 14:41, Lennart Poettering lenn...@poettering.net wrote: On Fri, 29.05.15 12:42, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: On 29 May 2015 at 11:25, Lennart Poettering lenn...@poettering.net wrote: On Fri, 29.05.15 00:24, Dimitri John Ledkov (dimitri.j.led

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

On 29 May 2015 at 11:17, har...@redhat.com wrote: From: Harald Hoyer har...@redhat.com If cryptsetup is called with a source device as argv[3], then craft the ID for the password agent with a unique device path. I'm not sure why this is needed... if the device path is not good enough, there

[systemd-devel] [PATCH v2 5/5] core/cgroup: Add cgroup.populated inotify watches, when available.

--- src/core/cgroup.c| 81 ++-- src/core/manager.c | 7 - src/core/manager.h | 3 ++ src/core/service.c | 2 +- src/shared/cgroup-util.c | 28 + src/shared/cgroup-util.h | 6 ++-- src/test/test-cgroup.c

[systemd-devel] [PATCH v2 4/5] unified-cgroup: fix cg_pid_get_path() and cg_get_path().

--- src/shared/cgroup-util.c| 8 src/test/test-cgroup-util.c | 18 ++ 2 files changed, 26 insertions(+) diff --git a/src/shared/cgroup-util.c b/src/shared/cgroup-util.c index 2bca32a..eae9f5d 100644 --- a/src/shared/cgroup-util.c +++ b/src/shared/cgroup-util.c @@

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

It appears in /proc/self/cgroup as `0::/' --- src/shared/cgroup-util.c| 4 src/test/test-cgroup-util.c | 3 ++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/src/shared/cgroup-util.c b/src/shared/cgroup-util.c index 9988e5c..2bca32a 100644 --- a/src/shared/cgroup-util.c

[systemd-devel] [PATCH v2 2/5] configure.ac: add option for experimental unified cgroup handling.

--- configure.ac | 11 +++ 1 file changed, 11 insertions(+) diff --git a/configure.ac b/configure.ac index 92654a6..232d419 100644 --- a/configure.ac +++ b/configure.ac @@ -1325,6 +1325,16 @@ AC_ARG_ENABLE(ldconfig, AM_CONDITIONAL(ENABLE_LDCONFIG, [test x$enable_ldconfig = xyes]) #

[systemd-devel] [PATCH v2 0/5] resent

... sigh looks like I had duplicate patches generated in my tree. this is a clean resent. Dimitri John Ledkov (5): cgroup-util: fix is_valid check to pass for unified cgroup hierchy. configure.ac: add option for experimental unified cgroup handling. core/mount-setup: Mount unified hierchy

[systemd-devel] [PATCH v2 3/5] core/mount-setup: Mount unified hierchy, instead of name=systemd, when compiled to do so.

--- src/core/mount-setup.c | 5 + src/shared/def.h | 4 2 files changed, 9 insertions(+) diff --git a/src/core/mount-setup.c b/src/core/mount-setup.c index c35248e..3112e00 100644 --- a/src/core/mount-setup.c +++ b/src/core/mount-setup.c @@ -94,10 +94,15 @@ static const MountPoint

[systemd-devel] [PATCH 3/5] core/mount-setup: Mount unified hierchy, instead of name=systemd, when compiled to do so.

--- src/core/mount-setup.c | 5 + src/shared/def.h | 4 2 files changed, 9 insertions(+) diff --git a/src/core/mount-setup.c b/src/core/mount-setup.c index c35248e..3112e00 100644 --- a/src/core/mount-setup.c +++ b/src/core/mount-setup.c @@ -94,10 +94,15 @@ static const MountPoint

[systemd-devel] [PATCH 5/5] Add cgroup.populated inotify watches.

--- src/core/cgroup.c| 81 ++-- src/core/manager.c | 7 - src/core/manager.h | 3 ++ src/core/service.c | 2 +- src/shared/cgroup-util.c | 28 + src/shared/cgroup-util.h | 6 ++-- src/test/test-cgroup.c

[systemd-devel] [PATCH 5/5] core/cgroup: Add cgroup.populated inotify watches, when available.

--- src/core/cgroup.c| 81 ++-- src/core/manager.c | 7 - src/core/manager.h | 3 ++ src/core/service.c | 2 +- src/shared/cgroup-util.c | 28 + src/shared/cgroup-util.h | 6 ++-- src/test/test-cgroup.c

[systemd-devel] [PATCH 2/5] configure.ac: add option for experimental unified cgroup handling.

--- configure.ac | 11 +++ 1 file changed, 11 insertions(+) diff --git a/configure.ac b/configure.ac index 92654a6..232d419 100644 --- a/configure.ac +++ b/configure.ac @@ -1325,6 +1325,16 @@ AC_ARG_ENABLE(ldconfig, AM_CONDITIONAL(ENABLE_LDCONFIG, [test x$enable_ldconfig = xyes]) #

[systemd-devel] [PATCH 4/5] unified-cgroup: fix cg_pid_get_path() and cg_get_path().

--- src/shared/cgroup-util.c| 8 src/test/test-cgroup-util.c | 18 ++ 2 files changed, 26 insertions(+) diff --git a/src/shared/cgroup-util.c b/src/shared/cgroup-util.c index 2bca32a..eae9f5d 100644 --- a/src/shared/cgroup-util.c +++ b/src/shared/cgroup-util.c @@

[systemd-devel] [PATCH 0/5] experimental basic unified cgroups work

they usually are. There are a few minor tweaks that I'm spotting in this integration, that I will follow up on, but for now enjoy, try out, and let me know what you think. Dimitri John Ledkov (5): cgroup-util: fix is_valid check to pass for unified cgroup hierchy. configure.ac: add option

[systemd-devel] [PATCH 1/5] cgroup-util: fix is_valid check to pass for unified cgroup hierchy.

It appears in /proc/self/cgroup as `0::/' --- src/shared/cgroup-util.c| 4 src/test/test-cgroup-util.c | 3 ++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/src/shared/cgroup-util.c b/src/shared/cgroup-util.c index 9988e5c..2bca32a 100644 --- a/src/shared/cgroup-util.c

[systemd-devel] [PATCH 3/5] Mount unified hierchy, instead of name=systemd.

--- src/core/mount-setup.c | 5 + src/shared/def.h | 4 2 files changed, 9 insertions(+) diff --git a/src/core/mount-setup.c b/src/core/mount-setup.c index ba96741..1cf7099 100644 --- a/src/core/mount-setup.c +++ b/src/core/mount-setup.c @@ -94,10 +94,15 @@ static const MountPoint

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

On 28 May 2015 at 18:08, Lennart Poettering lenn...@poettering.net wrote: On Thu, 28.05.15 16:42, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: It appears in /proc/self/cgroup as `0::/' What precisely does this fix? I mean, we need to do some major rework of things before

Re: [systemd-devel] [PATCH 2/2] systemctl: Don't skip native units when enabling/disabling SysV init.d scripts

On 28 May 2015 at 12:31, Lennart Poettering lenn...@poettering.net wrote: On Wed, 27.05.15 15:13, Martin Pitt (martin.p...@ubuntu.com) wrote: Hello, if you have both a systemd unit and a SysV init script with the same name, systemctl {en,dis}able currently diverts to chkconfig and friends

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

It appears in /proc/self/cgroup as `0::/' --- src/shared/cgroup-util.c| 4 src/test/test-cgroup-util.c | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/src/shared/cgroup-util.c b/src/shared/cgroup-util.c index c0b0ca4..eda7523 100644 --- a/src/shared/cgroup-util.c

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

It appears in /proc/self/cgroup as `0::/' --- v2 change: Test for unified cgroup should pass irrespective of whether allow_named is set. src/shared/cgroup-util.c| 4 src/test/test-cgroup-util.c | 3 ++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git

Re: [systemd-devel] [PATCH 2/2] man: use configured path for mount and umount binaries in manpages

On 27 May 2015 at 10:38, Filipe Brandenburger filbran...@google.com wrote: Export the MOUNT_PATH and UMOUNT_PATH variables as XML entities and use them in the systemctl.1 manpage instead of hardcoding the path in /usr/bin. Tested: - Ran ./configure ac_cv_path_MOUNT_PATH=/bin/mount (same for

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On 27 May 2015 at 10:52, Martin Pitt martin.p...@ubuntu.com wrote: Lennart Poettering [2015-05-27 11:42 +0200]: Well, but let's not forget that a major part of the issues popping up actually were committed weeks ago. Actually, no. As I said, on May 11 most everything was working just fine,

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On 26 May 2015 at 15:10, Martin Pitt martin.p...@ubuntu.com wrote: Lennart Poettering [2015-05-26 16:06 +0200]: I think this has been fixed now with Tom's commit ee3c31bf69746c5afc764c3d0337feec1bf25f0e contributed my Marc-Antoine. Confirmed this morning. Sorry, I should have followed up to

Re: [systemd-devel] preset activation on first boot takes too long

On 14 May 2015 at 18:00, Lennart Poettering lenn...@poettering.net wrote: On Thu, 14.05.15 17:13, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Heya, I'm looking at bootcharts and it seems like first boot preset activation takes too much time... So at the moment, we iterate all

[systemd-devel] [PATCH] core: Execute first boot presets in an enable-only preset-mode.

This means any existing enabled units well be preserved and no pre-created symlinks will be removed. This is done on first boot, when the assumption is that /etc is not populated at all (no machine-id setup). For minimal containers that gives a significant first boot speed up, approximately ~20ms

Re: [systemd-devel] [PATCH] .gitignore: add GNU GLOBAL files

Heya, On 15 May 2015 at 16:12, Łukasz Stelmach l.stelm...@samsung.com wrote: --- .gitignore | 4 1 file changed, 4 insertions(+) diff --git a/.gitignore b/.gitignore index f550950..d2f1a1f 100644 --- a/.gitignore +++ b/.gitignore @@ -22,6 +22,10 @@ /*.tar.xz /Makefile /TAGS

Re: [systemd-devel] [PATCH] .gitignore: add GNU GLOBAL files

On 15 May 2015 at 17:19, Łukasz Stelmach l.stelm...@samsung.com wrote: It was 2015-05-15 pią 18:03, when Lennart Poettering wrote: On Fri, 15.05.15 17:39, Łukasz Stelmach (l.stelm...@samsung.com) wrote: It was 2015-05-15 pią 17:25, when Lennart Poettering wrote: On Fri, 15.05.15 17:12,

[systemd-devel] preset activation on first boot takes too long

Heya, I'm looking at bootcharts and it seems like first boot preset activation takes too much time... So at the moment, we iterate all units, then iterate through presets until we find a match and act upon it. However, most distros have disable * as their last setting, or don't use presets at

Re: [systemd-devel] 60-persistent-storage.rules: add NVMe disks and partitions (again)

Hello, On 14 May 2015 at 08:10, Per Bergqvist p...@bst.lu wrote: Hej, There was a request for addition of NVMe disks Feb 10 2014 by Harald Hoyer which was sort of rejected by Kay Sievers by referring to “we should find out what to do for nvme before adding new users of scsi_id”. More

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On 13 May 2015 at 10:15, Karel Zak k...@redhat.com wrote: On Wed, May 13, 2015 at 06:35:58AM +0300, Andrei Borzenkov wrote: В Tue, 12 May 2015 20:37:15 +0200 Karel Zak k...@redhat.com пишет: On Tue, May 12, 2015 at 07:29:33PM +0300, Andrei Borzenkov wrote: В Tue, 12 May 2015 18:04:50

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On 13 May 2015 at 13:33, Lennart Poettering lenn...@poettering.net wrote: On Tue, 12.05.15 19:29, Andrei Borzenkov (arvidj...@gmail.com) wrote: All examples can be configured using drop-ins. Do we really need yet another syntax now? Well, even though units are all-powerful, I still believe

Re: [systemd-devel] dev-root.device is not active, results in an umount spree

Heya, On 13 May 2015 at 12:53, Martin Pitt martin.p...@ubuntu.com wrote: Hey Dimitri, Dimitri John Ledkov [2015-05-13 12:48 +0100]: Yet, dev-root.device is dead: # systemctl status dev-root.device ● dev-root.device Loaded: loaded Active: inactive (dead) This is very bad

[systemd-devel] dev-root.device is not active, results in an umount spree

I am booting without initramfs, using a plan9 filesystem as rootfs in a kvm. Thus my /proc/cmdline has: root=/dev/root rootflags=rw,trans=virtio,version=9p2000.L rootfstype=9p # mount /dev/root on / type 9p (rw,relatime,sync,dirsync,rw,trans=virtio,version=9p2000.L) Yet, dev-root.device is

Re: [systemd-devel] dev-root.device is not active, results in an umount spree

On 13 May 2015 at 13:43, Lennart Poettering lenn...@poettering.net wrote: On Wed, 13.05.15 12:48, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: I am booting without initramfs, using a plan9 filesystem as rootfs in a kvm. Thus my /proc/cmdline has: root=/dev/root rootflags=rw

Re: [systemd-devel] [PATCH] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

On 13 May 2015 at 14:00, Lennart Poettering lenn...@poettering.net wrote: On Mon, 11.05.15 16:58, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Hmm, all the other AM_PATH_PROG variables do not carry a _BIN suffix, should these two? I don't think so. (In general, I am not too big

[systemd-devel] [PATCH v2] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

--- Makefile.am | 2 ++ configure.ac| 3 +++ src/core/execute.h | 2 +- src/core/mount.c| 12 ++-- src/core/mount.h| 4 ++-- src/remount-fs/remount-fs.c | 10 +- 6 files changed, 19 insertions(+), 14 deletions(-)

[systemd-devel] [PATCH] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

--- Makefile.am | 2 ++ configure.ac| 3 +++ src/core/mount.c| 6 +++--- src/remount-fs/remount-fs.c | 10 +- 4 files changed, 13 insertions(+), 8 deletions(-) diff --git a/Makefile.am b/Makefile.am index e4d00a8..0ff11cc 100644 ---

Re: [systemd-devel] systemd-nspawn and IPv6

On 27 April 2015 at 15:01, Lennart Poettering lenn...@poettering.net wrote: On Sun, 26.04.15 16:50, Kai Krakow (hurikha...@gmail.com) wrote: Hello! I've successfully created a Gentoo container on top of a Gentoo host. I can start the container with machinectl. I can also login using SSH. So

Re: [systemd-devel] systemd-nspawn and IPv6

On 27 April 2015 at 15:56, Lennart Poettering lenn...@poettering.net wrote: On Mon, 27.04.15 15:44, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Well, networkd on the host automatically sets up IPv4 masquerading for each container. We simply don't do anything equivalent for IPv6

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

On 24 April 2015 at 10:06, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 21:04, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: On 23 April 2015 at 13:08, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 19:33, Andrei Borzenkov (arvidj

Re: [systemd-devel] Another attempt: Making dependencies properly overridable

On 23 April 2015 at 14:58, Christian Seiler christ...@iwakd.de wrote: On 04/23/2015 08:36 PM, Lennart Poettering wrote: I mean, so far the deps we set are combined from: unit file (1) + dropins(2) + .wants/ +

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

On 23 April 2015 at 13:08, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 19:33, Andrei Borzenkov (arvidj...@gmail.com) wrote: What does this actually do? Is the specified key file read from the specified device? It reads keyfile from filesystem on device

Re: [systemd-devel] Problem with intermediate target

On 18 April 2015 at 09:39, Christoph Pleger christoph.ple...@cs.tu-dortmund.de wrote: Hello, Why does systemd start this service before /var is mounted, though the service should be executed after remote-fs.target, and remote-fs.target comes after local-fs.target? Because remote-fs.target

Re: [systemd-devel] systemd and process migration

Heya, On 20 April 2015 at 06:59, Adrian Reber adr...@lisas.de wrote: Using CRIU I have been migrating processes from one system to another for the last few months (even years). I am now interested in migrating processes under systemd's control. Before starting to look how to make it work I

Re: [systemd-devel] [RFC 0/6] A network proxy management daemon, systemd-proxy-discoveryd

On 11 April 2015 at 13:41, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Fri, Apr 10, 2015 at 03:17:37PM +0300, Tomasz Bursztyka wrote: Hi, As it has been discussed in the systemd hackfest during the Linux Conference Europe, one daemon could centralize the management of all network

Re: [systemd-devel] Question about relationship between systemd v219 and kernel version.

On 6 April 2015 at 01:12, Lennart Poettering lenn...@poettering.net wrote: On Mon, 06.04.15 06:17, 임창근 (ck21...@samsung.com) wrote: Hello EveryOne. I wonder that If I use kernel v3.4 with systemd v219, systemd-run function is work or not. Because My target have kernel v3.4 and systemd

Re: [systemd-devel] recent udev dependency change delays plymouth and udev

On 2 April 2015 at 00:39, Martin Pitt martin.p...@ubuntu.com wrote: Hello all, The recent commit http://cgit.freedesktop.org/systemd/systemd/commit/?id=d99ce933 (which also made it into v219-stable at http://cgit.freedesktop.org/systemd/systemd-stable/commit/?h=v219-stableid=b238b0eaf71)

Re: [systemd-devel] fsckd needs to go

On 3 April 2015 at 05:58, Lennart Poettering lenn...@poettering.net wrote: Heya, so we discussed the whole fsckd situation a bit more here in Berlin, and we came to the conclusion that fsckd really should not exist the way it does in systemd. To start with, the code is really wrong, it

Re: [systemd-devel] [PATCH] systemctl: list-units -r should not fail with older systemd in container

On 1 April 2015 at 13:44, Lukáš Nykrýn lnyk...@redhat.com wrote: Lennart Poettering píše v Út 31. 03. 2015 v 19:28 +0200: On Tue, 31.03.15 16:10, Lukas Nykryn (lnyk...@redhat.com) wrote: Older version of systemd does not have d-bus method ListUnitsFiltered, so systemctl -r will fail just

Re: [systemd-devel] Drop systemd-ui

On 31 March 2015 at 15:08, Shawn Landden shawnland...@gmail.com wrote: On Tue, Mar 31, 2015 at 12:31 AM, Jóhann B. Guðmundsson johan...@gmail.com wrote: On 03/31/2015 02:30 AM, Shawn Landden wrote: On Mon, Mar 30, 2015 at 4:02 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote: On

  1   2   >