public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Kristoffer <kfs1@online.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: captive-ntfs FUSE support?
Date: Wed, 10 Aug 2005 18:15:56 +0100	[thread overview]
Message-ID: <42FA364C.9090605@gentoo.org> (raw)
In-Reply-To: <op.svanygid3czpo8@myhost.localdomain>

Kristoffer wrote:
> why?:
> Since LUFS is no longer maintained and FUSE is. since to use the LUFIS  
> bridge you have to install LUFS,

This is not true. lufis is a compatibility layer on top of FUSE which provides 
the same API as lufs (thereby allowing you to load lufs modules into fuse). It 
does not actually rely on any part of lufs.

As for captive, I don't think its worth the effort. It has severe memory 
problems and Linux-NTFS development is going quite fast anyway.

Daniel

  parent reply	other threads:[~2005-08-10 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 13:33 captive-ntfs FUSE support? Kristoffer
2005-08-10 13:51 ` Michal Schmidt
2005-08-10 17:15 ` Daniel Drake [this message]
2005-08-11  1:36   ` Joseph Fannin
2005-08-11 11:00     ` Daniel Drake

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=42FA364C.9090605@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=kfs1@online.no \
    --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