Date: Thu, 22 Aug 2013 06:41:33 -0500 From: Mark Felder <feld@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: sysutils/fusefs-ntfs & fusefs_enable="YES" Message-ID: <1377171693.8666.12828877.1913470C@webmail.messagingengine.com> In-Reply-To: <20130821230934.778ea95b@gumby.homeunix.com> References: <20130821223937.30d7e266@gumby.homeunix.com> <521534C9.3090207@bsdforen.de> <20130821230934.778ea95b@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 21, 2013, at 17:09, RW wrote: > On Wed, 21 Aug 2013 23:44:41 +0200 > Dominic Fandrey wrote: > > > On 21/08/2013 23:39, RW wrote: > > > The README.FreeBSD file for sysutils/fusefs-ntfs and several howtos > > > suggest adding the line: > > > > > > fusefs_enable="YES" > > > > > > to rc.conf, but as far as I can see this doesn't affect anything > > > since the port doesn't install an rc.d file. I would have expected > > > such a file to load the fuse kernel module which I'm having to load > > > myself. > > > > The file is there. fusefs-kmod > > I see what's happened. Earlier in the year,against my better judgement, > I move to CURRENT in futile attempt to make intel KMS work. It looks > like fuse has been moved into the base system, but /etc/rc.d/ hasn't yet > been updated to reflect that. > There isn't an /etc/rc.d/ for every kernel module. If you want to use fuse on FreeBSD 10 and later just put fuse_load="YES" in loader.conf. The rc.d script in the port was just a nice courtesy. I don't think it's likely we'll see an /etc/rc.d/fuse script appear in the base system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1377171693.8666.12828877.1913470C>