From: Florian Weimer <fw@deneb.enyo.de>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/17] pramfs: persistent and protected RAM filesystem
Date: Wed, 13 Jun 2012 20:57:53 +0200 [thread overview]
Message-ID: <87haufqbta.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <4FD46521.5070900@gmail.com> (Marco Stornelli's message of "Sun, 10 Jun 2012 11:13:05 +0200")
* Marco Stornelli:
> Pramfs documentation:
>
> http://pramfs.sourceforge.net
There doesn't seem to be an fsck. Is this correct?
next prev parent reply other threads:[~2012-06-13 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 9:13 [PATCH 00/17] pramfs: persistent and protected RAM filesystem Marco Stornelli
2012-06-10 11:20 ` Christian Stroetmann
2012-06-11 6:28 ` Marco Stornelli
2012-06-13 18:57 ` Florian Weimer [this message]
2012-06-14 6:17 ` Marco Stornelli
2012-06-16 6:57 ` Marco
-- strict thread matches above, loose matches on Subject: below --
2011-01-06 12:00 Marco Stornelli
2011-01-06 14:03 ` Peter Zijlstra
2011-01-06 16:26 ` Marco Stornelli
2011-01-06 16:58 ` Marco Stornelli
2011-01-06 18:22 ` Luck, Tony
2011-01-06 18:31 ` Marco Stornelli
2011-01-11 13:33 ` Pavel Machek
2011-01-11 19:01 ` Marco Stornelli
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=87haufqbta.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.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