All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to make the Buildroot embedded linux file system persistence?
Date: Tue, 16 Sep 2014 11:23:30 +0200	[thread overview]
Message-ID: <20140916112330.40118c9d@free-electrons.com> (raw)
In-Reply-To: <5417F84B.8050705@yahoo.com>

Dear Amir,

On Tue, 16 Sep 2014 13:13:55 +0430, Amir wrote:

> I have built an embedded linux using buildroot. after generating 
> rootfs.tar file system, I have tested the embedded linux and figured out 
> that every change I made to the linux is not taking place after reboot.
> 
> my question is: how to enable buildroot linux to have a persistence file 
> system and can save changes?
> 
> I have generated: rootfs.tar , rootfs.cpio , bzImage of kernel.

Which one are you using? If you've generated a rootfs.cpio, maybe
you've enabled the initramfs option, which as its name suggest is a
filesystem in RAM, which explains why your changes disappear after a
reboot.

Use a filesystem stored on persistent storage, such as a SD card, eMMC,
NAND flash or USB key.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-09-16  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  8:43 [Buildroot] how to make the Buildroot embedded linux file system persistence? Amir
2014-09-16  9:23 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-16  8:48 Amir Amir

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=20140916112330.40118c9d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.