From: Henning Schild <henning.schild@siemens.com>
To: Taneli Liljasto <taneli.liljasto@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: Request for Assistance: Customizing systemd Configuration on Isar Build System
Date: Sun, 19 Mar 2023 13:11:33 +0100 [thread overview]
Message-ID: <20230319131133.1353620e@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <79978853-0ee3-4f11-b58c-69e649bdd035n@googlegroups.com>
Am Sat, 18 Mar 2023 18:16:10 -0700 (PDT)
schrieb Taneli Liljasto <taneli.liljasto@gmail.com>:
> Hi,
>
> I hope this message finds you well. I am relatively new to BitBake
> and the process of creating custom Linux images. I am currently
> working on a project that requires the modification of the systemd
> configuration file located at /etc/systemd/system.conf. My objective
> is to enable the watchdog feature and alter the logging settings
> within this file.
Touching this file could turn out hard because it is owned by a package
that you in Isar install directly from Debian.
Better would be to set the values from snippet files in
/etc/systemd/system.conf.d/*.conf those snippets would be installed via
a customizations package using the class "dpkg-raw"
Best try it first manually and once you know what files and lines you
want start writing your package recipe and make sure the package gets
installed with IMAGE_INSTALL.
An example can actually be found here
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/89ec2cb2d8709419c8adffdc071242c69e50266a
It does watchdog, also something on printing and other things.
Henning
> I have been utilizing meta-isar's application recipes as a reference
> to include my custom files on the device. However, I have encountered
> a challenge with customizing the settings, as my files are being
> overwritten by package configurations during the build process. It
> appears that I may be missing some critical understanding of the
> correct method to achieve this customization.
>
> I kindly request your guidance on this matter. Your expertise and
> recommendations on how to properly modify the systemd configuration
> file within the Isar build system would be greatly appreciated. If
> there are any resources or documentation that you believe may be
> helpful in this regard, please do not hesitate to share them.
>
> Thank you in advance for your time and assistance. I look forward to
> learning from your collective knowledge and experience.
>
> Best regards,
> Taneli Liljasto
>
next prev parent reply other threads:[~2023-03-19 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 1:16 Taneli Liljasto
2023-03-19 12:11 ` Henning Schild [this message]
2023-03-19 17:50 ` Taneli Liljasto
2023-03-19 18:39 ` Henning Schild
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=20230319131133.1353620e@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=taneli.liljasto@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox