From: stefano babic <stefano.babic@babic.homelinux.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Handle environment variables like commands
Date: Wed, 15 Oct 2008 14:01:59 +0200 [thread overview]
Message-ID: <48F5DBB7.4070307@babic.homelinux.org> (raw)
In-Reply-To: <20081015110156.306B581C99CD@gemini.denx.de>
Wolfgang Denk wrote:
> Good catch. Yes, this must be prevented. Any variable named "builtin"
> must be ignored here - i. e. we should issue an erro when someone
> tries a "setenv", and ignore this variable explicitly (just in case
> someone sneaks this into the default environment, or uses un-fixed
> Linux tools to create such a variable).
I know, I wanted to know which is the preferred method to avoid that.
One way is to avoid to set the variable, as you suggest.
The other way is never execute a variable with the name "builtin" in the
command interpreter: "setenv builtin <something>" remains possible but
"builtin <command>" calls always the U-Boot commands.
Best regards,
Stefano Babic
--
stefano <stefano.babic@babic.homelinux.org>
GPG Key: 0x55814DDE
Fingerprint 4E85 2A66 4CBA 497A 2A7B D3BF 5973 F216 5581 4DDE
next prev parent reply other threads:[~2008-10-15 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 10:09 [U-Boot] [PATCH] Handle environment variables like commands Stefano Babic
2008-10-15 10:45 ` Petri Lehtinen
2008-10-15 11:01 ` Wolfgang Denk
2008-10-15 12:01 ` stefano babic [this message]
2008-10-15 12:25 ` Wolfgang Denk
2008-10-15 10:57 ` Wolfgang Denk
2008-10-15 11:56 ` stefano babic
2008-10-15 12:26 ` Wolfgang Denk
2008-10-15 12:09 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2008-10-15 13:56 Stefano Babic
2008-10-19 12:05 ` Wolfgang Denk
2008-10-20 7:50 ` stefano babic
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=48F5DBB7.4070307@babic.homelinux.org \
--to=stefano.babic@babic.homelinux.org \
--cc=u-boot@lists.denx.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