From: Anton Mikanovich <amikan@ilbers.de>
To: "Heinisch, Alexander" <alexander.heinisch@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] isar-installer: Added option to add additional kernel cmdline arguments for isar-image-installer.
Date: Wed, 11 Dec 2024 14:18:03 +0200 [thread overview]
Message-ID: <44f7ed38-5b3e-43ea-b6d4-41d9a7ea5c4a@ilbers.de> (raw)
In-Reply-To: <AM7PR10MB3320678AB826E49F14E985EC863E2@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM>
11/12/2024 13:57, Heinisch, Alexander wrote:
>> Hello Alexander,
>>
>> Can you also add any kind of usage example?
> You can find some examples here: https://github.com/ilbers/isar/commit/4c66faf1110ded164440df8108effef7e9a52d34
>
> - installer.unattended
> - installer.image.uri ...file name of the image to be installed (parameter name uri chosen since we plan to support download of images in upcoming patches)
> - installer.target.dev ...target device name (e.g. /dev/sda) for the image to be installed to
> - installer.target.overwrite ...strategy how to handle target devices not empty (possible values: OVERWRITE - overwrite data on target | ABORT - abort installation if target not empty)
>
> I will put the link and a short description in the commit message!
> Since, I plan to push further changes for the target bootstrapping,
> I'd prefer to update the documentation, once that's done.
>
> BR Alexander
Thanks, but I mean the usage of ADDITIONAL_KERNEL_CMDLINE with any
sample target, so we will have all the way of that variables starting
from image generation to have them handled in handle-config.sh.
This will help to keep tracking this functionality for regressions.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/44f7ed38-5b3e-43ea-b6d4-41d9a7ea5c4a%40ilbers.de.
next prev parent reply other threads:[~2024-12-11 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 9:35 alexander.heinisch via isar-users
2024-12-11 9:49 ` 'Florian Bezdeka' via isar-users
2024-12-11 11:52 ` 'Heinisch, Alexander' via isar-users
2024-12-11 9:53 ` Anton Mikanovich
2024-12-11 11:57 ` 'Heinisch, Alexander' via isar-users
2024-12-11 12:18 ` Anton Mikanovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 8:42 alexander.heinisch via isar-users
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=44f7ed38-5b3e-43ea-b6d4-41d9a7ea5c4a@ilbers.de \
--to=amikan@ilbers.de \
--cc=alexander.heinisch@siemens.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