Hi Alex,
On 06/05/2019 11:36, Alex Kiernan wrote:
On Mon, May 6, 2019 at 5:54 AM Jonas Bonn wrote:
Hi Alex,
The below is fine and looks good. The one thing that bothers me about
this is that "stateless" isn't really a property of the "distro", rather
it's a property
Hi Peter,
On 06/05/2019 12:28, Peter Kjellerstedt wrote:
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org On Behalf Of Jonas Bonn
Sent: den 6 maj 2019 06:54
To: Alex Kiernan ; openembedded-
c...@lists.openembedded.org
Subject: Re: [OE-core] [OE-Core][PATCH
Hi Alex,
The below is fine and looks good. The one thing that bothers me about
this is that "stateless" isn't really a property of the "distro", rather
it's a property of the image/machine. I suspect, in the same sense that
we have readonly-rootfs, that we should probably have image
Hi Alex,
On 02/05/2019 23:09, Alex Kiernan wrote:
From: Alex Kiernan
Rather than rely on systemd's default invocation of preset-all at
runtime, we pre-populate the symlink tree as part of of the image. This
is done late so any overrides of presets during rootfs construction
should already
simplify creation of machine-specific configuration
systemctl-native: Rewrite in Python supporting preset-all and mask
image: call systemctl preset-all for images
Jonas Bonn (3):
systemd: don't build firstboot by default
systemd: do not create machine-id
systemd:
Hi Alex,
On 26/04/2019 16:14, Alex Kiernan wrote:
On Thu, Apr 18, 2019 at 11:22 AM Andrej Valek wrote:
PATCH REBASED:
==
0001-do-not-disable-buffer-in-writing-files.patch
0002-don-t-use-glibc-specific-qsort_r.patch
0003-missing_type.h-add-__compare_fn_t-and-comparison_fn_.patch
On 13/02/2019 21:45, Randy MacLeod wrote:
On 2/13/19 5:00 AM, Jonas Bonn wrote:
On 11/02/2019 13:15, mikko.rap...@bmw.de wrote:
On Mon, Feb 11, 2019 at 12:08:46PM +, André Draszik wrote:
Please ignore this patch. Looks like a red-herring. Sorry for the
noise.
FWIW, I would like
On 11/02/2019 13:15, mikko.rap...@bmw.de wrote:
On Mon, Feb 11, 2019 at 12:08:46PM +, André Draszik wrote:
Please ignore this patch. Looks like a red-herring. Sorry for the noise.
FWIW, I would like to see this patch merged. Had some issues in the past
with busybox umount and added same
Hi Richard,
On 30/01/2019 22:54, Richard Purdie wrote:
On Mon, 2019-01-28 at 21:58 +0100, Jonas Bonn wrote:
Changed in v4:
- add patch to make systemd-firstboot a non-default option to systemd
to
prevent unexpected prompts at runtime
There were still some failures:
https
The dependency on systemd-systemctl-native is only needed if _both_
systemd and sysvinit are in play.
Signed-off-by: Jonas Bonn
---
meta/recipes-bsp/keymaps/keymaps_1.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/keymaps/keymaps_1.0.bb
b/meta/recipes
Signed-off-by: Jonas Bonn
---
meta/recipes-core/glibc/glibc-package.inc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-package.inc
b/meta/recipes-core/glibc/glibc-package.inc
index a98ae1a29c..329732f48c 100644
--- a/meta/recipes-core/glibc
Signed-off-by: Jonas Bonn
---
meta/recipes-core/dbus/dbus_1.12.10.bb | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus_1.12.10.bb
b/meta/recipes-core/dbus/dbus_1.12.10.bb
index d71f7f7042..d3301278b0 100644
--- a/meta/recipes-core/dbus
mount can generally figure out the filesystem type from the superblock;
otherwise, /proc/filesystems is a more correct fallback than
/etc/filesystems and presumably always available.
Signed-off-by: Jonas Bonn
---
meta/recipes-core/base-files/base-files/filesystems | 8
meta/recipes
When the rootfs is read-only, we cannot rely on systemd's default
invocation of preset-all at runtime in order to enable services. As
such, we need to do it at image creation time.
Signed-off-by: Jonas Bonn
---
meta/classes/rootfs-postcommands.bbclass | 2 ++
1 file changed, 2 insertions
.
Signed-off-by: Jonas Bonn
---
meta/classes/rootfs-postcommands.bbclass | 6 ++
meta/recipes-core/systemd/systemd-conf.bb | 9 ++---
meta/recipes-core/systemd/systemd_239.bb | 1 -
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/meta/classes/rootfs-postcommands.bbclass
b
'... not sure that this
ever worked as the implementation looks bogus and there aren't any users
anyway. This patch removes the 'preset' subcommand, as well.
Signed-off-by: Jonas Bonn
---
.../systemd/systemd-systemctl/systemctl | 36 ---
1 file changed, 7 insertions(+), 29
...
With this patch, systemd gets the right configuration irregardless of
whether /etc is populated at boot or not (i.e. in a "stateless"
system).
License-Update: configuration snippets licensing is independent of
systemd licensing
Signed-off-by: Jonas Bonn
---
meta/recipes-core/systemd/systemd-co
on systemd to do the service enablement.
This breaks the read-only-rootfs case; there's a fix for this in a
follow-up patch.
Signed-off-by: Jonas Bonn
---
meta/classes/systemd.bbclass | 33 -
1 file changed, 16 insertions(+), 17 deletions(-)
diff --git a/meta
voked and presenting a prompt to the user.
With this patch, the firstboot service becomes a PACKAGECONFIG option
that the user must actively select.
Signed-off-by: Jonas Bonn
---
meta/recipes-core/systemd/systemd_239.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/syste
moving things in that direction shortly.
/Jonas
Jonas Bonn (6):
systemd: don't build firstboot by default
systemd: do not create machine-id
systemd-conf: simplify creation of machine-specific configuration
systemd: create preset files instead of installing in image
systemd-systemctl
On 28/01/2019 18:26, Richard Purdie wrote:
On Mon, 2019-01-28 at 14:31 +, Richard Purdie wrote:
On Mon, 2019-01-28 at 15:26 +0100, Jonas Bonn wrote:
Hi,
On 28/01/2019 14:55, Richard Purdie wrote:
Unfortunately this series failed in testing:
https://autobuilder.yoctoproject.org
Hi,
On 28/01/2019 14:55, Richard Purdie wrote:
Unfortunately this series failed in testing:
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/226
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/167
so it looks like it may need some tweaks before we can merge
on systemd to do the service enablement.
This breaks the read-only-rootfs case; there's a fix for this in a
follow-up patch.
Signed-off-by: Jonas Bonn
---
meta/classes/systemd.bbclass | 33 -
1 file changed, 16 insertions(+), 17 deletions(-)
diff --git a/meta
s" configuration.
Getting to a "volatile" system (just empty /var) should be easier and
I'll post patches moving things in that direction shortly.
/Jonas
Jonas Bonn (5):
systemd: do not create machine-id
systemd-conf: simplify creation of machine-specific configuratio
When the rootfs is read-only, we cannot rely on systemd's default
invocation of preset-all at runtime in order to enable services. As
such, we need to do it at image creation time.
Signed-off-by: Jonas Bonn
---
meta/classes/rootfs-postcommands.bbclass | 2 ++
1 file changed, 2 insertions
.
Signed-off-by: Jonas Bonn
---
meta/classes/rootfs-postcommands.bbclass | 6 ++
meta/recipes-core/systemd/systemd-conf.bb | 9 ++---
meta/recipes-core/systemd/systemd_239.bb | 1 -
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/meta/classes/rootfs-postcommands.bbclass
b
'... not sure that this
ever worked as the implementation looks bogus and there aren't any users
anyway. This patch removes the 'preset' subcommand, as well.
Signed-off-by: Jonas Bonn
---
.../systemd/systemd-systemctl/systemctl | 36 ---
1 file changed, 7 insertions(+), 29
...
With this patch, systemd gets the right configuration irregardless of
whether /etc is populated at boot or not (i.e. in a "stateless"
system).
License-Update: configuration snippets licensing is independent of
systemd licensing
Signed-off-by: Jonas Bonn
---
meta/recipes-core/systemd/systemd-co
Hi Peter,
On 07/01/2019 17:43, Peter Kjellerstedt wrote:
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org On Behalf Of Jonas Bonn
+def systemd_create_presets(pkg):
+action = get_package_var(d, 'SYSTEMD_AUTO_ENABLE', pkg)
+presetf
When the rootfs is read-only, we cannot rely on systemd's default
invocation of preset-all at runtime in order to enable services. As
such, we need to do it at image creation time.
Signed-off-by: Jonas Bonn
---
meta/classes/rootfs-postcommands.bbclass | 2 ++
1 file changed, 2 insertions
'... not sure that this
ever worked as the implementation looks bogus and there aren't any users
anyway. This patch removes the 'preset' subcommand, as well.
Signed-off-by: Jonas Bonn
---
.../systemd/systemd-systemctl/systemctl | 36 ---
1 file changed, 7 insertions(+), 29
...
With this patch, systemd gets the right configuration irregardless of
whether /etc is populated at boot or not (i.e. in a "stateless"
system).
License-Update: configuration snippets licensing is independent of
systemd licensing
Signed-off-by: Jonas Bonn
---
meta/recipes-core/systemd/systemd-co
.
Signed-off-by: Jonas Bonn
---
meta/classes/rootfs-postcommands.bbclass | 6 ++
meta/recipes-core/systemd/systemd-conf.bb | 9 ++---
meta/recipes-core/systemd/systemd_239.bb | 1 -
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/meta/classes/rootfs-postcommands.bbclass
b
t;volatile" system (just empty /var) should be easier and
I'll post patches moving things in that direction shortly.
/Jonas
Jonas Bonn (5):
systemd: do not create machine-id
systemd-conf: simplify creation of machine-specific configuration
systemd: create preset files instead of instal
on systemd to do the service enablement.
This breaks the read-only-rootfs case; there's a fix for this in a
follow-up patch.
Signed-off-by: Jonas Bonn
---
meta/classes/systemd.bbclass | 33 -
1 file changed, 16 insertions(+), 17 deletions(-)
diff --git a/meta
On 02/01/2019 08:58, ChenQi wrote:
Hi Jonas,
Cleaning up systemd's /etc files while leaving other softwares requiring
/etc files is not that pleasant. At a minimum, systemd users who are not
aware of this 'stateless' concept would be confused. "Where's my
/etc/systemd/system.conf file?!"
Hi Alex,
On 02/01/2019 13:06, Alexander Kanavin wrote:
On Mon, 31 Dec 2018 at 13:07, Jonas Bonn wrote:
diff --git a/meta/recipes-core/systemd/systemd_239.bb
b/meta/recipes-core/systemd/systemd_239.bb
index 70e687c92e..7b4c5c56aa 100644
--- a/meta/recipes-core/systemd/systemd_239.bb
+++ b
trickier due to needing to handle users, etc., but we'll
get there.
But please don't get hung up on the "stateless" aspect of things when
looking at this patch series. These systemd patches are independent of
whether or not that is the goal.
/Jonas
Best Regards,
Chen Qi
On 12/31/2018 08:0
Hi Randy,
Thanks for looking at this.
On 01/01/2019 16:29, Randy MacLeod wrote:
On 12/31/18 7:05 AM, Jonas Bonn wrote:
The configuration files that systemd installs are just skeletons
detailing the available options and their default values. The
recommended means of changing
Now that the systemd class sets up service presets instead of actively
enabling services, the 'enable' and 'disable' subcommands for systemctl
are not actually used anywhere. As such, we can remove these to make
sure that nobody inadvertently introduces new uses of them.
We do, however, one case
At first boot, systemd will create the /etc/systemd/system directory
from service preset files. As such, for a normal, writable /etc
(writable rootfs), there is no need to set up this directory at image
creation time.
This patch changes the systemd machinery to create preset files and to
rely on
When the rootfs is read-only, we cannot rely on systemd's default
invocation of preset-all at runtime in order to enable services. As
such, we need to do it at image creation time.
---
meta/classes/rootfs-postcommands.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git
At installation, systemd _both_ installs preset files for its services
and enables the services accordingly (effectively, calling 'systemctl
preset-all' on its own services). As we now rely on systemd calling
preset-all at first boot, there's no need to carry the pre-populated
/etc/systemd/system
sier and
I'll post patches moving things in that direction shortly.
/Jonas
Jonas Bonn (7):
systemd: do not create machine-id
systemd-conf: simplify creation of configuration
systemd: move additional conffiles to systemd-conf
systemd: create preset files instead of installing in image
systemd-syste
There is no reason to have an emtpy machine-id as part of the systemd
package. Either:
i) the filesystem is writable and the file will be created
automatically; or
ii) the filesystem is read-only, in which case the empty machine-id file
should be created as part of the read-only-rootfs tweaks.
The configuration files that systemd installs are just skeletons
detailing the available options and their default values. The
recommended means of changing the configuration is to provide snippets
in configuration directories. For example, journald.conf settings are
best set in
---
meta/recipes-core/systemd/systemd-conf.bb | 4 +++-
meta/recipes-core/systemd/systemd_239.bb | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/systemd/systemd-conf.bb
b/meta/recipes-core/systemd/systemd-conf.bb
index a504afe3e7..ea99166a2e 100644
---
47 matches
Mail list logo
