mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Richter <Alexander.Richter@ATSonline.de>
To: Jean-Christophe BEGUE <begue.jc@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Programatically write in a file in the environnent with a hush command
Date: Wed, 27 May 2015 06:08:49 +0000	[thread overview]
Message-ID: <D72B6FFF-645F-41CC-9B99-2ACE13B05BFC@atsonline.de> (raw)
In-Reply-To: <CABP==CLFeG59X3OyMxJrxTzWDg-Xm8dURb-k-JXu3as+pY5mKA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]

Hello,
> Am 26.05.2015 um 17:42 schrieb Jean-Christophe BEGUE <begue.jc@gmail.com>:
> 
> Hello,
> 
> I'm trying to pass a value from Barebox to the operating system, using
> the usreland command bareboxenv -l.
> 
> My problem is : How should I write that status from my hush barebox script?
> 
> echo $mystatus > /env/data/my_status_file
You can use the command nv to create non volatile shell variables. Don’t forget to save the Environment.
> 
> The above command doesn't work as '>' is not implemented.
> 
> I've the feeling that I'm missing something?
> 
To access the new variable (/env/nv/foo.bar) from userspace, you can use the „bareboxenv“ tool

Alexander Richter

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

  reply	other threads:[~2015-05-27  6:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 15:41 Jean-Christophe BEGUE
2015-05-27  6:08 ` Alexander Richter [this message]
2015-05-27  6:24   ` Alexander Richter
2015-05-27  6:53 ` Sascha Hauer
2015-05-27 13:52   ` Jean-Christophe BEGUE

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=D72B6FFF-645F-41CC-9B99-2ACE13B05BFC@atsonline.de \
    --to=alexander.richter@atsonline.de \
    --cc=barebox@lists.infradead.org \
    --cc=begue.jc@gmail.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