From: Chris Simmonds <chris@2net.co.uk>
To: Johnny Hung <johnny.hacking@gmail.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>,
Matthias Kaehlcke <matthias@kaehlcke.net>,
Ricard Wanderlof <ricard.wanderlof@axis.com>,
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: Mon, 25 Jan 2010 08:27:58 +0000 [thread overview]
Message-ID: <4B5D560E.2020901@2net.co.uk> (raw)
In-Reply-To: <cb9ecdfa1001242009x30eabcd3gbd0bb1d8a931199e@mail.gmail.com>
Johnny Hung wrote:
> 2010/1/22 Marco Stornelli <marco.stornelli@gmail.com>:
>> 2010/1/22 Johnny Hung <johnny.hacking@gmail.com>:
>>> 2010/1/20 Marco Stornelli <marco.stornelli@gmail.com>:
>>>> 2010/1/20 Johnny Hung <johnny.hacking@gmail.com>:
>>>>> 2010/1/19 Matthias Kaehlcke <matthias@kaehlcke.net>:
>>>>>> El Tue, Jan 19, 2010 at 02:17:22PM +0100 Ricard Wanderlof ha dit:
>>>>>>
>>>>> 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.
>>>>> Another query, does the syslogd/klogd log files also store in jffs2
>>>>> rootfs? Write to jffs2 frequently will reduce flash life cycle.
>>>>>
>>>>> BRs, H. Johnny
>>>>>> --
>>> It seems there are a lot of file-systems I have to study :P. The same
>>> question is
>>> how to split my rootfs? Re-mount /etc, /var to another file-sysyem mtd part when
>>> system boot up?
>>>
> Yes, I know. So if I want set etc directoyr to /dev/mtd5 not in rootfs
> /, I need to add "/dev/mtdblock5 /etc jffs2 defaults
> 0 0" in /etc/fstab file but rootfs doesn't contain /etc
> directory because /etc directoyr is store in /dev/mtdblock5.
> Do you know what I mean? The kernel execute /sbin/init after mount
> rootfs and /sbin/init is link to busybox, busybox will read
> /etc/inittab file to initial. The problem is coming, how busybox to
> read /etc in rootfs before mount /dev/mtdblock5 to /etc? There is no
> program to mount /dev/mtdblock5 to /etc before busybox init execute.
>
> I think I must mistake some concept, please give me a hint.
> Thank you
> BRs, H. Johnny
>
You have two /etc directories: one in the the read-only root file system
and one in the jffs2 fs. In the root fs you have /etc/fstab,
/etc/inittab and any scripts it may call. The init program will mount
/dev/mtdblock5 over the top of the /etc that is in the rootfs, so giving
you the read/write version of /etc. Any files open in the old /etc -
e.g. /etc/inittab - will continue to be open, but any new files opened
in /etc will use the read/write version in jffs2. You can also do some
interesting things with symbolic links... This technique works. I have
used it in several projects.
--
Chris Simmonds 2net Limited
chris@2net.co.uk http://www.2net.co.uk/
next prev parent reply other threads:[~2010-01-25 8:27 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
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 [this message]
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=4B5D560E.2020901@2net.co.uk \
--to=chris@2net.co.uk \
--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 \
--cc=marco.stornelli@gmail.com \
--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).