From: Yaroslav Rastrigin <yarick@it-territory.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: [fuse-devel] Merging?
Date: Thu, 13 Jan 2005 02:19:31 +0300 [thread overview]
Message-ID: <200501130219.32461.yarick@it-territory.ru> (raw)
In-Reply-To: <200501122233.58450.vincenzo_mlRE.MOVE@yahoo.it>
Hi,
On 13 January 2005 00:33, you wrote:
> a particular filesystem and has ended up resorting to plasticfs (which
> uses the LD_PRELOAD trick - not quite satisfying but it does not
>
> require kernel patching) saying:
> > Most of the problem I have [...] will still be in a better
> > MLFUSE, which is that it requires to modify the kernel by loading a
> > module (which is often tied to one particular version of Linux which
> > means that it is tedious to maintain such module), and users hate
> > that.
Can't agree more. I don't want to release my fuse-based SMB-connector (smb
kioslave/gnome-vfs replacement :-) for exactly this reason - having released
some projects earlier , I can't afford (in terms of time) to answer emails
asking how to install fuse , where to grab it and which version, how to build
etc, so I'm eagerly awaiting when fuse will be merged and I could point to
kernel.org and required kernel version...
Right now I think -mm tree will be a good starting point to instantly increase
fuse testing base to iron out possible glitches and to ensure official
acceptance.
--
Managing your Territory since the dawn of times ...
next prev parent reply other threads:[~2005-01-12 23:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:33 Vincenzo Ciancia
2005-01-12 23:19 ` Yaroslav Rastrigin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 15:19 Hubert Tonneau
[not found] <loom.20041231T155940-548@post.gmane.org>
[not found] ` <E1ClQi2-0004BO-00@dorka.pomaz.szeredi.hu>
2005-01-12 13:49 ` Miklos Szeredi
2005-01-12 14:31 ` Diego Calleja
2005-01-12 14:51 ` Miklos Szeredi
[not found] ` <200501122120.08217.vincenzo_mlRE.MOVE@yahoo.it>
2005-01-12 20:32 ` Miklos Szeredi
2005-01-13 14:08 ` Pavel Machek
2005-01-12 15:58 ` Florian Schanda
2005-01-12 16:16 ` Dobrica Pavlinusic
2005-01-14 11:37 ` Nix
2005-01-12 19:01 ` Andrew Morton
2005-01-12 19:15 ` Erik Hensema
2005-01-12 19:56 ` Miklos Szeredi
2005-01-12 20:15 ` Christian Axelsson
2005-01-12 20:19 ` Miklos Szeredi
2005-01-12 20:51 ` Diego Calleja
2005-01-12 21:15 ` Tomasz Torcz
2005-01-13 14:37 ` Pavel Machek
2005-01-17 17:01 ` Steve McIntyre
2005-01-18 22:23 ` Luca Ferroni
2005-01-12 19:44 ` Pavel Machek
2005-01-12 20:35 ` Miklos Szeredi
2005-01-12 20:56 ` Pavel Machek
2005-01-13 9:06 ` Miklos Szeredi
2005-01-13 10:52 ` Bernhard Schauer
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=200501130219.32461.yarick@it-territory.ru \
--to=yarick@it-territory.ru \
--cc=linux-kernel@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
Powered by JetHome