From: "Maciej Sołtysiak" <pysiak.satriani@wp.pl>
To: reiserfs-list@namesys.com, reiserfs-list@namesys.com
Subject: Re: future r4 maintenance question
Date: Sat, 22 Jul 2006 23:26:28 +0200 [thread overview]
Message-ID: <1368904392.20060722232628@wp.pl> (raw)
In-Reply-To: <44C287B0.2060907@slaphack.com>
Hello David,
Saturday, July 22, 2006, 10:16:48 PM, you wrote:
> There's another note to kernel developers -- if Reiser5, 6, and 7 are
> implemented as suites of plugins on top of Reiser4, then the Reiser4
> code will be maintained for a very long time. Kind of like ext2 vs
> ext3, only moreso -- a Reiser5 FS may well be a Reiser4 FS mounted with
> additional mount options.
This the exact information I was hoping to get. I think it's important
for people to realize it. Thanks.
> # Make a playlist of all files by Hendrix, mp3 or otherwise:
> for i in `find`; do
> if [ `cat "$i/.../song-info/artist"` == 'Jimi Hendrix' ]; then
> echo "../$i" >> playlists/hendrix.m3u;
> fi;
> done
I've read about this :-)
Are plugins for such a thing entirely/mostly kernel-space?
I mean, the power of FUSE is being in user-space...
If there was an API to write a id3 plugin it propably be more
beneficial.
Well, it's plugins. If someone writes a kernelspace id3 plugin,
someone else could write a kernelspace plugin with a userspace
supplied configuration.
--
Best regards,
Maciej
next prev parent reply other threads:[~2006-07-22 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 15:32 future r4 maintenance question Pysiak Satriani
2006-07-22 18:03 ` Hans Reiser
2006-07-22 19:51 ` Maciej Sołtysiak
2006-07-22 20:16 ` David Masover
2006-07-22 21:26 ` Maciej Sołtysiak [this message]
2006-07-23 6:23 ` Hans Reiser
2006-07-23 6:07 ` Hans Reiser
2006-07-22 18:53 ` Mike Benoit
2006-07-22 19:12 ` Matthias Barremaecker
2006-07-22 19:42 ` David Masover
2006-07-23 11:11 ` Sander Sweers
2006-07-22 20:04 ` Maciej Sołtysiak
2006-07-22 19:32 ` David Masover
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=1368904392.20060722232628@wp.pl \
--to=pysiak.satriani@wp.pl \
--cc=reiserfs-list@namesys.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 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.