mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: B Gol <behnam_golds@yahoo.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: Re: how to persistently save config values
Date: Fri, 29 Sep 2017 09:27:05 +0000 (UTC)	[thread overview]
Message-ID: <2055913396.367969.1506677225722@mail.yahoo.com> (raw)
In-Reply-To: <1043852685.129432.1506673503086@mail.vodafone.de>

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@arcor.de> 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@lists.infradead.org

http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2017-09-29  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29  8:25 Giorgio Dal Molin
2017-09-29  9:02 ` Oleksij Rempel
2017-09-29  9:27 ` B Gol [this message]
2017-09-29 10:25   ` Giorgio Dal Molin
2017-09-29 11:35 ` Sascha Hauer
2017-09-29 12:31   ` Giorgio Dal Molin
2017-09-29 13:00     ` Sascha Hauer

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=2055913396.367969.1506677225722@mail.yahoo.com \
    --to=behnam_golds@yahoo.com \
    --cc=barebox@lists.infradead.org \
    /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