From: Sascha Hauer <s.hauer@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 4/4] defaultenv: Convert init script to C
Date: Mon, 29 Apr 2019 08:57:26 +0200 [thread overview]
Message-ID: <20190429065726.n2sezyznkd3ggjwi@pengutronix.de> (raw)
In-Reply-To: <20190426123705.payrtca5k5a3ilsj@pengutronix.de>
On Fri, Apr 26, 2019 at 02:37:05PM +0200, Roland Hieber wrote:
> Hi Sascha,
>
> small note: one might want to interrupt long-running processes during
> the init sequence, e.g. if an init script contains a "dhcp" call or does
> some NFS mount, but the board is currently not connected to the network.
Do you have a better example? You shouldn't run dhcp in an init script.
> Now it is no longer possible to interrupt such processes, even when
> global.autoboot_abort_key is set to anything else than "ctrl-c". Was
> this use case considered?
You can't abort the init sequence, but you can prevent it from being
executed at all. So when you are in such a situation, reset the board
and use ctrl-c or 'q' to not run the init sequence.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-04-29 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 10:26 [PATCH 1/4] Shell: Handle aborting loops better Sascha Hauer
2019-04-24 10:26 ` [PATCH 2/4] console: forbid ctrlc during startup Sascha Hauer
2019-04-24 10:26 ` [PATCH 3/4] console_countdown: Add pattern list Sascha Hauer
2019-04-24 10:26 ` [PATCH 4/4] defaultenv: Convert init script to C Sascha Hauer
2019-04-26 12:37 ` Roland Hieber
2019-04-29 6:57 ` Sascha Hauer [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=20190429065726.n2sezyznkd3ggjwi@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rhi@pengutronix.de \
/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