All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "Openembedded-core@lists.openembedded.org"
	<Openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v6] systemd: Build the systemctl executable
Date: Thu, 20 Feb 2025 16:52:50 +0100	[thread overview]
Message-ID: <ae46ffa2-b88d-4ec5-822a-08c00e2baa46@gmail.com> (raw)
In-Reply-To: <1825F47182B39BA0.23135@lists.openembedded.org>

From meta/classes-recipe/rootfs-postcommands.bbclass:

     # 20:12 < mezcalero> koen: you have three options: a) run 
systemd-machine-id-setup at install time, b) have / read-only and an 
empty file there (for stateless) and c) boot with / writable
         touch ${IMAGE_ROOTFS}${sysconfdir}/machine-id
     fi

We could think of further improvements. One thing that comes to mind is 
changing systemd-systemctl-native to systemd-tools-native and enable the 
build of systemd-machine-id-setup.

Slava

On 20.02.2025 16:33, Vyacheslav Yurkov via lists.openembedded.org wrote:
> Isn't is supposed to be created on first boot?
>
> Slava
>
> On 20.02.2025 15:07, Ross Burton wrote:
>> On 19 Feb 2025, at 10:39, Vyacheslav Yurkov via 
>> lists.openembedded.org <uvv.mail=gmail.com@lists.openembedded.org> 
>> wrote:
>>> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
>>>
>>> Instead of the python re-implementation build the actual systemctl from
>>> the systemd source tree. The python script was used when systemd didn't
>>> provide an option to build individual executables. It is possible in 
>>> the
>>> meantime, so instead of always adapting the script when there's a new
>>> functionality, we simply use upstream implementation.
>> If I compare an image built with master and this, there’s one notable 
>> change in the file list:
>>
>> Changes to images/qemuarm64/glibc/core-image-full-cmdline 
>> (files-in-image.txt):
>>    /etc/machine-id was removed
>>
>> The good news is that apart from that the final images are identical, 
>> but that change wasn’t expected.
>>
>> Ross
>



  parent reply	other threads:[~2025-02-20 15:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 10:39 [PATCH v6] systemd: Build the systemctl executable uvv.mail
2025-02-20 14:07 ` [OE-core] " Ross Burton
2025-02-20 15:33   ` Vyacheslav Yurkov
     [not found]   ` <1825F47182B39BA0.23135@lists.openembedded.org>
2025-02-20 15:52     ` Vyacheslav Yurkov [this message]
2025-02-20 16:03       ` Alex Kiernan
2025-02-25 11:21         ` Richard Purdie
2025-02-25 12:23           ` Mikko Rapeli
2025-02-25 13:50             ` Richard Purdie
2025-02-25 14:48         ` Ross Burton
2025-02-26 10:43           ` Vyacheslav Yurkov
2025-02-28 15:56             ` Alexis CELLIER
2025-02-28 16:33               ` Alex Kiernan
2025-02-28 17:28                 ` Alexis CELLIER
2025-02-28 21:09                   ` Alex Kiernan
2025-03-04  9:27           ` Koen Kooi
2025-02-20 17:08       ` Ross Burton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae46ffa2-b88d-4ec5-822a-08c00e2baa46@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=Ross.Burton@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.