Yes, it works.
Why do I have to kldload it manually?
I think this is why; during November, the time of ccc post, I had just upgraded from the all-mighty FreeBSD-10.1 p4 to FreeBSD-10.2 p7. Just like 8.2, I’m back to doing things by the book(s). The first thing I installed was pftop, then sshguard. Sshguard did not work properly. It had the machine wide open.
No worries, I’ll fix it later. By the time I install
sysutils/fusefs-ntfs all my tests fail. Been there before. I juggled to confusion. As you see in my previous post I had
ntfs_load=”YES” in both the
/boot/loader.conf and
/etc/rc.conf. I could have fixed it by fixing my mistake
if any, but I’m sure I tested both ways individually, many times. I gave up.
Anyway, I jump to fix sshguard first. I have p4 in primary-3. This is why I like duel-boot. It's for cases like this. I deleted all the sshguard and ntfs files from p7-10.2. I mounted primary-3. I copied all those same files from p4-10.1 to p7-10.2 to their proper directories. I removed the rc.conf entry
if not already.
After booting, both ntfs and sshguard worked. So as far as removing the command out of the rc.conf, I don’t know what happen, but I know I tested it for days, individually as I googled for the new solution. Eventually I did not care to repeat those steps to be sure. It worked! And above all, sshguard worked too. The problem could have been bad ports, but for me, upgrading FreeBSD beyond p4, than p7 brought new problems for my Gnome/Mate setup. I don’t care no more. I loved p4, but now I got p7-10.2. As far a desktop goes, I may never give it up until 11.2. I mean it this time.