From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] omap4: use plain text env file instead boot scripts
Date: Tue, 25 Dec 2012 21:00:32 +0100 [thread overview]
Message-ID: <20121225200032.91E7C200F85@gemini.denx.de> (raw)
In-Reply-To: <1356444923-16737-1-git-send-email-javier.martinez@collabora.co.uk>
Dear Javier Martinez Canillas,
In message <1356444923-16737-1-git-send-email-javier.martinez@collabora.co.uk> you wrote:
> Based on commit cf073e49bc3502be1b48a0e3faf0cde9edbb89db for beagleboard
>
> Using the new env import command it is possible to use plain text files instead
> of script-images. Plain text files are much easier to handle.
Are you sure you want to do this in a production environment? The
ease of use may be helpful during development, but please note that
there is no validation of the content passed to env import in any way
- and feeding it crap you can even crash the system - not to mention
from the problems that can result from corrupted environment settings.
Script images are checksum protected, which appears to be a
significant advantage to me - also, they carry information like name
and timestamp, which in production environments are often very helpful
to diagnose problems (like asking your customers: which exact version
of the environment script are you loading?).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Every living thing wants to survive.
-- Spock, "The Ultimate Computer", stardate 4731.3
next prev parent reply other threads:[~2012-12-25 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 14:15 [U-Boot] [PATCH 1/1] omap4: use plain text env file instead boot scripts Javier Martinez Canillas
2012-12-25 20:00 ` Wolfgang Denk [this message]
2012-12-26 3:49 ` Javier Martinez Canillas
2012-12-26 11:40 ` Wolfgang Denk
2012-12-26 11:54 ` Javier Martinez Canillas
2013-01-02 14:39 ` Tom Rini
2013-01-02 22:05 ` Javier Martinez Canillas
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=20121225200032.91E7C200F85@gemini.denx.de \
--to=wd@denx.de \
--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 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.