From: Dobrica Pavlinusic <dpavlin@rot13.org>
To: akpm@osdl.org, torvalds@osdl.org
Cc: fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
mnalis@voyager.hr
Subject: Re: [fuse-devel] Merging?
Date: Wed, 12 Jan 2005 17:16:45 +0100 [thread overview]
Message-ID: <20050112161645.GA7162@llin.pliva.hr> (raw)
In-Reply-To: <20050112153131.1f778264.diegocg@gmail.com>
On Wed, Jan 12, 2005 at 03:31:31PM +0100, Diego Calleja wrote:
> El Wed, 12 Jan 2005 14:49:35 +0100 Miklos Szeredi <miklos@szeredi.hu> escribió:
> > Well, there doesn't seem to be a great rush to include FUSE in the
> > kernel. Maybe they just don't realize what they are missing out on ;)
> >
> > 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.
>
> -Possibility to write stupid filesystems like "gmailfs".
Not to mention Fuse::DBI which allows you to mount relational database
as a file-system. Imagine editing templates from your CMS with vi. Joy,
right?
Back to serious notes, having ability to write filesystems in user-space
is something that micro kernels (like HURD or plan9) had for a long time
and it's extremely useful if file-system semantic is mappable to problem
at hand.
That would also help reduce kernel bloat because you could write
something like umsdos in user-space where it belongs in first place.
--
Dobrica Pavlinusic 2share!2flame dpavlin@rot13.org
Unix addict. Internet consultant. http://www.rot13.org/~dpavlin
next prev parent reply other threads:[~2005-01-12 16:16 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 ` 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 [this message]
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
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=20050112161645.GA7162@llin.pliva.hr \
--to=dpavlin@rot13.org \
--cc=akpm@osdl.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mnalis@voyager.hr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome