From: "'Heinisch, Alexander' via isar-users" <isar-users@googlegroups.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"Prusty, Badrikesh" <badrikesh.prusty@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 1/3] installer: allow unattended mode to abort with configurable timeout
Date: Fri, 9 Jan 2026 11:06:43 +0000 [thread overview]
Message-ID: <adf0e6072e26c4172c6da20a1f99d755fc19087e.camel@siemens.com> (raw)
In-Reply-To: <399d79be-6052-46b0-9100-47a7d2a04a35@ilbers.de>
On Wed, 2026-01-07 at 14:41 +0200, Anton Mikanovich wrote:
> Applied patchset to next, thanks.
Sry for the late reply - holiday season :-)
>
> 28/12/2025 01:15, 'Badrikesh Prusty' via isar-users wrote:
> > Enable users to abort unattended installations before they start by
> > setting
> > INSTALLER_UNATTENDED_ABORT_ENABLE. Set an optional countdown
> > timeout with
> > INSTALLER_UNATTENDED_ABORT_TIMEOUT (default 5 seconds).
> >
> > Automatically append installer.unattended.abort.enable and
> > installer.unattended.abort.timeout=<timeout-in-seconds> to the
> > kernel
> > command line only when the feature is enabled.
> >
> > Abort unattended mode via keypress and switch to normal
> > installation mode,
"switch to normal installation mode" is the key message of this
feature. By INSTALLER_UNATTENDED_ABORT_* one is tempted to assume the
installation is aborted by this feature. Maybe we could rename those to
something more unambigious. e.g.
INSTALLER_UNATTENDED_MODESWITCH_{ENABLE,TIMEOUT}
?
> > notifying all consoles via a shared file
> > /tmp/attended_mode_trigger.
> >
> > Signed-off-by: Badrikesh Prusty <badrikesh.prusty@siemens.com>
--
Alexander Heinisch
Siemens AG
www.siemens.com
--
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/adf0e6072e26c4172c6da20a1f99d755fc19087e.camel%40siemens.com.
prev parent reply other threads:[~2026-01-09 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 23:15 'Badrikesh Prusty' via isar-users
2025-12-27 23:15 ` [PATCH v2 2/3] kas: support bundling multiple images via menu system 'Badrikesh Prusty' via isar-users
2025-12-27 23:15 ` [PATCH v2 3/3] kas: add menu option to abort unattended installation 'Badrikesh Prusty' via isar-users
2026-01-07 12:41 ` [PATCH v2 1/3] installer: allow unattended mode to abort with configurable timeout Anton Mikanovich
2026-01-09 11:06 ` 'Heinisch, Alexander' via isar-users [this message]
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=adf0e6072e26c4172c6da20a1f99d755fc19087e.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=amikan@ilbers.de \
--cc=badrikesh.prusty@siemens.com \
--cc=jan.kiszka@siemens.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