From: Johnny Hung <johnny.hacking@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Matthias Kaehlcke <matthias@kaehlcke.net>,
kernelnewbies <kernelnewbies@nl.linux.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
Date: Fri, 22 Jan 2010 11:01:45 +0800 [thread overview]
Message-ID: <cb9ecdfa1001211901u4384f6d4w68698aeb1cfc5cad@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1001200809550.32263@lnxricardw.se.axis.com>
2010/1/20 Ricard Wanderlof <ricard.wanderlof@axis.com>:
>
> On Wed, 20 Jan 2010, Johnny Hung wrote:
>
>>> i'd also recommend you to consider if you really need the
>>> ramdisk. when using a ram disk its entire content is loaded to the RAM
>>> occupying space, even if you don't use certain files (or part of
>>> them). other filesystems are more efficient in this aspect.
>>> if the main purpose is to have a read only rootfs, i'd suggest a look
>>> at squashfs.
>>
>> I consider to use ramdisk as rootfs because worry about wrong
>> operation in rootfs (is use jffs2 rootfs) and it will cause system
>> boot up failed.
>
> You have a point, however, you could do two things to help:
>
> a) Mount the root file system as read-only. That way you can never write to
> it, unless you remount it read-write. But you can still reflash that
> partition if you need to upgrade.
>
> b) Register the mtd partition holding the root file system as read-only.
> This is even more seecure as remounting the file system won't permit writes.
> However, it also means you can't write to it for upgrading. (I
> don't think the mtd core permits changing an already registered mtd
> partition from readonly to writable, but I could be wrong.)
>
>> Another query, does the syslogd/klogd log files also store in jffs2
>> rootfs? Write to jffs2 frequently will reduce flash life cycle.
>
> I think it is fairly common to have a combination of devices:
>
> / (root) is a readonly flash device (mtd partition)
> /etc is a writable flash device (mtd partition)
> /tmp and /var are ramdisks (tmpfs), so they are writable, but lost when
> power is cycled.
I think it's a good combination for my board. How do I sepcific the
/etc to another mtd part?
The busybox init will parse /etc/inittab after setup signal handler
and initializes console. I only
know to do it is to re-mount etc directory from another mtd to /etc.
Is it right?
Thank your help.
BRs, H. Johnny
>
> /Ricard
> --
> Ricard Wolf Wanderlöf ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden www.axis.com
> Phone +46 46 272 2016 Fax +46 46 13 61 30
>
next prev parent reply other threads:[~2010-01-22 3:01 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
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 [this message]
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=cb9ecdfa1001211901u4384f6d4w68698aeb1cfc5cad@mail.gmail.com \
--to=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 \
--cc=matthias@kaehlcke.net \
--cc=ricard.wanderlof@axis.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;
as well as URLs for NNTP newsgroup(s).