All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: kinema@gmail.com, fuse-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, akpm@osdl.org, torvalds@osdl.org
Subject: Re: [fuse-devel] Merging?
Date: Wed, 12 Jan 2005 15:31:31 +0100	[thread overview]
Message-ID: <20050112153131.1f778264.diegocg@gmail.com> (raw)
In-Reply-To: <E1CoisR-0001Hi-00@dorka.pomaz.szeredi.hu>

El Wed, 12 Jan 2005 14:49:35 +0100 Miklos Szeredi <miklos@szeredi.hu> escribió:


> So if any of you would like to support this motion, you can mail the
> linux-kernel list and maybe Linus and Andrew, to generate a little
> discussion on why (or why not) inclusion is a good idea.


Personally I think it's cool for "desktops" and other reasons because:

-It could replace gnome-vfs AND kioslaves by a more generic solution that works
 for all environments

-You could implement several "not-performance-critical" filesystems (fat,
 isofs) with FUSE to avoid possible security issues. Give that nowadays 
 usb sticks and cd/dvds are so common it'd be possible to modify a filesystem
 on purpose to crash the kernel if a bug were found in those filesytems. With
 FUSE that posibility decreases.

-Since you can use other programming languages, I suposse it'd be easier for
 people to write support for weird filesystems.

-Better for kernel (less code to maintain given a big number of filesystems)
 and less pressure for VFS developers when making big changes to the VFS.

-Possibility to write stupid filesystems like "gmailfs".
 

  reply	other threads:[~2005-01-12 14:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20041231T155940-548@post.gmane.org>
     [not found] ` <E1ClQi2-0004BO-00@dorka.pomaz.szeredi.hu>
2005-01-12 13:49   ` [fuse-devel] Merging? Miklos Szeredi
2005-01-12 14:31     ` Diego Calleja [this message]
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
2005-01-12 15:19 Hubert Tonneau
  -- strict thread matches above, loose matches on Subject: below --
2005-01-12 21:33 Vincenzo Ciancia
2005-01-12 23:19 ` Yaroslav Rastrigin

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=20050112153131.1f778264.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --cc=akpm@osdl.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=kinema@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@osdl.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 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.