From: David Masover <ninja@slaphack.com>
To: reiserfs-list@namesys.com
Subject: Re: ReConfigurable Directory Structure & Agrregation of files according to semantic.
Date: Thu, 18 Mar 2004 17:04:30 -0600 [thread overview]
Message-ID: <405A2AFE.8060107@slaphack.com> (raw)
In-Reply-To: <87u10njss0.fsf@uhoreg.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hubert Chan wrote:
|>>>>>"David" == David Masover <ninja@slaphack.com> writes:
|
|
| David> Alexander G. M. Smith wrote:
| Alexander> ... I (and others) think it would be better for this to be
| Alexander> done at the file system level. That way you can leverage all
| Alexander> sorts of other utilities and
|
| David> What about a reiser4 plugin?
|
| I would think that would count as being in the filesystem level.
Yet it doesn't involve writing a *new* filesystem, which is I think what
was being suggested? Alexander?
| David> What about a plugin that is mostly in userspace?
|
| That just reminded me of lufs[1], which allows you to create a userspace
| daemon that communicates with the lufs module to provide access to a
A userspace daemon is what I was thinking, except that lufs is, again,
implementing an entire filesystem rather than piggybacking on one that
already exists. Or is this new filesystem really so easy? If so, I
want my stable reiser4!
No offense to anyone working on reiser4. It looks impressive so far,
and I haven't even taken a peek at the code. I'm impatient, but I don't
want to seem ungrateful.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQFoq/ngHNmZLgCUhAQLiNg//QOOTYVCMGzvWp7TPpJUMBUw3ty8rN8cT
XzCojUMKnece5O3NT75UHjkiRRKWiZxFxSkvwa7idfzg0fOajdCxdYqxnN3k+c6q
nZyp2cUeLPG/EU4oSIhEjEZYhj5IUENUzALhPftAOveUMc4vN0XvmpAESUZ1ApBp
efKH61wiWn7eq3NdHXMBbWroC9Rp2W1H36Gqe4lBwZFPPSo+XXHmjT2kRY5sjw9x
RA2UcoFiNbsfLiLviFAsfAiHSkCUop06Tub0js3sMAvWNxHPE6Fu6/DOUxmZsKom
tz10eAL+I0oRBy0+iVzwpEZ6aB2ic17cPS9KW9RBwzYWfVavJKrJ+BqZRgL0sARl
dW4A9XkKiyngAufrUli6WDJaihaWZtpP1APpBmM+eDdVQzihuVlL9ZCPaybtuhDn
O8dgwXKSdE2GCKG0lGEweKbow6mXDe8TTypvXzpSDVU4cyvBdUzhisb2HyHlUigx
rH1kJlTQvEmQIWnxkqQQxe5oX98dNnHxJLDtRyoiIN9ATGE0tEWbHZzvO8rGsOA3
wxtRwIr4xeXUKF8I0RN+3JI9rNqH2UNTzNTTIhOleVqO9O50IDJSR++XT0ZJ65Lu
WDctewQ16xm84IobMKqV3c+GVdRIpQjIdaChjnDYaovf+wstcQnzT/y9D58MOOma
+U37zogaPIs=
=k/hJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-03-18 23:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 22:45 ReConfigurable Directory Structure & Agrregation of files according to semantic faraz ahmed
2004-03-16 23:52 ` Alexander G. M. Smith
2004-03-17 2:49 ` Isaac Claymore
2004-03-17 3:22 ` Alexander G. M. Smith
2004-03-17 14:47 ` David Masover
2004-03-17 17:19 ` Hubert Chan
2004-03-18 23:04 ` David Masover [this message]
2004-03-19 0:32 ` Alexander G. M. Smith
2004-03-19 1:39 ` Hubert Chan
2004-03-17 4:10 ` Hubert Chan
2004-03-17 6:28 ` Isaac Claymore
2004-03-17 16:49 ` Hubert Chan
2004-03-20 17:54 ` Valdis.Kletnieks
2004-03-22 21:08 ` Hubert Chan
2004-03-22 21:28 ` Valdis.Kletnieks
2004-03-22 22:37 ` Hubert Chan
2004-03-17 7:53 ` faraz ahmed
2004-03-17 8:14 ` Hans Reiser
2004-03-17 8:20 ` Nishant Sharma
2004-03-17 17:04 ` Hubert Chan
2004-03-17 17:49 ` Nishant Sharma
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=405A2AFE.8060107@slaphack.com \
--to=ninja@slaphack.com \
--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.