Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Apr 2018 20:29:20 +0200
From:      Polytropon <freebsd@edvax.de>
To:        Ernie Luzar <luzar722@gmail.com>
Cc:        tech-lists@zyxst.net, freebsd-questions@freebsd.org
Subject:   Re: Help mounting USB NTFS HD
Message-ID:  <20180415202920.c4c310c7.freebsd@edvax.de>
In-Reply-To: <5AD38810.8040806@gmail.com>
References:  <5AD35C67.9030208@gmail.com> <20180415171851.add2965a.freebsd@edvax.de> <5AD3792B.70004@gmail.com> <a15a830b-f2c1-3217-da54-d333cdf49101@zyxst.net> <5AD38810.8040806@gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sun, 15 Apr 2018 13:12:48 -0400, Ernie Luzar wrote:
> tech-lists wrote:
> > On 15/04/2018 17:09, Ernie Luzar wrote:
> >> But just to verify, I added it and rebooted. This changed nothing. Still
> >> got
> >> /root >ntfs-3g -o r /dev/da0s1 /mnt
> >> fuse: failed to open fuse device: No such file or directory
> > 
> > Please paste the output of (as root) kldstat.
> > 
> > -o r isn't a valid option, at least not according to the manpage. It
> > should be -o ro like this:
> > 
> > ntfs-3g -o ro /dev/da0s1 /mnt
> 
> 
> The syntax for /boot/loader.conf  is
> 
> fuse_load="YES"  NOT fuse_enable="YES"
> 
> kldstat now shows fuse.ko as loaded
> 
> and ntfs-3g -o ro /dev/da0s1 /mnt cmd does work.
> 
> Thanks for everyones help.

Sorry for the confusion - yes, _load is correct, _enable is WRONG.
I just checked from an actual instantiation of /boot/loader.conf
on a system that happily uses the ntfs-3g mount approach as shown
above. :-)


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20180415202920.c4c310c7.freebsd>