From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <ahmad@a3f.at>
Subject: [PATCH 2/2] sandbox: state: reword warning about initial state errors
Date: Sun, 4 Apr 2021 13:18:31 +0200 [thread overview]
Message-ID: <20210404111831.592821-2-ahmad@a3f.at> (raw)
In-Reply-To: <20210404111831.592821-1-ahmad@a3f.at>
The message didn't explicitly say it is expected behavior to not find
barebox-state on startup. Reword the message to make this clearer.
Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
---
arch/sandbox/board/env/init/state | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/sandbox/board/env/init/state b/arch/sandbox/board/env/init/state
index 0b8e40409f97..b8a2b42a53ea 100644
--- a/arch/sandbox/board/env/init/state
+++ b/arch/sandbox/board/env/init/state
@@ -5,8 +5,9 @@ fi
source /env/data/ansi-colors
echo -e $CYAN
-echo "******************************************************************"
-echo "*** Inconsistent barebox state buckets detected on first boot ***"
-echo "*** barebox will repair them on next shutdown ***"
-echo "*****************************************************************"
+echo "*******************************************************"
+echo "*** Inconsistent barebox state buckets detected ***"
+echo "*** This is normal for a first boot ***"
+echo "*** barebox will repair them on next poweroff/reset ***"
+echo "*******************************************************"
echo -e -n $NC
--
2.30.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-04-04 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 11:18 [PATCH 1/2] sandbox: env: set nv.autoboot=abort to drop to shell Ahmad Fatoum
2021-04-04 11:18 ` Ahmad Fatoum [this message]
2021-04-07 10:59 ` Uwe Kleine-König
2021-04-13 7:43 ` Sascha Hauer
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=20210404111831.592821-2-ahmad@a3f.at \
--to=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
/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