mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sohaib Mohamed <sohaib.amhmd@gmail.com>
To: barebox@lists.infradead.org
Cc: Sohaib Mohamed <sohaib.amhmd@gmail.com>
Subject: [PATCH] Documentation: defaultenv-2: Document C-based init script
Date: Mon, 10 Nov 2025 21:55:31 +0100	[thread overview]
Message-ID: <20251110-fixup_docs-v1-1-1acaf5593d26@gmail.com> (raw)

Add a note to clarify that the default init script is now implemented in
C rather than as a shell script.

Fixes: 90df2a955e3c ("defaultenv: Convert init script to C")
Signed-off-by: Sohaib Mohamed <sohaib.amhmd@gmail.com>
---
 Documentation/user/defaultenv-2.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Documentation/user/defaultenv-2.rst b/Documentation/user/defaultenv-2.rst
index 3715fd770d9d89d52172bcc1e7564d871977aa30..e5cb4a51bfad47e5022fb719d513a201519334e5 100644
--- a/Documentation/user/defaultenv-2.rst
+++ b/Documentation/user/defaultenv-2.rst
@@ -50,9 +50,10 @@ and their respective included directories in ``defaultenv/Makefile``:
 /env/bin/init
 -------------
 
-This script is executed by the barebox startup code after initialization.
-In defaultenv-2, this script will define and set a number of global
-variables, followed by sourcing all of the scripts in ``/env/init/`` with:
+The default init script is now written in C. However, you can still define
+your own ``/env/bin/init`` script and it will take precedence over the
+built-in C implementation.
+Example for simple init script:
 
 .. code-block:: sh
 

---
base-commit: 0633a4db9d2351234b565b55978ce068b387eb2d
change-id: 20251110-fixup_docs-0566a0084735

Best regards,
-- 
Sohaib Mohamed <sohaib.amhmd@gmail.com>




                 reply	other threads:[~2025-11-10 20:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251110-fixup_docs-v1-1-1acaf5593d26@gmail.com \
    --to=sohaib.amhmd@gmail.com \
    --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