Comments for anderson http://blogs.freebsdish.org/anderson Just another FreeBSD Committers Blogs weblog Fri, 21 Nov 2008 10:57:28 +0000 http://wordpress.org/?v=2.6 Comment on PUFFS for FreeBSD? by Ale http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-30 Ale Mon, 25 Aug 2008 17:53:58 +0000 http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-30 Hello. I'm the maintainer of the sysutils/fusefs-ntfs (NTFS-3G) port, and it has some serious problems residing in the current fuse4bsd implementation (the author quickly fixed most of the problems that appeared, but now he is very busy at work IIRC). See the fusefs-ntfs/files/README.FreeBSD file, section "Known Problems". In short (I'm not a kernel programmer so please excuse me if I made some mistakes in the explanation), as FreeBSD uses vnode based IO and Linux uses full paths, it happens frequently that when a vnode is reused any filesystem using FUSE reports "file not found" or EAGAIN when using the filesystem (not the FUSE one, but the native UFS fs; as the problems is with the vnodes being reused). These problems can make it unusable when doing something else like compiling/extracting. Doing any kind of operations inside the FUSE filesystem does not produce the error, as it uses a user space caching library. If you make any progress on the port, I would like to hear about it. Also it would be nice if the code could be shared between FreeBSD and NetBSD then. Thanks, Ale Hello.

I’m the maintainer of the sysutils/fusefs-ntfs (NTFS-3G) port, and it has some serious problems residing in the current fuse4bsd implementation (the author quickly fixed most of the problems that appeared, but now he is very busy at work IIRC). See the fusefs-ntfs/files/README.FreeBSD file, section “Known Problems”.

In short (I’m not a kernel programmer so please excuse me if I made some mistakes in the explanation), as FreeBSD uses vnode based IO and Linux uses full paths, it happens frequently that when a vnode is reused any filesystem using FUSE reports “file not found” or EAGAIN when using the filesystem (not the FUSE one, but the native UFS fs; as the problems is with the vnodes being reused). These problems can make it unusable when doing something else like compiling/extracting. Doing any kind of operations inside the FUSE filesystem does not produce the error, as it uses a user space caching library.

If you make any progress on the port, I would like to hear about it. Also it would be nice if the code could be shared between FreeBSD and NetBSD then.

Thanks,
Ale

]]> Comment on FreeBSD Cross Reference Online by Anthony Anderson http://blogs.freebsdish.org/anderson/2007/10/19/freebsd-cross-reference-online/#comment-9 Anthony Anderson Fri, 18 Jan 2008 19:46:41 +0000 http://blogs.freebsdish.org/anderson/2007/10/19/freebsd-cross-reference-online/#comment-9 Hey!...I Googled for eric anderson, but found your page about FreeBSD Cross Reference Online...and have to say thanks. nice read. Hey!…I Googled for eric anderson, but found your page about FreeBSD Cross Reference Online…and have to say thanks. nice read.

]]> Comment on PUFFS for FreeBSD? by anderson http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-7 anderson Tue, 27 Nov 2007 17:05:02 +0000 http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-7 tarfs is still on the plate, but development slowed to a crawl over the last few months as I have joined a startup and it is eating most of my time. :) I plan on finishing up tarfs first, then will be looking for another file system related project. I have thought about helping with bluffs also, but that's not up to me. tarfs is still on the plate, but development slowed to a crawl over the last few months as I have joined a startup and it is eating most of my time. :)

I plan on finishing up tarfs first, then will be looking for another file system related project. I have thought about helping with bluffs also, but that’s not up to me.

]]> Comment on PUFFS for FreeBSD? by ivoras http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-6 ivoras Tue, 27 Nov 2007 16:28:59 +0000 http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-6 If PUFFS is more stable then FreeBSD's existing port, and it's compatible with existing FUSE modules, then thumbs up! If PUFFS is more stable then FreeBSD’s existing port, and it’s compatible with existing FUSE modules, then thumbs up!

]]> Comment on PUFFS for FreeBSD? by Joel http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-5 Joel Tue, 27 Nov 2007 15:39:49 +0000 http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-5 what happened to tarfs? what happened to tarfs?

]]> Comment on PUFFS for FreeBSD? by jema http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-4 jema Tue, 27 Nov 2007 14:19:46 +0000 http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-4 Sure, that's really neat one! Sure, that’s really neat one!

]]> Comment on Utility File Systems by ivoras http://blogs.freebsdish.org/anderson/2007/10/14/utility-file-systems/#comment-2 ivoras Sat, 20 Oct 2007 00:07:58 +0000 http://blogs.freebsdish.org/anderson/2007/10/14/utility-file-systems/#comment-2 One thing that's not new is ditching the TCP/IP "sockets" API in favor of file system-like semantics. Historically, Unix has favored "everything is a file" approach and the sockets API was one of the first that didn't follow that path. I feel it's inconsistent that we can't just open /dev/fxp0 for reading and sniff the network, or open it for writing and inject packets. :) One thing that’s not new is ditching the TCP/IP “sockets” API in favor of file system-like semantics. Historically, Unix has favored “everything is a file” approach and the sockets API was one of the first that didn’t follow that path.

I feel it’s inconsistent that we can’t just open /dev/fxp0 for reading and sniff the network, or open it for writing and inject packets. :)

]]>