Dear Nishanth Menon, In message <1363992223-1628-1-git-send-email...@ti.com> you wrote: > For production systems it is better to use script images since > they are protected by checksums and carry valuable information > like name and timestamp. Also, you can't validate the content > passed to env import. > > But for development, it is easier to use the env import command and > plain text files instead of script-images.
Be careful here. There are some subtle, but important differences. With a script image, you are basically running standard commands, which includes certain tests and limitations. With "env import", you are just importing a set of environment settings, without further tests for permissions, etc. For example, think if data like your MAC address or board serial number are important to you, or if you are willing to have any user overwrite these with arbitrary data. 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: w...@denx.de I think that all right-thinking people in this country are sick and tired of being told that ordinary decent people are fed up in this country with being sick and tired. I'm certainly not. But I'm sick and tired of being told that I am. - Monty Python _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot