From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Delete all env vars except read onlys
Date: Wed, 20 Feb 2008 22:30:02 +0100 [thread overview]
Message-ID: <00ca01c8740c$5a7b9fe0$c3031c0a@atmel.com> (raw)
In-Reply-To: 200802202217.58210.matthias.fuchs@esd-electronics.com
>> >
>> > After a longish discussion with Detlev we came up with a new
>> > proposal, which hopefully is acceptable to all. We agreed that a
>> > command name like "clearenv" or "scrubenv" or similar (which doesn't
>> > require any arguments) might be too dangerous for the unexperienced
>> > user why randomly types commands "just to see what happens". For
>> > example, even if you type "erase" it will not do any damage because
>> > arguments are missing - but "erase all" will blow away most of your
>> > flash content without asking.
>> >
>> > So the idea is to call the new command "environment" (or short "env");
>> > usage would be then:
>> >
>> > => env clear
>> >
>> > to clear the envrionment (except read-only variables); thsi also
>> > allows for pretty useful additional functionality like this:
>> >
>> > => env default
>> >
>> > to reset the environment to the (compiled in) default settings.
>> >
I see this as essential and have implemented this in my own u-boot.
I call it "defenv".
It is a little different though, It will reinitialize the predefined environment
variables to default settings but will not touch the other.
If "env default" is implemented the same way, then you could get a
100% clean environment by:
env clear ; env default
What will "env" do without parameters?
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-02-20 21:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 8:44 [U-Boot-Users] Delete all env vars except read onlys Matthias Fuchs
2008-02-12 14:49 ` Stefan Roese
2008-02-12 22:55 ` Wolfgang Denk
2008-02-13 8:21 ` Matthias Fuchs
2008-02-13 8:56 ` Stefan Roese
2008-02-13 9:18 ` Matthias Fuchs
2008-02-13 10:02 ` Markus Klotzbücher
2008-02-13 10:13 ` Stefan Roese
2008-02-13 10:33 ` Markus Klotzbücher
2008-02-13 11:13 ` Detlev Zundel
2008-02-13 12:55 ` Markus Klotzbücher
2008-02-13 12:58 ` Stefan Roese
2008-02-13 22:43 ` Wolfgang Denk
2008-02-13 22:49 ` Scott Wood
2008-02-13 23:03 ` Wolfgang Denk
2008-02-13 23:04 ` Scott Wood
2008-02-13 23:11 ` Wolfgang Denk
2008-02-15 15:37 ` Detlev Zundel
2008-02-13 22:40 ` Wolfgang Denk
2008-02-13 22:50 ` Scott Wood
2008-02-13 23:05 ` Wolfgang Denk
2008-02-14 5:20 ` Stefan Roese
2008-02-14 7:44 ` Wolfgang Denk
2008-02-15 15:52 ` Detlev Zundel
2008-02-15 16:11 ` Wolfgang Denk
2008-02-15 16:40 ` Wolfgang Denk
2008-02-15 17:12 ` Markus Klotzbücher
2008-02-15 20:27 ` Jean-Christophe PLAGNIOL-VILLARD
2008-02-20 21:17 ` Matthias Fuchs
2008-02-20 21:30 ` Ulf Samuelsson [this message]
2008-02-21 0:04 ` Wolfgang Denk
2008-02-22 12:00 ` Wolfgang Denk
2008-02-18 9:41 ` Martin Krause
2008-03-25 21:10 ` Wolfgang Denk
2008-02-13 22:38 ` Wolfgang Denk
2008-02-12 22:38 ` Wolfgang Denk
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='00ca01c8740c$5a7b9fe0$c3031c0a@atmel.com' \
--to=ulf@atmel.com \
--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