From: Marco <marco.stornelli@coritel.it>
To: Jacob Avraham <jacob@imaginecommunications.com>
Cc: "Leisner, Martin" <Martin.Leisner@Xerox.com>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: ramfs/tmpfs for application partition
Date: Sat, 17 Jan 2009 16:55:18 +0100 [thread overview]
Message-ID: <4971FF66.6080709@coritel.it> (raw)
In-Reply-To: <FF584854D6FFE547AB2F7515A798AC3A045716A1F8@venus.imagineil.tv>
Hi Jacob,
only another idea, why do you think to use a persistant ram filesystem
(like pramfs) mounted on /my/application/partition? If you use a simple
ram you can repopulate after a power off/on the directory with a simple
untar of the archive. In this way you haven't to repopulate the
filesystem after each reboot. What do you think about it? Could it be a
solution?
Marco
Jacob Avraham ha scritto:
>> Not sure I fully understand....
>>
>> You basically want two blobs -- the initramfs and the application?
>>
> Yes, I want to keep on the flash a stable, rarely changed, OS image, which is in initramfs
> format, and another application image, which is changing frequently.
>
>> You can expand the initramfs by copying to it...so you mount the
>> application and run a script to copy it to initramfs before running it.
>>
> When you say 'you mount the application' it means that the application
> image on the flash has to be in some filesystem format, right? Like cramfs?
> On the other hand, if I want the application directory tree to reside
> in memory (and handle application persistency needs via the JFFS2 partition),
> maybe all I need is to keep a compressed tar image of the application on the flash,
> and untar it into /my/application/partition, which will be in initramfs?
> So I don't need to create another tmpfs filesystem as suggested in another post?
> Is there a better way to handle this?
>
>> marty
>>
>>> Hi,
>>>
>>> I have a system with 128M RAM and a flash partitioned so that 10M
>> is
>>> dedicated to initramfs image,
>>> 6M to application partition. And another 6M for JFFS2.
>>> As I have plenty of RAM, I'd like to have my application directory
>>> mounted on RAM, from a pre-populated
>>> filesystem that resides in the 6M application partition.
>>> So basically I want to use the same mechanism as initramfs, but
>> mounted
>>> on /my/app/partition instead of root.
>>> Does it make sense? How do I go about and do that?
>>>
>>>
>>> Jacob Avraham
>>>
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
> ************************************************************************************
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-01-17 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 16:43 ramfs/tmpfs for application partition Jacob Avraham
2009-01-15 16:55 ` Leisner, Martin
2009-01-17 9:39 ` Jacob Avraham
2009-01-17 15:55 ` Marco [this message]
2009-01-15 17:04 ` Mike Frysinger
[not found] ` <4972E3F4.1020508@codefidence.com>
[not found] ` <FF584854D6FFE547AB2F7515A798AC3A045716A316@venus.imagineil.tv>
2009-01-18 13:55 ` Gilad Ben-Yossef
2009-03-09 6:00 ` Aras Vaichas
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=4971FF66.6080709@coritel.it \
--to=marco.stornelli@coritel.it \
--cc=Martin.Leisner@Xerox.com \
--cc=jacob@imaginecommunications.com \
--cc=linux-embedded@vger.kernel.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 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.