Date: Thu, 22 Aug 2013 09:58:17 -0500 From: Mark Felder <feld@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: sysutils/fusefs-ntfs & fusefs_enable="YES" Message-ID: <1377183497.4016.12901853.54B19F71@webmail.messagingengine.com> In-Reply-To: <20130822141656.267fd5c5@gumby.homeunix.com> References: <20130821223937.30d7e266@gumby.homeunix.com> <521534C9.3090207@bsdforen.de> <20130821230934.778ea95b@gumby.homeunix.com> <1377171693.8666.12828877.1913470C@webmail.messagingengine.com> <20130822141656.267fd5c5@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 22, 2013, at 8:16, RW wrote: > On Thu, 22 Aug 2013 06:41:33 -0500 > Mark Felder wrote: > > > On Wed, Aug 21, 2013, at 17:09, RW wrote: > > > > 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. > > I have added it to loader.conf, but the reason I brought it up was that > I thought the documentation might be out of date, which appears to be > the case. > > If nothing's been decided I can't really submit a documentation > patch. > > If anyone's interested the relevant files are: > > sysutils/ntfsprogs/files/README.FreeBSD > sysutils/fusefs-ntfs/files/README.FreeBSD > I forgot about the READMEs that come with those ports. We might want to mention FreeBSD 10+ specific setup there I guess.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1377183497.4016.12901853.54B19F71>