I just put all the variables in the source directory and then compile again. Look inside the following dir and its sub dirs, you'll see all the default(hard coded) variables inside it: /source-path/barebox-yyyy.mm.d/defaultenv/ Simply make a text file inside a sub dir.The file name would be your variable name and the string inside the file would be the value for that particular variable. On Friday, September 29, 2017 12:20 PM, Giorgio Dal Molin <giorgio.nicole@xxxxxxxx> wrote: Hi, I'm working on a new project with an embedded system based on a standard intel PC. I already have a barebox.efi running on the system; my problem is now how to permanently save some variables so that, on restart, they can be automatically restored by my '/env/bin/init' script. The variables I mean are for example 'eth0.ipaddr' or 'eth0.serveraddr'. A solution I used in the past was a custom 'env_dump' command that generated a config text file like: eth0.ipaddr=10.0.0.15 eth0.serveraddr=10.0.0.1 ... Then I saved the file with 'saveenv' and restored it back with 'loadenv'. Is there a better way to solve this problem ? I don't like very much having to write 'custom commands' myself. I had a look at the state framework but it seems kinda overkill for what I need. giorgio _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
