[Midnightbsd-cvs] mports [21006] trunk/sysutils/fusefs-ntfs/files/README.FreeBSD: remove reporting info.

[laffer1 at midnightbsd.org]

Revision: 21006
          http://svnweb.midnightbsd.org/mports/?rev=21006
Author:   laffer1
Date:     2016-02-05 14:14:43 -0500 (Fri, 05 Feb 2016)
Log Message:
-----------
remove reporting info. this does not make sense

Modified Paths:
--------------
    trunk/sysutils/fusefs-ntfs/files/README.FreeBSD

Modified: trunk/sysutils/fusefs-ntfs/files/README.FreeBSD
===================================================================
--- trunk/sysutils/fusefs-ntfs/files/README.FreeBSD	2016-02-05 19:13:13 UTC (rev 21005)
+++ trunk/sysutils/fusefs-ntfs/files/README.FreeBSD	2016-02-05 19:14:43 UTC (rev 21006)
@@ -1,5 +1,5 @@
 ==============================================================================
-NTFS-3G README for the FreeBSD port
+NTFS-3G README for the BSD port
 ==============================================================================
 
 1. Introduction
@@ -27,13 +27,13 @@
 ==============================================================================
 
 The port has a patch to align read/write operations to the media block size
-(required on FreeBSD).
+(required on BSD).
 
 The port has 2 options: LOCK (to prevent access to the device by external
 programs than NTFS-3G once mounted, default on Linux), and UBLIO (use a user
 space cache library, see devel/libublio, not required on Linux).
 
-The reason for using UBLIO is that FreeBSD removed support for block devices,
+The reason for using UBLIO is that BSD removed support for block devices,
 being them now character devices. The former ones had a cache, and NTFS-3G was
 optimized for it (Linux still uses them). The same happens on Mac OS X (based
 on FreeBSD 5). So using UBLIO both improves performance (~10 times faster),
@@ -124,26 +124,8 @@
 described in fuse4bsd (sysutils/fusefs-kmod) documentation (Linux access is
 path based while FreeBSD is vnode based, which may be reused).
 
-==============================================================================
-6. Reporting bugs
-==============================================================================
-
-About the port itself, you can ask the maintainer (preferable) and/or in the
-ports at FreeBSD.org mailing list.
-
-About general NTFS problems (corruptions, etc) ask in the NTFS-3G forum (see
-below).
-
-But often (even on Linux, 50% of the issues are related to these) the problems
-reside on the FUSE implementation (the library itself, or fuse4bsd portion).
-
-For reporting kernel panics, see:
-
-http://fuse.sourceforge.net/wiki/index.php/DebugFreeBSDPanicsHowto
-
 And you can report them to the fuse4bsd author (preferable), or here:
 
 NTFS-3G forum:	http://forum.ntfs-3g.org/
-FreeBSD PRs:	http://www.freebsd.org/send-pr.html
 
 ==============================================================================