Re: sysutils/fusefs-ntfs fusefs_enable=YES
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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: sysutils/fusefs-ntfs fusefs_enable=YES
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 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: sysutils/fusefs-ntfs fusefs_enable=YES
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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
sysutils/fusefs-ntfs fusefs_enable=YES
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. Has something fallen off here? Perhaps the README file should just recommend adding fuse_load=YES to loader.conf. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: sysutils/fusefs-ntfs fusefs_enable=YES
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 -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: sysutils/fusefs-ntfs fusefs_enable=YES
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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
