public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miklos.Szeredi@eth.ericsson.se (Miklos Szeredi)
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	avfs@fazekas.hu
Subject: [ANNOUNCE] FUSE: Filesystem in Userspace 0.95
Date: Thu, 10 Jan 2002 10:55:09 +0100 (MET)	[thread overview]
Message-ID: <200201100955.KAA19208@duna207.danubius> (raw)


FUSE 0.95 is available (download or CVS) from:

   http://sourceforge.net/projects/avf

What's new in 0.95 compared to 0.9

   - Major performance improvements in both the kernel module and the
     library parts.

   - Small number of bugs fixed.  FUSE has been through some stress
     testing and no problems have turned up yet.

   - Library interface simplified.  A simple 'hello world' filesystem
     can now be implemented in less than 100 lines.

   - Python (by Jeff Epler) and Perl (by Mark Glines) bindings are in
     the works, and will be released some time in the future (now
     available through CVS).

Problems still remaining:

   - Security problems when fuse is used by non-privileged users:

       o permissions on mountpoint can only be checked by kernel
         (patch exists)

       o user can intentionally block the page writeback operation,
         causing a system lockup.  I'm not sure this can be solved in
         a truly secure way.  Ideas?

Introduction for newbies:

  FUSE provides a simple interface for userspace programs to export a
  virtual filesystem to the Linux kernel.  FUSE also aims to provide a
  secure method for non privileged users to create and mount their own
  filesystem implementations.

  Fuse is available for the 2.4 (and later) kernel series.
  Installation is easy and does not need a kernel recompile.

             reply	other threads:[~2002-01-10  9:55 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  9:55 Miklos Szeredi [this message]
2002-01-13  3:10 ` [ANNOUNCE] FUSE: Filesystem in Userspace 0.95 Pavel Machek
2002-01-21 10:18   ` Miklos Szeredi
2002-01-23 10:47     ` Pavel Machek
2002-01-22 19:07 ` Daniel Phillips
2002-01-23  2:33   ` [Avfs] " Justin Mason
2002-01-23  5:26     ` Daniel Phillips
  -- strict thread matches above, loose matches on Subject: below --
2002-02-22 15:57 [PATCH] 2.4.x write barriers (updated for ext3) James Bottomley
2002-02-22 16:10 ` Chris Mason
2002-02-22 16:13 ` Stephen C. Tweedie
2002-02-22 17:36   ` James Bottomley
2002-02-22 18:14     ` Chris Mason
2002-02-28 15:36       ` James Bottomley
2002-02-28 15:55         ` Chris Mason
2002-02-28 17:58           ` Mike Anderson
2002-02-28 18:12           ` Chris Mason
2002-03-01  2:08             ` James Bottomley
2002-03-03 22:11         ` Daniel Phillips
2002-03-04  3:34           ` Chris Mason
2002-03-04  5:05             ` Daniel Phillips
2002-03-04 15:03               ` James Bottomley
2002-03-04 17:04                 ` Stephen C. Tweedie
2002-03-04 17:16                   ` Chris Mason
2002-03-04 18:05                     ` Stephen C. Tweedie
2002-03-04 18:28                       ` James Bottomley
2002-03-04 19:55                         ` Stephen C. Tweedie
2002-03-04 19:48                       ` Daniel Phillips
2002-03-04 19:57                         ` Stephen C. Tweedie
2002-03-04 21:06                           ` Daniel Phillips
2002-03-05 14:58                             ` Stephen C. Tweedie
2002-03-05  7:48                         ` Jens Axboe
2002-03-04 19:51                     ` Daniel Phillips
2002-03-05  7:42                       ` Jens Axboe
2002-03-04 17:35                   ` James Bottomley
2002-03-04 17:48                     ` Chris Mason
2002-03-04 18:11                       ` James Bottomley
2002-03-04 18:41                         ` Chris Mason
2002-03-04 21:34                         ` Stephen C. Tweedie
2002-03-04 18:09                     ` Stephen C. Tweedie
2002-03-04  8:19             ` Helge Hafting
2002-03-04 14:57             ` James Bottomley
2002-03-04 17:24               ` Chris Mason
2002-03-04 19:02                 ` Daniel Phillips
2002-03-05  7:22               ` Jeremy Higdon
2002-03-05 23:01                 ` Daniel Phillips
2002-03-04  4:21           ` Jeremy Higdon
2002-03-04  5:31             ` Daniel Phillips
2002-03-04  6:09               ` Jeremy Higdon
2002-03-04  7:57                 ` Daniel Phillips
2002-03-05  7:09                   ` Jeremy Higdon
2002-03-05 22:56                     ` Daniel Phillips
2002-03-04 16:52                 ` Stephen C. Tweedie
2002-03-04 18:15                   ` Daniel Phillips
2002-03-05  7:40                     ` Jens Axboe
2002-03-05 22:29                       ` Daniel Phillips
2002-03-12  7:01                         ` Jens Axboe
2002-03-10  5:24                   ` Douglas Gilbert
2002-03-11 11:13                     ` Kurt Garloff
2002-03-12  1:17                       ` GOTO Masanori
2002-03-12  6:58                       ` Jens Axboe
2002-03-13 22:37                         ` Peter Osterlund
2002-03-11 11:34                     ` Stephen C. Tweedie
2002-03-11 17:15                       ` James Bottomley
2002-03-04 14:48           ` James Bottomley
2002-03-06 13:59             ` Daniel Phillips
2002-03-06 14:34               ` James Bottomley
2002-02-25 10:57 ` Helge Hafting
2002-02-25 15:04   ` James Bottomley

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=200201100955.KAA19208@duna207.danubius \
    --to=miklos.szeredi@eth.ericsson.se \
    --cc=avfs@fazekas.hu \
    --cc=linux-fsdevel@vger.kernel.org \
    --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