From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] FUSE (was: Add a module post kernel config/build)
Date: Wed, 18 Apr 2007 15:35:49 +0200 [thread overview]
Message-ID: <1609263.41bEaePWJD@kn.gn.rtr.message-center.info> (raw)
In-Reply-To: 20070418135051.3d23b2a7@hactar.digimed.co.uk
Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 18 Apr 2007 12:37:07 +0200, Alexander Skwar wrote:
>
>> As far FUSE is concerned, it might be advisable to stay away from the
>> in-kernel FUSE and use the standalone sys-fs/fuse package. At
>> least ntfs3g doesn't work with the in-kernel fuse.
>
> Really? It works here, as do sshfs and encfs.
Hm. Not so sure anymore. I seem to remember, that either sys-fs/ntfs3g
or sys-fs/fuse would completely refuse to build, if in-kernel fuse was
built.
But checking out the ebuilds on the CVS, I can't seem to be able to back
this statement I made.
While we're at the topic of fuse - which version is more recent?
The one in gentoo kernel or the one in the seperate package?
Alexander Skwar
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-18 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 9:15 [gentoo-user] Add a module post kernel config/build reader
2007-04-18 10:33 ` Boyd Stephen Smith Jr.
2007-04-19 0:44 ` [gentoo-user] " reader
2007-04-18 10:37 ` Alexander Skwar
2007-04-18 12:50 ` Neil Bothwick
2007-04-18 13:35 ` Alexander Skwar [this message]
2007-04-18 15:00 ` [gentoo-user] FUSE (was: Add a module post kernel config/build) Neil Bothwick
2007-04-19 0:40 ` [gentoo-user] " reader
2007-04-19 4:42 ` Nistor Andrei
2007-04-19 6:58 ` Alexander Skwar
2007-04-19 10:45 ` reader
2007-04-19 13:15 ` Neil Bothwick
2007-04-18 10:47 ` [gentoo-user] Add a module post kernel config/build Mike Williams
2007-04-18 11:10 ` Etaoin Shrdlu
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=1609263.41bEaePWJD@kn.gn.rtr.message-center.info \
--to=listen@alexander.skwar.name \
--cc=gentoo-user@lists.gentoo.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