Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Oct 2007 14:27:53 -0400 (EDT)
From:      "Monah Baki" <mbaki@whywire.net>
To:        "Monah Baki" <mbaki@whywire.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: 1 TB data copy
Message-ID:  <4393.192.60.228.173.1192213673.squirrel@www.geekisp.com>
In-Reply-To: <44658.192.60.228.173.1192211870.squirrel@www.geekisp.com>
References:  <3236.67.100.188.210.1192191787.squirrel@www.geekisp.com> <20071012085956.7d8faf2d.wmoran@potentialtech.com> <470F7545.5010808@cyberleo.net> <54db43990710120649s222eb064td2400db50a7b8e65@mail.gmail.com> <44658.192.60.228.173.1192211870.squirrel@www.geekisp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Solved it.

Had to manually run

kldload /usr/local/modules/fuse.ko


Thank you all for your support.



> Hi all,
>
> Installed the following
>
> sysutils/fusefs-ntfs
> sysutils/ntfsprogs
>
> When I run the command
>
> ntfs-3g /dev/da0s1 /mnt/windows
>
> I get the error message
> fuse: failed to open fuse device: No such file or directory
>
>
> Thank you
>
>
>
>> On 10/12/07, CyberLeo Kitsana <cyberleo@cyberleo.net> wrote:
>>> Bill Moran wrote:
>>> > In response to "Monah Baki" <mbaki@whywire.net>:
>>> > I'm not completely up to speed with FreeBSD's NTFS support.  Last I
>>> looked
>>> > at it, it was experimental and there were warnings everywhere.  I
>>> assume
>>> > it's improved since then (~3 years ago) but can't say with authority.
>>>
>>> As I recall, the native FreeBSD NTFS support is read-only. However, the
>>> NTFS-3g project has a mostly complete (and pretty safe) read/write
>>> implementation as a FUSE program, which can be found in ports:
>>>
>>> sysutils/fusefs-ntfs
>>> sysutils/ntfsprogs
>>>
>>
>> FreeBSD NTFS is not read only, but there are restrictions on what it
>> can write. To quote the man page:
>>
>>      There is limited writing ability.  Limitations: file must be
>> nonresident
>>      and must not contain any sparses (uninitialized areas); compressed
>> files
>>      are also not supported.  The file name must not contain multibyte
>> charac-
>>      ters.
>>
>> If your file name uses only ASCII characters, you will be probably be
>> OK using mount_ntfs to write to an NTFS filesystem. I've used it for
>> years, but mostly for reading files. The few times I've used it for
>> writing, it worked fine. I think you are most likely to have problems
>> if you use it to edit an existing file.
>>
>> - Bob
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"
>>
>
>
> BSD Networking, Microsoft Notworking
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"
>


BSD Networking, Microsoft Notworking



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4393.192.60.228.173.1192213673.squirrel>