From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: Barebox List <barebox@lists.infradead.org>,
B Gol <behnam_golds@yahoo.com>
Subject: Re: how to persistently save config values
Date: Fri, 29 Sep 2017 12:25:18 +0200 (CEST) [thread overview]
Message-ID: <1391726154.111771.1506680718837@mail.vodafone.de> (raw)
In-Reply-To: <2055913396.367969.1506677225722@mail.yahoo.com>
Hi,
thanks for your answer but I think this is not really what I need.
I need a way to configure and change the variable values at runtime.
The envfs with the loadenv and saveenv commands is OK, what I'm missing
is a way to 'edit' the environment before I can save it back to the persistent
storage.
I'm thinking about adding some options to printenv to let it dump the variables
given on its command line to a file.
giorgio
> On September 29, 2017 at 11:27 AM B Gol wrote:
>
> 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 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
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-09-29 10:25 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
2017-09-29 10:25 ` Giorgio Dal Molin [this message]
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=1391726154.111771.1506680718837@mail.vodafone.de \
--to=giorgio.nicole@arcor.de \
--cc=barebox@lists.infradead.org \
--cc=behnam_golds@yahoo.com \
/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