Skip to main content.
Navigation:
DENX
>
U-Boot
>
TaskSetEnvironmentDefaults
Translations:
Edit
|
Attach
|
Raw
|
Ref-By
|
Printable
|
More
U-Boot
Sections of this site:
DENX Home
|
DULG
|
ELDK-5
|
Know
|
Training
|
U-Boot
|
U-Bootdoc
Topics
U-Boot Home
Documentation
Source Code
The Custodians
Custodian Repositories
Development Process
Release Cycle
Coding Style
Patches
Tasks
Contacts
Changes
Index
List of pages in U-Boot
Search
---+ Set Environment to Default Values ---++ Rationale: There are many situations where it is desirable to reset the environment variables to default values (like the built-in defautl settings). After some discussion we agreed that a command name like "clearenv" or "scrubenv" or similar (which doesn't require any arguments) might be too dangerous for the inexperienced user who 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. ---++ Suggested Implementation: The idea is to call the new command "environment" (or short "env"); usage would be then: <verbatim> => env clear </verbatim> to clear the environment (except read-only variables); thsi also allows for pretty useful additional functionality like this: <verbatim> => env default </verbatim> to reset the environment to the (compiled in) default settings. A more fancy implementation would allow for <verbatim> => env default [name ...] </verbatim> to reset a list of specific variables to their default values. %T% Note: This feature would be especially interesting in combination with the [[TaskEnvironmentGroups]["Group Environment Variables"]] feature. One might even consider something like <verbatim> => env clear all </verbatim> to blow away the whole env, including the read-only variables. [Disadvantage: this requires that "all" is a reserve variable name.] -- Main.WolfgangDenk - 12 Oct 2008