mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: how to persistently save config values
Date: Fri, 29 Sep 2017 14:31:40 +0200 (CEST)	[thread overview]
Message-ID: <1240553302.113348.1506688301119@mail.vodafone.de> (raw)
In-Reply-To: <20170929113543.p2unhzcdk4knwpvx@pengutronix.de>

Hi Sascha,

thank you for the answer.

I just experimented a bit with the environment and the nv vars
and I think I'll go this way.

I was a bit surprised by the saveenv command though: my understanding
of the (default) environment was that it was a read only blob
hardcoded in the barebox image; I thought if I want some new/dynamic
env content to be saved for the next reboot I have to explicitly provide
a storage disk/cf/mtd partition to the saveenv and then to the loadenv.
Instead, just saying 'saveenv' saves the contents of '/env' 'somewhere'
from where it can be restored on next reboot (very good!).

Together with the nv vars and the 'nv.dev.' prefix this just does the
trick for me.

Thank you.

giorgio

> On September 29, 2017 at 1:35 PM Sascha Hauer wrote:
> 
> On Fri, Sep 29, 2017 at 10:25:03AM +0200, 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
> 
> (should be eth0.serverip)
> > ...
> > 
> > Then I saved the file with 'saveenv' and restored it back with 'loadenv'.
> 
> Normally you should edit /env/network/eth0 to change the network config.
> 
> Also there is the possibility to create a nv variable that automatically
> mirrors to the device variable. In this case it would be
> nv.dev.eth0.ipaddr and nv.dev.eth0.serverip. This doesn't work with dhcp
> though.
> 
> Sascha
> 
> -- 
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
> 
> _______________________________________________
> 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

  reply	other threads:[~2017-09-29 12:32 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
2017-09-29 11:35 ` Sascha Hauer
2017-09-29 12:31   ` Giorgio Dal Molin [this message]
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=1240553302.113348.1506688301119@mail.vodafone.de \
    --to=giorgio.nicole@arcor.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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