<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: PUFFS for FreeBSD?</title>
	<atom:link href="http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/</link>
	<description>Just another FreeBSD Committers Blogs weblog</description>
	<pubDate>Tue, 06 Jan 2009 15:40:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Ale</title>
		<link>http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-30</link>
		<dc:creator>Ale</dc:creator>
		<pubDate>Mon, 25 Aug 2008 17:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-30</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Hello.</p>
<p>I&#8217;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 &#8220;Known Problems&#8221;.</p>
<p>In short (I&#8217;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 &#8220;file not found&#8221; 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.</p>
<p>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.</p>
<p>Thanks,<br />
Ale</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anderson</title>
		<link>http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-7</link>
		<dc:creator>anderson</dc:creator>
		<pubDate>Tue, 27 Nov 2007 17:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-7</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.  <img src='http://blogs.freebsdish.org/anderson/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>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&#8217;s not up to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ivoras</title>
		<link>http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-6</link>
		<dc:creator>ivoras</dc:creator>
		<pubDate>Tue, 27 Nov 2007 16:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-6</guid>
		<description>If PUFFS is more stable then FreeBSD's existing port, and it's compatible with existing FUSE modules, then thumbs up!</description>
		<content:encoded><![CDATA[<p>If PUFFS is more stable then FreeBSD&#8217;s existing port, and it&#8217;s compatible with existing FUSE modules, then thumbs up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-5</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Tue, 27 Nov 2007 15:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-5</guid>
		<description>what happened to tarfs?</description>
		<content:encoded><![CDATA[<p>what happened to tarfs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jema</title>
		<link>http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-4</link>
		<dc:creator>jema</dc:creator>
		<pubDate>Tue, 27 Nov 2007 14:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/anderson/2007/11/27/puffs-for-freebsd/#comment-4</guid>
		<description>Sure, that's really neat one!</description>
		<content:encoded><![CDATA[<p>Sure, that&#8217;s really neat one!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
