linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Johnny Hung <johnny.hacking@gmail.com>
Cc: linux-embedded@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-mtd@lists.infradead.org,
	kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
Date: Tue, 19 Jan 2010 10:50:24 +0100	[thread overview]
Message-ID: <20100119095024.GD16182@darwin> (raw)
In-Reply-To: <cb9ecdfa1001190120r593f7799sf566df5a855b8a54@mail.gmail.com>

El Tue, Jan 19, 2010 at 05:20:53PM +0800 Johnny Hung ha dit:

> I have build an embedded Linux system and rootfs is a ramdisk. Ramdisk
> rootfs resides in memory so modify files is non-effective after a
> reboot. Some directories in rootfs, like /etc, /usr, ... are contain
> many application configuration files and I want to mount it to jffs2
> flash filesysyem so it will take effect after a reboot. Is it
> possible?

yes, this is possible

> I know the flash has write times limited so the log files
> (syslogd/klogd) should not store in flash. In general, how to deploy
> root file system for embedded linux with flash storage?

- add jffs2 support to your kernel
- create your image using mkfs.jffs2 from mtd-utils
- flash the image
- specify the rootfs partition and type in the bootargs of the kernel

for further information i recommend the lecture of
http://free-electrons.com/doc/flash-filesystems.pdf

depending on your requirements/size of the rootfs partitions UBIFS
might be an option to consider

-- 
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

      El trabajo es el refugio de los que no tienen nada que hacer
                            (Oscar Wilde)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ


  reply	other threads:[~2010-01-19  9:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  9:20 mount ramdisk rootfs /etc directory to jffs2 filesystem Johnny Hung
2010-01-19  9:50 ` Matthias Kaehlcke [this message]
2010-01-19 10:13   ` Johnny Hung
2010-01-19 10:20     ` Matthias Kaehlcke
2010-01-19 12:03       ` Johnny Hung
2010-01-19 13:17         ` Ricard Wanderlof
2010-01-19 14:06           ` Matthias Kaehlcke
2010-01-20  2:32             ` Johnny Hung
2010-01-20  7:12               ` Matthias Kaehlcke
2010-01-20  7:15               ` Ricard Wanderlof
2010-01-20  7:17                 ` Matthias Kaehlcke
2010-01-22  3:01                 ` Johnny Hung
2010-01-20  7:57               ` Marco Stornelli
2010-01-20 10:21                 ` Matthias Kaehlcke
2010-01-20 11:54                   ` Marco Stornelli
2010-01-22  3:07                 ` Johnny Hung
2010-01-22  8:14                   ` Marco Stornelli
2010-01-25  4:09                     ` Johnny Hung
2010-01-25  8:27                       ` Chris Simmonds
2010-01-25  8:43                         ` Johnny Hung

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=20100119095024.GD16182@darwin \
    --to=matthias@kaehlcke.net \
    --cc=johnny.hacking@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).