Re: [systemd-devel] Unit File: Create Folder With User Permissions

Hi Austin, this does sound like a use-case for RuntimeDirectory=. See http://www.freedesktop.org/software/systemd/man/systemd.exec.html for details. That is simpler and makes sure the directory is created/cleaned up as needed by systemd as the job is started/stopped. That is available since

[systemd-devel] So how am I supposed to put together my Linux system?

Hi I have read http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html with interest and since I am using a home-grown image based installation scheme anyway, I would like to try and move that closer to the proposal from the systemd cabal. It is pretty easy to create the

Re: [systemd-devel] So how am I supposed to put together my Linux system?

Hi Lennart, thanks for taking the time to reply! On Fri, Sep 5, 2014 at 6:58 PM, Lennart Poettering lenn...@poettering.net wrote: Yeah, we want to encourage distros to install kernels into /usr, somewhere next to where the kmods already are, and then copy that over where necessary into the

[systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

From f3a193de94959875cd1d83f941ed8fc8275c82eb Mon Sep 17 00:00:00 2001 From: Tobias Hunger tobias.hun...@digia.com Date: Wed, 24 Sep 2014 21:57:00 +0200 Subject: [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags= on kernel command line This allows to configure boot loader entries

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

Ping? This is really useful to test out the changes proposed in http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html Yes, Lennart seems to want to move to something more strict that can also work with the uefi secure boot, but this helps me get a test system of the ground

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

Any feedback at all? Please? Am I doing something wrong in posting my patch here? Best Regards, Tobias On Sat, Sep 27, 2014 at 5:59 PM, Tobias Hunger tobias.hun...@gmail.com wrote: Ping? This is really useful to test out the changes proposed in http://0pointer.net/blog/revisiting-how-we-put

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

to patch submission processes nowadays:-) Best Regards, Tobias On Wed, Oct 1, 2014 at 12:26 PM, Colin Guthrie gm...@colin.guthr.ie wrote: Ronny Chevalier wrote on 30/09/14 20:28: Hi, 2014-09-30 21:18 GMT+02:00 Tobias Hunger tobias.hun...@gmail.com: Any feedback at all? Please? Am I doing

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

On Thu, Oct 2, 2014 at 3:15 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 24.09.14 22:08, Tobias Hunger (tobias.hun...@gmail.com) wrote: The patch is line-broken, please resend non-linebroken version! I'll fix that, sorry. +static int add_usr_mount(void

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

From 681971f9cca5b3db085f47750f27f3f8d51f5036 Mon Sep 17 00:00:00 2001 From: Tobias Hunger tobias.hun...@digia.com Date: Wed, 24 Sep 2014 21:57:00 +0200 Subject: [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags= on kernel command line This allows to configure boot loader entries

[systemd-devel] [PATCH] Small cleanup for systemd-fstab-generator

From 4d038e78cd9656712a74901e0b6c79184764e7c1 Mon Sep 17 00:00:00 2001 From: Tobias Hunger tobias.hun...@digia.com Date: Fri, 3 Oct 2014 16:29:30 +0200 Subject: [PATCH 1/2] fstab-generator: Small cleanup --- src/fstab-generator/fstab-generator.c | 8 ++-- 1 file changed, 2 insertions(+), 6

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

Hoyer wrote: On 24.09.2014 22:08, Tobias Hunger wrote: From f3a193de94959875cd1d83f941ed8fc8275c82eb Mon Sep 17 00:00:00 2001 From: Tobias Hunger tobias.hun...@digia.com Date: Wed, 24 Sep 2014 21:57:00 +0200 Subject: [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags= on kernel

Re: [systemd-devel] [PATCH] fstab-generator: Honor usr=, usrfstype= and usrflags=

: On Thu, 09.10.14 09:37, Tobias Hunger (tobias.hun...@gmail.com) wrote: On Oct 8, 2014 2:15 PM, Harald Hoyer harald.ho...@gmail.com wrote: What is the rationale of this patch? Supporting systems without /etc/fstab in the root device? Overriding the /etc/fstab settings

[systemd-devel] [PATCH] Honor mount.usr*= on kernel command line

Lennart, Harald: I did check the kernel sources for the string \mount\: As expected that string does show up in a couple of places, but it does not seem to be in use as a module name at this time. Tobias G-R: Thanks for the instructions on how to use git-send-email:-) Tobias Hunger (1): fstab

[systemd-devel] [PATCH] fstab-generator: Honor mount.usr*= on kernel command line

This allows to configure boot loader entries for systems where the root and usr filesystems are in different subvolumes (or even on different drives). --- man/systemd-fstab-generator.xml | 76 - src/fstab-generator/fstab-generator.c | 90

Re: [systemd-devel] [PATCH] fstab-generator: Honor mount.usr*= on kernel command line

wrote: On Thu, 09.10.14 21:37, Tobias Hunger (tobias.hun...@gmail.com) wrote: This allows to configure boot loader entries for systems where the root and usr filesystems are in different subvolumes (or even on different drives). Thanks! Applied! Lennart -- Lennart Poettering, Red Hat

Re: [systemd-devel] So how am I supposed to put together my Linux system?

Hi Lennart, On Wed, Oct 22, 2014 at 7:03 PM, Lennart Poettering lenn...@poettering.net wrote: Sorry for the late response, been travelling for a month, and then have been more travelling, and still trying to process all the mails that queued up since. No problem at all:-) On Fri, Sep 5,

Re: [systemd-devel] So how am I supposed to put together my Linux system?

On Thu, Oct 23, 2014 at 12:51 AM, Lennart Poettering lenn...@poettering.net wrote: snip Correct. I can see that for some uses this might appear as overkill, but in general I would not make much of a distinction between the kernel and the basic userspace here, they really belong together. I

Re: [systemd-devel] feature request: dlopen

Hi Luke, I am mostly a lurker on the systemd mailing list, so my opinion does not carry weight in this community. On Tue, Feb 17, 2015 at 9:24 PM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: so i'm not going to protest - i'm going to try a different approach. i'd like you to look at this

Re: [systemd-devel] Is there trouble with git://anongit.freedesktop.org/systemd/systemd ?

Hah, now it works for me again, too. Thanks to whoever fixed the issue! On Sun, Mar 22, 2015 at 6:13 AM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 22 Mar 2015 00:23:07 +0100 Tobias Hunger tobias.hun...@gmail.com пишет: Hi! I get fatal: unable to connect

Re: [systemd-devel] How to factory reset?

on systemd-in-initrd debugging in arch linux would be appreciated at this point:-) On Fri, Mar 13, 2015 at 2:20 PM, Tobias Hunger tobias.hun...@gmail.com wrote: Hi Zbyszek, I would expect the machine-id to be written before mount units are processed, so for that to work I would need to mount

[systemd-devel] Is there trouble with git://anongit.freedesktop.org/systemd/systemd ?

Hi! I get fatal: unable to connect to anongit.freedesktop.org: anongit.freedesktop.org[0: 131.252.210.161]: errno=Connection refused all day long now. Is there something wrong with the git server or did I break something locally? Best Regards, Tobias

[systemd-devel] How to factory reset?

Hi everybody, I am running a kiosk-like box here and have a read-only copy of /etc hidden away in /usr/ somewhere. /etc is a symlink to that directory and that works fine. Recently I thought I'd experiment with factory reset. My idea was to use a tmpfs mounted on /etc instead of that symlink and

Re: [systemd-devel] How to factory reset?

If you're concerned about bootloader configuration modification as a threat vector, then it needs to go on an encrypted volume. This suggests an initial bootloader configuration that only enables the user to supply a passphrase/key file to unlock that volume, and then load a new bootloader

Re: [systemd-devel] How to factory reset?

Hi Lennart, thanks for taking the time to answer! It is highly appreciated. On Tue, Mar 10, 2015 at 5:01 PM, Lennart Poettering lenn...@poettering.net wrote: So you want not just factory reset, but actually a stateless system, where every single boot is basically a factory reset? Yes, but I

Re: [systemd-devel] How to factory reset?

On Tue, Mar 10, 2015 at 6:38 PM, Lennart Poettering lenn...@poettering.net wrote: On Tue, 10.03.15 18:13, Tobias Hunger (tobias.hun...@gmail.com) wrote: So you want not just factory reset, but actually a stateless system, where every single boot is basically a factory reset? Yes, but I do

Re: [systemd-devel] How to factory reset?

: On Tue, Mar 10, 2015 at 10:23:23PM +0100, Tobias Hunger wrote: On Tue, Mar 10, 2015 at 9:33 PM, Tobias Hunger tobias.hun...@gmail.com wrote: presets and machined ID are applied by PID 1, before it begins with starting any units, hence *really* early on. Note though that actually /etc/machine-id

Re: [systemd-devel] How to factory reset?

On Tue, Mar 10, 2015 at 9:33 PM, Tobias Hunger tobias.hun...@gmail.com wrote: presets and machined ID are applied by PID 1, before it begins with starting any units, hence *really* early on. Note though that actually /etc/machine-id is used as flag for is /etc empty. If the file exists

Re: [systemd-devel] [PATCH 1/2] fstab-generator: Support root on tmpfs (or other deviceless FS)

On Tue, Mar 24, 2015 at 5:12 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: This wouldn't work if fstype was NULL. We also have a list of network filesystems, whic I assume don't require a device, and we can consult this list instead of including it here. I pushed the patch with

[systemd-devel] [PATCH] fstab-generator: Do less sanity checking

Mount whatever the user asked to be mounted on / and /usr on the kernel command line. Do less sanity check and do *not* bail out when the mount device looks strange or does not exist. This basically makes the changes for deviceless filesystems from yesterday unnecessary and is in line with what

Re: [systemd-devel] [PATCH] fstab-generator: Do less sanity checking

Thanks Tom! I added the check for the rw /sys so that both the code path for fstab as well as for the kernel cmdline are doing similar checks. I was thinking about putting all the validation for both code paths into one function, but there are so many small things that only make sense in one of

Re: [systemd-devel] [PATCH 1/2] fstab-generator: Support root on tmpfs (or other deviceless FS)

=tmpfs Cheers, Tom On Tue, Mar 24, 2015 at 12:52 AM, Tobias Hunger tobias.hun...@gmail.com wrote: This allows for stateless systems. --- src/fstab-generator/fstab-generator.c | 21 + src/shared/util.c | 30 ++ src/shared

Re: [systemd-devel] feature request: dlopen

Hello Luke, On Mon, Feb 23, 2015 at 12:58 AM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: I understood most of these dependencies to be indirect: Packages that depend on other packages that in turn depend on libsystemd. Is that correct? that's right. so, what that means is that the

Re: [systemd-devel] feature request: dlopen

Hi Luke, On Mon, Feb 23, 2015 at 3:08 AM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: the problem, zbigniew, is that the intended use of this silent noop feature - to make it *possible* to have an alternative PID1 - *hasn't happened*. any upstream software developer who has added in

Re: [systemd-devel] [PATCH 1/2] fstab-generator: Support root on tmpfs (or other deviceless FS)

I won't promise anything, but I'll give it a try later tonight. It is a bit frightening under what kind of attention you people have to work: Even this tiny patch made it onto phoronix and I just got my first flame about ruining Linux. ___ systemd-devel

Re: [systemd-devel] [PATCH] fstab-generator: Support root on tmpfs

for in fstab-generator at this time, then I'd say it is out of scope for this patch. Best Regards, Tobias On Mon, Mar 23, 2015 at 9:39 AM, Vasiliy Tolstov v.tols...@selfip.ru wrote: 2015-03-23 11:21 GMT+03:00 Tobias Hunger tobias.hun...@gmail.com: I had been thinking about adding more device-less

Re: [systemd-devel] [PATCH] fstab-generator: Support root on tmpfs

the fstab-generator can support at this time. Best Regards, Tobias On Mon, Mar 23, 2015 at 11:17 AM, Vasiliy Tolstov v.tols...@selfip.ru wrote: 2015-03-23 13:02 GMT+03:00 Tobias Hunger tobias.hun...@gmail.com: I never used overlayfs myself, can you set up an overlayfs via the kernel commandline

Re: [systemd-devel] [PATCH] fstab-generator: Support root on tmpfs

for the review! Best Regards, Tobias On Mon, Mar 23, 2015 at 2:46 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Sun, Mar 22, 2015 at 08:29:25AM +0300, Andrei Borzenkov wrote: В Sun, 22 Mar 2015 00:57:23 +0100 Tobias Hunger tobias.hun...@gmail.com пишет: src/fstab-generator/fstab

[systemd-devel] [PATCH 1/2] fstab-generator: Support root on tmpfs (or other deviceless FS)

This allows for stateless systems. --- src/fstab-generator/fstab-generator.c | 21 + src/shared/util.c | 30 ++ src/shared/util.h | 1 + 3 files changed, 44 insertions(+), 8 deletions(-) diff --git

[systemd-devel] [PATCH 2/2] fstab-generator: Do not check deviceless filesystems

There is no need to check those. --- src/shared/generator.c | 5 + 1 file changed, 5 insertions(+) diff --git a/src/shared/generator.c b/src/shared/generator.c index 569b25b..c348ca2 100644 --- a/src/shared/generator.c +++ b/src/shared/generator.c @@ -42,6 +42,11 @@ int

[systemd-devel] [PATCH 0/2] support stateless systems on real hardware

issue due to /etc not being populated in time for dbus to pick up its settings. Best Regards, Tobias Tobias Hunger (2): fstab-generator: Support root on tmpfs (or other deviceless FS) fstab-generator: Do not check deviceless filesystems src/fstab-generator/fstab-generator.c | 21

Re: [systemd-devel] systemd-nspawn trouble

Hi Lennart, On Wed, Apr 22, 2015 at 1:46 PM, Lennart Poettering lenn...@poettering.net wrote: I was trying to run systemd-nspawn --ephemeral, but that failed since I had a read-only image in /var/lib/machines. Why is that not allowed? systemd-nspawn does create its own snapshot of that one

Re: [systemd-devel] systemd-nspawn trouble

PS: Is there a way to stop the VMs to get a btrfs subvolume created in /var/lib/machines? I have a couple of .#vm subvolumes in /var/lib/machines now and btrfs subvolume delete does not work on those since they have a subvolume in /var/lib/machine. Apparently systemd-nspawn also stumbled over

Re: [systemd-devel] systemd-nspawn trouble

On Wed, Apr 22, 2015 at 4:04 PM, Lennart Poettering lenn...@poettering.net wrote: Well, if that's what it says, then yes. We can certainly add support for manipulating nft too, but so far the APIs fo that appeared much less convincing to me, and quite a bit more exotic. The user space tools

Re: [systemd-devel] systemd-nspawn trouble

On Wed, Apr 22, 2015 at 3:12 PM, Tobias Hunger tobias.hun...@gmail.com wrote: Hi Lennart, On Wed, Apr 22, 2015 at 1:46 PM, Lennart Poettering lenn...@poettering.net wrote: I was trying to run systemd-nspawn --ephemeral, but that failed since I had a read-only image in /var/lib/machines. Why

[systemd-devel] systemd-nspawn trouble

Hi! Now that systemd 219 is finally available in arch I am playing with systemd-nspawn again. I was trying to run systemd-nspawn --ephemeral, but that failed since I had a read-only image in /var/lib/machines. Why is that not allowed? systemd-nspawn does create its own snapshot of that one after

Re: [systemd-devel] systemd-nspawn trouble

By the way: Is there a way to get the journal from a --ephemeral container? I had expected --link-journal=host to work, but --link-journal seems to not be allowed in any way. On Sat, Apr 25, 2015 at 12:14 AM, Tobias Hunger tobias.hun...@gmail.com wrote: Hello, sorry (again) for the delay. I

Re: [systemd-devel] systemd-nspawn trouble

, Apr 22, 2015 at 5:00 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 22.04.15 16:31, Tobias Hunger (tobias.hun...@gmail.com) wrote: On Wed, Apr 22, 2015 at 4:04 PM, Lennart Poettering lenn...@poettering.net wrote: Well, if that's what it says, then yes. We can certainly add

Re: [systemd-devel] systemd-nspawn trouble

Yes, I was referring to a container when using the name vm. Sorry if I caused confusion with this, I used to run lots of real VMs and then moved those over to containers and still think of those services as virtual machines. On Mon, Apr 27, 2015 at 5:01 PM, Lennart Poettering

Re: [systemd-devel] [systemd-commits] TODO

, Tobias Hunger (tobias.hun...@gmail.com) wrote: Hi Lennart, I just asked about the status of this, so I have links handy: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811 https://bugs.archlinux.org/task/44016 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970 https

Re: [systemd-devel] [PATCH v2] efi-boot-generator: Continue if /boot does not exist

220 that actually will make it into arch Linux and I can drop my hand-rolled packages:-) Best Regards, Tobias On Mon, Apr 13, 2015 at 3:27 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Sun, Apr 12, 2015 at 06:49:41PM +0200, Lennart Poettering wrote: On Sat, 11.04.15 02:13, Tobias

Re: [systemd-devel] [systemd-commits] TODO

Hi Lennart, I just asked about the status of this, so I have links handy: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811 https://bugs.archlinux.org/task/44016 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970 https://bugzilla.redhat.com/show_bug.cgi?id=1201964 All of

[systemd-devel] [PATCH] efi-boot-generator: Continue if /boot does not exist

/boot does not exist on a stateless system, so do not get confused by that. --- src/efi-boot-generator/efi-boot-generator.c | 23 +++ 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/src/efi-boot-generator/efi-boot-generator.c

[systemd-devel] [PATCH v2] gpt-generator: Find device on a stateless system

A stateless system has a tmpfs as root file system. That obviously does not have any block device associated with it. So try falling back to the device of the /usr filesystem if the root filesystem fails. --- src/gpt-auto-generator/gpt-auto-generator.c | 9 +++-- 1 file changed, 7

Re: [systemd-devel] [PATCH v2] gpt-generator: Find device on a stateless system

This time with fixed indentation. Sorry for taking so long to follow up on this, easter holidays were taking their toll:-) Best Regards, Tobias On Sat, Apr 11, 2015 at 1:52 AM, Tobias Hunger tobias.hun...@gmail.com wrote: A stateless system has a tmpfs as root file system. That obviously

[systemd-devel] [PATCH v2] efi-boot-generator: Continue if /boot does not exist

/boot does not exist on a stateless system, so do not get confused by that. --- src/efi-boot-generator/efi-boot-generator.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/efi-boot-generator/efi-boot-generator.c b/src/efi-boot-generator/efi-boot-generator.c index

Re: [systemd-devel] heads-up: chasing journal(?) related regression in 219 causing boot hang/fail

Hi Martin, did you make any progress with this bug? Apparently the same issue is blocking systemd-219 from getting into arch linux ( https://bugs.archlinux.org/task/44016 ), so this seems to be a wide-spread issue. Is anyone taking a serious look into this issue? Best Regards, Tobias On Mon,

Re: [systemd-devel] [PATCH] fstab-generator: Support root on tmpfs

over the eastern On Wed, Apr 8, 2015 at 11:21 PM, Lennart Poettering lenn...@poettering.net wrote: On Sun, 22.03.15 00:57, Tobias Hunger (tobias.hun...@gmail.com) wrote: BTW, if you are interested, I'd be willing to take this one step further even, and default to tmpfs as root fs, if only

[systemd-devel] [PATCH] gpt-generator: Find device on a stateless system

A stateless system has a tmpfs as root file system. That obviously does not have any block device associated with it. So try falling back to the device of the /usr filesystem if the root filesystem fails. --- src/gpt-auto-generator/gpt-auto-generator.c | 9 +++-- 1 file changed, 7

Re: [systemd-devel] nspawn: No Return key in machinectl login?

Thanks for the reply! I'll try to collect all requested info tonight or over the weekend. Best Regards, Tobias On Thu, Jun 18, 2015 at 9:24 PM, Lennart Poettering lenn...@poettering.net wrote: On Tue, 26.05.15 21:40, Tobias Hunger (tobias.hun...@gmail.com) wrote: This is stty -a from outside

Re: [systemd-devel] nspawn: No Return key in machinectl login?

the result in any way whether or not I run this in konsole or xterm. I got this on a laptop, so if you want to play with a machine that shows this behavior I can demonstrate it if that help:-) Best Regards, Tobias On Fri, Jun 19, 2015 at 10:15 AM, Tobias Hunger tobias.hun...@gmail.com wrote: Thanks

Re: [systemd-devel] nspawn --ephemeral

Hi Johannes, there is a tmpfiles.d rule in your container that creates that snapshot if it is not there yet. I started to create a var/lib/machines directory in the container as part of the container creation process, which prevents systemd 219 from creating the btrfs snapshot there.

Re: [systemd-devel] nspawn: No Return key in machinectl login?

Regards, Tobias On Tue, May 26, 2015 at 9:40 PM, Tobias Hunger tobias.hun...@gmail.com wrote: This is stty -a from outside the container: speed 38400 baud; rows 46; columns 114; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; swtch = undef; start = ^Q

[systemd-devel] nspawn: No Return key in machinectl login?

Hello, I am having a problem with one of my containers set up with systemd-nspawn. For some reason the return key will not work most of the time (19 out of 20 attemps) after doing machinectl login into that machine. This effects not all programs: bash works, fish-shell does not. Sudo password

Re: [systemd-devel] nspawn: No Return key in machinectl login?

part of your reply. I tried running stty eol ^D -F /dev/pts/0 inside the container and got a SIGSEGV. It works outside the container. Best Regards, Tobias On Tue, May 26, 2015 at 4:11 PM, Lennart Poettering lenn...@poettering.net wrote: On Sat, 23.05.15 00:09, Tobias Hunger (tobias.hun

Re: [systemd-devel] About the state of two posts

Hi John, I do run a couple of (mostly -- I do keep /var) stateless systems and have few problems with those ever since systemd 222. Best Regards, Tobias On Mon, Aug 24, 2015 at 2:10 PM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 21.08.15 07:24, john maverick

[systemd-devel] systemd-nspawn --setenv=SOMETHING=other: What is that for?

Hi Systemd List! I have been trying today to pass some information into a container I set up with systemd-nspawn, using --setenv=SOMEVAR=foo. That works, I see SOMEVAR in /proc/1/environ of the container. So far so good. Now I want to use that information to configure a service, so I add a

Re: [systemd-devel] systemd-nspawn --setenv=SOMETHING=other: What is that for?

Am 25.10.2015 00:41 schrieb "Zbigniew Jędrzejewski-Szmek" : > There is not built-in support for that. > > You can always look at /proc/1/environ from privileged processes, or add > a generator script to create the units you need from that file. Most non-trivial docker images

Re: [systemd-devel] systemd-nspawn --setenv=SOMETHING=other: What is that for?

Hi Lennart, the ContainerInterface says: "The container manager should set $container_uuid= as environment variable for the container's PID 1 to the container UUID it wants to set." I had expected that to be implemented by not resetting this environment variable when starting whichever service

Re: [systemd-devel] Pass environment variables down to systemd-service in container

THANKS! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] nspawn: No Return key in machinectl login?

, Tobias On Fri, Jun 19, 2015 at 10:15 AM, Tobias Hunger tobias.hun...@gmail.com wrote: Thanks for the reply! I'll try to collect all requested info tonight or over the weekend. Best Regards, Tobias On Thu, Jun 18, 2015 at 9:24 PM, Lennart Poettering lenn...@poettering.net wrote: On Tue

[systemd-devel] Systemd 226: Neither machinectl login nor machinectl shell works

Hello, I just upgraded to systemd 226 in the hope that machinectl shell will work better for me than machinectl login. Unfortunately it is not and machinectl login is also unusable:-/ Both produce the "Connected to machine X. Press ^] three times within 1s to exit session" line and then just sit

Re: [systemd-devel] machinectl shell

Hi Arnaud, Am 04.10.2015 11:27 schrieb "arnaud gaboury" : > > First, thank you for this new feature. I do think this is a much more > clean way to log as root. > > I just can't get the correct shell, which is /bin/zsh: > > /etc/passwd > --- >

Re: [systemd-devel] Systemd 226: Neither machinectl login nor machinectl shell works

On Sun, Sep 6, 2015 at 12:13 PM, Lennart Poettering wrote: > This should be fixed with git now. And we'll do a new release very > soon now. Any progress yet on the "very soon now" release? Building systemd manually and then integrating that into a newly installed copy

Re: [systemd-devel] echo message not coming on terminal with systemd

Am 18.12.2015 07:51 schrieb "Navneet Sinha" : > No it doesn't fix it. Secondly, my main problem is why it is not working with systemd. When, I was using this script as initscript before porting this to systemd. I was able to see all echo messages. Sysvinit did not

[systemd-devel] How to debug machinectl shell?

Hello List, I am running on arch-linux, using systemd 228 and have a machine started using systemd-nspawn. It shows up in machinectl list. I can machinectl login MACHINE into this machine, but when I try to run machinectl shell MACHINE I only get this: Failed to get shell PTY: Cannot set

Re: [systemd-devel] Stateless system howto

Hi Visali, Am 25.02.2016 20:47 schrieb "Vasiliy Tolstov" : > > Hi,i want to build image that mounts readonly /usr and / readwrite. That is really simple to do: Just edit the kernel command line to include the appropriate flags to mount usr read-only. Documentation for the

Re: [systemd-devel] systemd efi boot and default entry

Hi Alex, On Fri, Apr 1, 2016 at 5:14 PM, Alex Crawford <alex.crawf...@coreos.com> wrote: > On 04/01, Tobias Hunger wrote: >> IIRC both coreos and chormeOS only mark a boot as successful after >> talking to their respective update servers. The assumption apparently >> is

Re: [systemd-devel] systemd efi boot and default entry

Hi Johann, Am 01.04.2016 17:38 schrieb "Jóhann B. Guðmundsson" : > So if your server has the role of an web server and the web service fails to run or is not run ( for example you forgot to enable it, or you misconfigured it before rebooting ) or that phone home service failed

Re: [systemd-devel] systemd efi boot and default entry

Hi Jóhann and Vasiliy, IIRC both coreos and chormeOS only mark a boot as successful after talking to their respective update servers. The assumption apparently is that the OS can fix itself when it is able to communicate properly with its own update server. It would be nice if something similar

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

Hi Chris, Am 20.04.2016 18:48 schrieb "Chris Murphy" : > There two IRSTs. One is Rapid Storage (firmware raid working in > conjunction with mdadm), the other is Rapid Start. I am aware of that and we both refer to the same thing. > Rapid Start is what > I'm referring to

Re: [systemd-devel] PredictableInterfaceNames and Debian

Am 16.04.2016 18:46 schrieb "Xen" : > And if you did need to write stuff: why not queue the changes and then > apply them after the remount rw, if that is necessary? Create an overlay > to /etc ;-), write stuff to the overlay, then remount, freeze access, > and write the

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

Am 20.04.2016 06:47 schrieb "Chris Murphy" : > I kinda have to agree, if it can't be encrypted, then I think linux > hibernation is almost pointless, and maybe just give up. Intel Rapid > Start (firmware managed) hibernation with SSDs and the proper GPT > partition type

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

Am 20.04.2016 22:42 schrieb "Chris Murphy" <li...@colorremedies.com>: > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger <tobias.hun...@gmail.com> wrote: > > > https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/T460s-Does-it-have-Intel-rapid-start

Re: [systemd-devel] systemd.volatile=yes

Hi Lennart, I probed a bit deeper: Apparently the openssh package is currently borked in arch linux:-/ I ended up with a slightly different version in the non systemd.volatile case which does work:-/ Sorry for the false alarm and wasting your time. Best Regards, Tobias PS: I did send the

Re: [systemd-devel] systemd.volatile=yes

Hi Lennart, On Mon, Sep 4, 2017 at 11:06 AM, Lennart Poettering wrote: > Hmm, mount.usr= should continue to be supported. It's documented in > the systemd-fstab-generator man page however, not in the > kernel-command-line one. We should fix that however, can you file a >

[systemd-devel] systemd.volatile=yes

Hi, I have been running a system based on a tmpfs as '/' and with a read-only /usr for a while now and am rather happy with that setup. I added "mount.usr" and similar flags to systemd ages ago, so that I could configure that setup via kernel parameters. That has worked great so far. Recently I

Re: [systemd-devel] Multiple initrds in unified kernel images?

On Fri, Oct 5, 2018 at 9:10 AM David Anderson wrote: > > And of course, the law of asking questions on the internet is verified, and I > find the answer minutes after asking a thousand people. A Linux initramfs is > a concatenation of cpio archives, so I can just `cat microcode.img initrd.gz >

Re: [systemd-devel] Stateless system - Centos8 and overlayfs on root

Hi, You said no data is to be stored when powered down. What do you need the overlay for then? Just mount to a tmpfs as '/' and centos as '/usr', which is something that systemd supports out of the box. You will need at least some files in /etc for this to work, and I just have the initrd untar

Re: [systemd-devel] : How to modify systemd so that the NTP function is disabled when systemd is first started?

Hi www, On Thu, Apr 23, 2020, 04:14 www wrote: > hi Michal and Kevin, > > We applied systemd to embedded Linux, so we often need to update/flash the > whole system. When we select disable *time synchronization* function, > the embedded system will use the time itself. After we update the

Re: [systemd-devel] How to use systemd-repart partitions?

Hi Lennart, On Wed, May 20, 2020 at 12:01 PM Lennart Poettering wrote: > On Mi, 20.05.20 00:12, Tobias Hunger (tobias.hun...@gmail.com) wrote: > > The one thing that is frustrating is to get a machine image generated > > by my build server onto a new piece of hardware. So I wanted

Re: [systemd-devel] How to use systemd-repart partitions?

Hi Lennart, On Tue, May 19, 2020 at 11:26 PM Lennart Poettering wrote: > So, yes, "systemd-makefs" was how I intended this originally to be > done. However, I think that's not going to suffice in the long run, > and instead systemd-repart will soon be able to format file systems > natively by

[systemd-devel] How to use systemd-repart partitions?

Hello! I am experimenting with automatically partitioning, formatting and creating files on a new drive based on configuration. Systemd comes with all the building blocks nowadays to do this, but I am still struggling a bit. I have created some partition definitions and ran systemd-repart to

Re: [systemd-devel] How to use systemd-repart partitions?

On Wed, May 20, 2020, 15:21 Lennart Poettering wrote: > > What about things like create subvolumes on BTRFS? systemd-tmpfiles > > does support that. > > If this is desirable we could probably add MakeSubvolume= or so which > is applied before CopyFiles= is run, or so. CopyFiles and CopyBlocks

Re: [systemd-devel] How to use systemd-repart partitions?

Hi Chris, On Sat, May 30, 2020, 10:09 Chris Murphy wrote: > Future feature for the former case: > - Btrfs seed/sprout feature expressly supports this use case for > replicating a seed image when destination is also Btrfs. > # mount /dev/seed /mnt > # btrfs device add /dev/sprout /mnt > # mount

Re: [systemd-devel] Strange partition layout from systemd-repart

I took the liberty to implement support for a setup script to systemd-repart here: https://github.com/systemd/systemd/pull/16258 The patch is incomplete: It is missing documentation, tests and is basically just a sketch of the implementation, but I would appreciate some feedback anyway before I

[systemd-devel] Strange partition layout from systemd-repart

Hello! I have a 32GB USB stick and used dd to put a ~2.5GB image onto it. The image contains three partitions (ESP, root, root-verity). I would like to make the remaining space on the USB stick available to users. So I created a set of files for systemd-repart: 00_esp.conf: [Partition] Type=esp

Re: [systemd-devel] Strange partition layout from systemd-repart

. I'll fix the image generation. Maybe there is some way to improve the reporting done by systemd-repart in such a case? Best Regards, Tobias On Thu, Jun 4, 2020 at 4:42 PM Tobias Hunger wrote: > > Hello! > > I have a 32GB USB stick and used dd to put a ~2.5GB image onto it. The >

Re: [systemd-devel] Networking in a systemd-nspawn container

Hi Lennart, On Fri, Nov 19, 2021 at 2:23 PM Lennart Poettering wrote: > Two ideas I recently thought about: > > 1. Maybe resolved's "stub" logic should support listening on yet >another local IP address: 127.0.0.54 or so, where the same stub >listens as on 127.0.0.53, but where we

[systemd-devel] Networking in a systemd-nspawn container

Hello Systemd Mailing List! I have a laptop and run a couple of systemd-nspawn containers on that machine. This works great, except that name resolution insode the containers fails whenever the network on the outside changes. This is not too surprising: At setup time the resolver information is