From: David Chow <davidchow@shaolinmicro.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Erez Zadok <ezk@cs.sunysb.edu>, Jeff Garzik <jgarzik@pobox.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: fistgen-0.1.1 released (linux-2.6 support)
Date: Sat, 31 Jul 2004 20:04:26 +0800 [thread overview]
Message-ID: <410B8ACA.6000902@shaolinmicro.com> (raw)
In-Reply-To: <20040731105423.GB23725@mail.shareable.org>
FiST is a stackable file system project, or you can say it is a file
filtering project. fistgen has is a template-based file system
development tool, and of couse runs at user space. But fs'es (C sources)
which generated by fistgen run entirely in the kernel. You can write
FiST file systems in C language without the need to bother kernel VFS
integration or internal understanding , simple use FiST language macros
to write file systems. For example, wrapfs (wrapper file system) is a
simply fs on fs file system which is used for testing and demonstration
the most basic stackable file system. Instead of mounting block devices,
you mount directories. You can even develop encryption and other useful
storage tools which requires fs-level integration but no need to hack or
write fs from scratch .
Personally, I suggests newbies of fs development to work with FiST to
get start on understanding VFS, as you can generate as many of fs'es as
you like, it is useful for fs-devel beginners to play around with.
regards,
David Chow
Jamie Lokier wrote:
>Erez Zadok wrote:
>
>
>>>where is the README or URL that describes what fistgen _is_?
>>>
>>>Your announcement is tailored such that only people who already know
>>>what fistgen (version 0.1.1) is would want to download it.
>>>
>>> Jeff
>>>
>>>
>>I'll say again...
>>
>> http://www.filesystems.org/
>>
>>
>
>I'm with Jeff.
>
>A one line description of what fistgen is in the email would still be helpful.
>
>I'm not going to waste 30 seconds faffing about starting a web
>browser, if you can't be bothered to include a simple brief
>description.
>
>Like many people, I read lots of mails, quickly. Yesterday it was
>nearly 2000. I spent an average time of 2 seconds on each. It's not
>possible to follow links to web sites on that time scale.
>
>If a quick scan says its interesting, I'll read more, maybe even break
>out the browser. Something as trivial as an informative subject line
>or a brief description makes all the difference.
>
>This is constructive criticism, the point being please include a brief
>description of what the thing is when making public announcements.
>It's not hard, and very useful.
>
>In the interests of generosity, I've just had a look at
>www.filesystems.org. From your email announcement, I had guessed that
>FiST and fistgen were some sort of userspace filesystem tool, like
>podfuk and a few others (including an NFS-based one I worked on). But
>now I see that it's not.
>
>To be honest, from reading the main page of the web site I still don't
>understand what FiST is useful for at the moment. As research it
>looks very promising. Btw, does it offer the facility for lazy
>copy-on-write trees that was discussed on linux-kernel a few months
>ago -- useful for jails and cloned compilation trees?
>
>
next prev parent reply other threads:[~2004-07-31 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 21:05 fistgen-0.1.1 released (linux-2.6 support) Erez Zadok
2004-07-30 21:31 ` Jeff Garzik
2004-07-30 21:41 ` Erez Zadok
2004-07-31 10:54 ` Jamie Lokier
2004-07-31 12:04 ` David Chow [this message]
2004-07-31 14:23 ` Erez Zadok
2004-07-31 14:41 ` Erez Zadok
2004-07-31 19:57 ` Jamie Lokier
2004-08-02 18:18 ` Erez Zadok
2004-08-02 19:08 ` Jamie Lokier
2004-08-02 20:34 ` Erez Zadok
2004-08-03 1:54 ` Shaya Potter
2004-08-03 12:42 ` Charles P. Wright
2004-08-03 15:05 ` Shaya Potter
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=410B8ACA.6000902@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=ezk@cs.sunysb.edu \
--cc=jamie@shareable.org \
--cc=jgarzik@pobox.com \
--cc=linux-fsdevel@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 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).