From: "Trevor Woerner" <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [master-next][PATCH 3/3] sysvinit/rc: improved progress messages
Date: Wed, 23 Dec 2020 12:06:21 -0500 [thread overview]
Message-ID: <20201223170621.35727-3-twoerner@gmail.com> (raw)
In-Reply-To: <20201223170621.35727-1-twoerner@gmail.com>
I noticed that the progress text messages were always a system behind; i.e. if
the current boot script was "networking" the message would indicate the
previous script and would say "networking" next.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
meta/recipes-core/sysvinit/sysvinit/rc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit/rc b/meta/recipes-core/sysvinit/sysvinit/rc
index 61946e56eb..15ff660965 100755
--- a/meta/recipes-core/sysvinit/sysvinit/rc
+++ b/meta/recipes-core/sysvinit/sysvinit/rc
@@ -28,7 +28,6 @@ startup_progress() {
fi
#echo "PROGRESS is $progress $runlevel $first_step + ($step of $num_steps) $step_change $progress_size"
if type psplash-write >/dev/null 2>&1; then
- psplash-write "MSG $(basename $1 .sh | cut -c 4-)" || true
psplash-write "PROGRESS $progress" || true
fi
}
@@ -55,7 +54,7 @@ startup() {
"$@"
;;
esac
- startup_progress "$1"
+ startup_progress
}
# Ignore CTRL-C only in this shell, so we can interrupt subprocesses.
@@ -161,6 +160,7 @@ startup() {
#
[ -f $previous_start ] && [ ! -f $stop ] && continue
fi
+ psplash-write "MSG $(basename $i .sh | cut -c 4-)"
case "$runlevel" in
0|6)
startup $i stop
--
2.30.0.rc0
prev parent reply other threads:[~2020-12-23 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 17:06 [master-next][PATCH 1/3] PSPLASH_FIFO_DIR: refactor Trevor Woerner
2020-12-23 17:06 ` [master-next][PATCH 2/3] psplash: work on first boot (sysvinit) Trevor Woerner
2020-12-23 18:00 ` [OE-core] " Richard Purdie
2020-12-23 21:50 ` Trevor Woerner
2020-12-23 22:06 ` Richard Purdie
2020-12-23 22:35 ` Trevor Woerner
2020-12-23 22:39 ` Richard Purdie
2020-12-23 22:41 ` Trevor Woerner
2020-12-23 22:43 ` Richard Purdie
2020-12-23 22:55 ` Trevor Woerner
2020-12-23 17:06 ` Trevor Woerner [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=20201223170621.35727-3-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.