mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Frank Wunderlich <>
Subject: barebox extending boot-scripts
Date: Wed, 5 Jan 2022 16:20:43 +0100	[thread overview]
Message-ID: <trinity-236a89db-cfb0-4d29-bf25-44dc71d5d143-1641396043420@3c-app-gmx-bs58> (raw)


i'm making my first steps and try to add more boot-scripts (to land in /env/boot)

i added a scipt in


and set

DEFAULT_ENVIRONMENT_PATH [=arch/arm/boards/rockchip-rk3568-evb/defaultenv]

but if i boot the board /env/boot only contains the 2 default scripts

barebox@Rockchip RK3568 EVB:/ ls /env/boot/
bnet    net

so maybe the dir/config-option i used is for defining variables only right? should this point to an directory or a file?

i see this file which looks like the source of it


I've put them there and they appear, but this is not board specific, so if i later want to upstream one this is maybe not the right place.


seems to be a menu entry, but have not yet figured out how i can define one to add my scripts too

have not found anything for it in the documentation yet

btw. is there a way to use ls with wildcard without printing the path?

ls /mnt/sd.1/extlinux/
Image_5.16            Image_5.16-next.gz    Image_5.16.gz

ls /mnt/sd.1/extlinux/Image*

i want to list only files matching Image*, but without path....number of columns does not matter

regards Frank

barebox mailing list

             reply	other threads:[~2022-01-05 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 15:20 Frank Wunderlich [this message]
2022-01-05 16:07 ` Ahmad Fatoum
2022-01-05 18:13   ` Aw: " Frank Wunderlich
2022-01-06  8:08     ` Sascha Hauer
2022-01-06 12:41       ` Aw: " Frank Wunderlich
2022-01-07 13:07         ` Sascha Hauer
2022-01-07 16:42           ` Aw: " Frank Wunderlich
2022-01-10  9:42             ` Sascha Hauer
2022-01-15 13:47               ` Aw: " Frank Wunderlich
2022-01-17  8:59                 ` Sascha Hauer
2022-01-29 10:40       ` Aw: " Frank Wunderlich
2022-01-31 11:03         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-236a89db-cfb0-4d29-bf25-44dc71d5d143-1641396043420@3c-app-gmx-bs58 \ \ \

* 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