Dear Alexander, In message <53de658f.5010...@ahsoftware.de> you wrote: > > Just to clarify: I see uEnv.txt (which only was possible through your > env import implementation) as a read-only configuration file for u-boot,
This is just one of the many possible usages. > And I don't think all the necessary stuff to save a file in all the > possible filesystems should end up in u-boot. Modifying filesystems is > dangerous. Thius has nothing to do with exporting an environment. The export operation and the writing to the file system are two separate steps. If a file system driver contains write support or not depends on the file system code. For the environment it does not matter. If we have write support, we just use it. > So from a u-boot point of view uEnv.txt is a read-only mechanism and I'm > happy with it as such. As mentioned, this is but one usage. I think that "env import" / "env export" should be kept symmetric. 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 Any technology distinguishable from magic is insufficiently advanced. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
