For that kind of complicated case, I would recommand mounting /data in your
initrd (i.e before the real systemd is started)
If you don't have an initrd in your system, you can replace systemd with a
simple shell script. We did something similar recently
#!/bin/sh
/bin/mount /dev/sda4 /data
exec
On Mo, 01.07.19 08:25, Belisko Marek (marek.beli...@gmail.com) wrote:
> Hi,
>
> I'm working on rpi3 by using mender OTA system and for identifying
> devices I would like to have for every of it different hostname. As
> rootfs is update-able (rootA, rootB layout) so I tried to create file
> in /dat
Hi,
on my current Fedora (30) system, I'm trying to hook a test to
validate systemd unit files via `systemd-analyze verify`
this however has a problem that it analyzes & verifies the entire
chain, reporting errors if _any_ of the system units has an error.
Is there a way to limit `verify` to on
On Mon, 01 Jul 2019 08:20:23 +0200
"Ulrich Windl" wrote:
> >>> Simon McVittie schrieb am 11.06.2019 um
> >>> 16:29 in Nachricht
> <20190611142939.GA6676@horizon>:
> > On Tue, 11 Jun 2019 at 15:44:07 +0200, Ulrich Windl wrote:
> >> Does anybody running the list care to fix the list-processor.
Care to open an issue at GitHub ?
On Fri, Jun 28, 2019 at 7:52 PM Christian Rohmann
wrote:
>
> Hello systemd-devel,
>
> after a recent update to systemd 241 my previously working GRE tunnel
> does not work anymore:
>
> Jun 28 13:58:54 localhost systemd-networkd[637]: mytunnel:
> vti/ipip/sit/gre/
On Mon, Jul 1, 2019 at 9:48 AM Lennart Poettering
wrote:
>
> On Mo, 01.07.19 08:25, Belisko Marek (marek.beli...@gmail.com) wrote:
>
> > Hi,
> >
> > I'm working on rpi3 by using mender OTA system and for identifying
> > devices I would like to have for every of it different hostname. As
> > rootfs
