Date: Thu, 5 Feb 2015 13:51:30 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Thomas Mueller <mueller6724@bellsouth.net> Cc: freebsd-ports@freebsd.org Subject: Re: How to use mkntfs, I get "not a block device" Message-ID: <EC6E96DA-74F6-43C0-BD44-28C21249954E@dons.net.au> In-Reply-To: <666687.83990.bm@smtp117.sbc.mail.ne1.yahoo.com> References: <901212.67634.bm@smtp117.sbc.mail.ne1.yahoo.com> <43567E46-07C9-4067-B9A7-18080B93B64B@dons.net.au> <134D33C1-973F-46E8-AC09-29CAF8DB3A99@dons.net.au> <666687.83990.bm@smtp117.sbc.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 4 Feb 2015, at 20:28, Thomas Mueller <mueller6724@bellsouth.net> = wrote: >> The port should really patch this out (IMO) - it doesn't make sense = on FreeBSD since it doesn't _have_ block devices. >> If you pass it the -F flag it should let your format the disk. >>=20 > Should I wait for the bug fix to show in sysutils/fusefs-ntfs, or = should I just do > mkntfs -F /dev/gpt/SeaExp1-03 ?=20 > after kldload fuse . Just use -F. Note that mkntfs is unrelated to fuse - you can use the NTFS tools = without touching FUSE at all - the only time FUSE is involved is when = you mount an NTFS volume. > I thought I'd seen error messages referring to block devices, or "not = a block device" in FreeBSD and NetBSD before. They were removed a while ago :) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC6E96DA-74F6-43C0-BD44-28C21249954E>