Date: Thu, 5 Feb 2015 11:43:52 +0000 (UTC) From: "Thomas Mueller" <mueller6724@bellsouth.net> To: freebsd-ports@freebsd.org Subject: Re: How to use mkntfs, I get "not a block device" Message-ID: <469946.64698.bm@smtp115.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>
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. >> > > Should I wait for the bug fix to show in sysutils/fusefs-ntfs, or should I just do > > mkntfs -F /dev/gpt/SeaExp1-03 ? > > 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 I just did with -F, got the message that Windows won't be able to boot from such a device, then get Initializing device with zeroes: 0% (now up to 3% as I type this on other computer. I can wait, really need to go to bed.) I wasn't planning to run MS-Windows, and don't know if there is anything else that could boot from NTFS. Thanks for help! Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469946.64698.bm>