From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] To Neil Bothwick: Question re ntfs-3g
Date: Thu, 04 Oct 2007 11:12:22 +0800 [thread overview]
Message-ID: <1191467542.14241.8.camel@neuromancer.home.net> (raw)
In-Reply-To: <47045885.9000404@sbcglobal.net>
On Wed, 2007-10-03 at 22:05 -0500, Anthony E. Caudel wrote:
> Neil, back on 15 July, you stated that you used ntfs-3g with only the
> in-kernel fuse modules.
>
> When I try that, I get the following error:
>
> error while loading shared libraries: libfuse.so.2: cannot open shared
> object file: No such file or directory
>
> I find I have to use sys-fs/fuse to be able to mount ntfs-3g.
I'm using ntfs-3g w/o issues. I'm not using in-kernel fuse modules
though. I'm compiling it from the version in portage
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-04 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 3:05 [gentoo-user] To Neil Bothwick: Question re ntfs-3g Anthony E. Caudel
2007-10-04 3:12 ` Ow Mun Heng [this message]
2007-10-04 5:49 ` Liviu Andronic
2007-10-04 6:59 ` Iain Buchanan
2007-10-04 8:20 ` Neil Bothwick
2007-10-04 20:50 ` Anthony E. Caudel
2007-10-04 6:59 ` [gentoo-user] " Alexander Skwar
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=1191467542.14241.8.camel@neuromancer.home.net \
--to=ow.mun.heng@wdc.com \
--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