FAQ SearchLogin
Tuxera Home
View unanswered posts | View active topics It is currently Fri Jun 18, 2021 19:04

Post new topic Reply to topic  [ 7 posts ] 
NTFS-3G on FreeBSD 6.2 
Author Message

Joined: Mon May 21, 2007 19:23
Posts: 3
Post NTFS-3G on FreeBSD 6.2
I've just installed FreeBSD 6.2 and fusefs-ntfs is not visible, i've tried pkg_add and the package isn't in the "latest" dir on their ftp for ports for this version.

Does anyone know why this is?

I tried to install manually but it gave me an error during ./configure:

"configure: error: Please see FreeBSD support at http://www.freshports.org/sysutils/fusefs-ntfs"

Anyone had this before or know what's going on?

Tue May 22, 2007 00:55
Tuxera CTO

Joined: Tue Nov 21, 2006 23:15
Posts: 1648
Post NTFS-3G on FreeBSD 6.2
Did you try both of the belows? What are the exact error messages?

To install the port: cd /usr/ports/sysutils/fusefs-ntfs/ && make install clean


To add the package: pkg_add -r fusefs-ntfs

Tue May 22, 2007 01:08

Joined: Mon May 21, 2007 19:23
Posts: 3
error for pkg_add:

:: pkg_add -r fusefs-ntfs
Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports ... s-ntfs.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.0-release/Latest/fusefs-ntfs.tbz' by URL

and the port doesn't exist:

/usr/ports/sysutils/fusefs-ntfs: No such file or directory.

Tue May 22, 2007 13:16
Tuxera CTO

Joined: Tue Nov 21, 2006 23:15
Posts: 1648
pkg_add tries to use a totally wrong, non-existing directory (packages-6.0-release). But it also seems that only FreeBSD 7 has the package.

Tue May 22, 2007 15:07

Joined: Mon May 21, 2007 19:23
Posts: 3
Thanks for your help szaka, not sure why it didn't come with release but i've done a proper cvsup now, I was updating src now ports (oops) and i've now installed it, next will be mounting drives :)

Tue May 22, 2007 17:42

Joined: Mon Jun 04, 2007 15:12
Posts: 1
Who knows how get on with "mount_fusefs: seekscript failed" ?
Thanks! :)

Mon Jun 04, 2007 15:24

Joined: Mon Mar 05, 2007 02:23
Posts: 14
Faust wrote:
Who knows how get on with "mount_fusefs: seekscript failed" ?
Thanks! :)

The very same question was the topic of fuse4bsd-devel@ last December:
http://creo.hu/pipermail/fuse4bsd-devel ... hread.html

Funnily, the only post which is missing from the archive (due to braindead
Mailman content filtering) is the one which tells the solution :) So I copy
that mail right here.

If it didn't help in your case, write to

fuse4bsd-devel creo hu
              @    .

or to me,

csaba.henk creo hu
          @    .

From csaba.henk@xxx Sun Dec 17 18:17:01 2006
Date: Sun, 17 Dec 2006 18:17:01 +0100
From: Csaba Henk <csaba.henk@xxx>
To: Anish Mistry <amistry@xxx>
Cc: fuse4bsd-devel@xxx, Yura Pakhuchiy <pakhuchiy@xxx>


Funny it is. The fact that both you and Yura had the same problem with
by-and-large the same code snapshot is pretty misleading. Your problem
has nothing to do with 6.2-RC1 as such.

Indeed it has something to do with your kernel config. (For Yura I can't
precisely know that this was the problem, as he failed to send me his
config, but the symptoms strongly suggest this.)

You seem to be unaware of the following notification in

# Enable extra debugging code for locks.  This stores the filename and
# line of whatever acquired the lock in the lock itself, and change a
# number of function calls to pass around the relevant data.  This is
# not at all useful unless you are debugging lock code.  Also note
# that it is likely to break e.g. fstat(1) unless you recompile your
# userland with -DDEBUG_LOCKS as well.
options         DEBUG_LOCKS

So recompile fstat with -DDEBUG_LOCKS. Apart from userland, the fuse
module also needs the appropriate defines. Therefore I added support for
building the module against a particular kernel config:


This is for the devel code though, therefore I attach hereby a patch which you
can apply against the release.

So apply the appropriate patch, and compile fuse4bsd so that you add a
"KERNCONF=BIGGUY" to your make parameters. From that on things will work
again, hopefully.

  *  *  *

Now what to do about the port?

It's your task to make up your mind :) nevertheless I have some ideas.

1) Leave things as is and let users figure out this themselves?
2) Parse out the config of the acually running kernel from uname output
   or from the kern.version sysctl?
3) Don't do anything but warn users to add the appropriate KERNCONF
   value if they use a non-standard config?

Regarding 2): it could be done, eg., as follows:
take the output of

  sysctl kern.version | head -2 | tail -1 | sed -n "s/.*@`hostname`://p"

If it's not empty, this could be passed to make as the vaule of
KERNCONFDIR (here KERCONFDIR, above KERNCONF, that's intentional!).
If it's empty then the kernel has been compiled on another machine and
the config may not be available.

However, 2) may not be appropriate at all if target system differs from
the currently running one.

I think the best would be adding a "make config" menu where one could
choose if s/he wants the value of KERCONFDIR being found out for the
currently running kernel as written above.


diff -r c9549d324226 fuse_module/Makefile
--- a/fuse_module/Makefile   Sat Feb 11 01:30:59 2006 +0200
+++ b/fuse_module/Makefile   Sun Dec 17 17:37:42 2006 +0100
@@ -7,8 +7,12 @@ CFLAGS+=3D -DFMASTER

-.if defined(INVARIANTS)
+.if defined(KERNCONF)
+KERNCONFDIR=3D /usr/obj/usr/src/sys/${KERNCONF}
+.if defined(KERNCONFDIR)

.if defined(DEBUG)
diff -r c9549d324226 fuse_module/fuse_subr.c
--- a/fuse_module/fuse_subr.c   Sat Feb 11 01:30:59 2006 +0200
+++ b/fuse_module/fuse_subr.c   Sun Dec 17 17:37:42 2006 +0100
@@ -1,3 +1,5 @@
+#include "config.h"
#include <sys/types.h>
#include <sys/param.h>
#include <sys/systm.h>
diff -r c9549d324226 fuse_module/config.h
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/fuse_module/config.h   Sun Dec 17 17:37:42 2006 +0100
@@ -0,0 +1,3 @@
+#include <opt_global.h>

Thu Jun 07, 2007 12:49
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.