public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Taneli Liljasto <taneli.liljasto@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Request for Assistance: Customizing systemd Configuration on Isar Build System
Date: Sat, 18 Mar 2023 18:16:10 -0700 (PDT)	[thread overview]
Message-ID: <79978853-0ee3-4f11-b58c-69e649bdd035n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1238 bytes --]

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.

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

[-- Attachment #1.2: Type: text/html, Size: 1281 bytes --]

             reply	other threads:[~2023-03-19  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  1:16 Taneli Liljasto [this message]
2023-03-19 12:11 ` Henning Schild
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=79978853-0ee3-4f11-b58c-69e649bdd035n@googlegroups.com \
    --to=taneli.liljasto@gmail.com \
    --cc=isar-users@googlegroups.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