<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Analyzing a memory card with MacOS X</title>
	<atom:link href="http://blogs.23.nu/c0re/2005/10/antville-10057/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.23.nu/c0re/2005/10/antville-10057/</link>
	<description>Just another blogs.23.nu TNG weblog</description>
	<lastBuildDate>Wed, 10 Mar 2010 06:08:29 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cklein</title>
		<link>http://blogs.23.nu/c0re/2005/10/antville-10057/comment-page-1/#comment-38</link>
		<dc:creator>cklein</dc:creator>
		<pubDate>Wed, 15 Oct 2008 22:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://3.blogs.23.nu/c0re/2005/10/antville-10057/#comment-38</guid>
		<description>


You can get the patch &lt;a href=&quot;http://untergrund.bewaff.net/~chris/c0de/diskarbitrationd.diff&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.


 This comment was originally posted on 20051006T18:33:20</description>
		<content:encoded><![CDATA[<p>You can get the patch <a href="http://untergrund.bewaff.net/~chris/c0de/diskarbitrationd.diff" rel="nofollow">here</a>.</p>
<p> This comment was originally posted on 20051006T18:33:20</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jens</title>
		<link>http://blogs.23.nu/c0re/2005/10/antville-10057/comment-page-1/#comment-36</link>
		<dc:creator>jens</dc:creator>
		<pubDate>Wed, 15 Oct 2008 22:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://3.blogs.23.nu/c0re/2005/10/antville-10057/#comment-36</guid>
		<description>How about...

How about...
... patching this: http://blog.annulator.de/articles/2005/06/09/hastalads_store-nie-wieder-ds_store-dateien


 This comment was originally posted on 20051006T11:51:23</description>
		<content:encoded><![CDATA[<p>How about&#8230;</p>
<p>How about&#8230;<br />
&#8230; patching this: <a href="http://blog.annulator.de/articles/2005/06/09/hastalads_store-nie-wieder-ds_store-dateien" rel="nofollow">http://blog.annulator.de/articles/2005/06/09/hastalads_store-nie-wieder-ds_store-dateien</a></p>
<p> This comment was originally posted on 20051006T11:51:23</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cklein</title>
		<link>http://blogs.23.nu/c0re/2005/10/antville-10057/comment-page-1/#comment-37</link>
		<dc:creator>cklein</dc:creator>
		<pubDate>Wed, 15 Oct 2008 22:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://3.blogs.23.nu/c0re/2005/10/antville-10057/#comment-37</guid>
		<description>


Very nice software, but I guess it won&#039;t work:
I was wrong in the orignal posting that Finder.app creates
the trashcan directories, it&#039;s the diskarbitrationd itself,
see function &lt;code&gt;void _DAMountCreateTrashFolder( DADiskRef disk, CFURLRef mountpoint )&lt;/code&gt; in &lt;code&gt;DAMount.c&lt;/code&gt;.


 This comment was originally posted on 20051006T17:04:44</description>
		<content:encoded><![CDATA[<p>Very nice software, but I guess it won&#8217;t work:<br />
I was wrong in the orignal posting that Finder.app creates<br />
the trashcan directories, it&#8217;s the diskarbitrationd itself,<br />
see function <code>void _DAMountCreateTrashFolder( DADiskRef disk, CFURLRef mountpoint )</code> in <code>DAMount.c</code>.</p>
<p> This comment was originally posted on 20051006T17:04:44</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cklein</title>
		<link>http://blogs.23.nu/c0re/2005/10/antville-10057/comment-page-1/#comment-35</link>
		<dc:creator>cklein</dc:creator>
		<pubDate>Wed, 15 Oct 2008 22:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://3.blogs.23.nu/c0re/2005/10/antville-10057/#comment-35</guid>
		<description>


I read TONS of useless documentation, about
all kind of ancient MacOS X versions and tools
like autodiskmount (&lt;cite&gt;This command is deprecated and exists only for backwards compatibility.&lt;/cite&gt;)
and just before giving up, I found this tool:
&lt;code&gt;/usr/sbin/diskarbitrationd&lt;/code&gt; that is started
from a startscript in &lt;code&gt;/priv/etc/mach_init.d/diskarbitrationd.plist&lt;/code&gt;. I still have to find out who restarts the program after killing it, for testing purposes, I renamed the program and started it with the &lt;b&gt;-d&lt;/b&gt; flag. Here is the output:

diskarbitration [2897] -&gt; diskarbitration [2897]
  probed disk, id = /dev/disk2s1, with msdos, ongoing.
  probed disk, id = /dev/disk2s1, with msdos, success.
  mounted disk, id = /dev/disk2s1, ongoing.
  mounted disk, id = /dev/disk2s1, success.
.

Patching the diskarbitrationd seems easy, but the
mechanism itself doesn&#039;t. I&#039;m thinking about preventing
mounting of FAT filesystems, or even some execution prevention by a lock file.


 This comment was originally posted on 20051005T23:38:28</description>
		<content:encoded><![CDATA[<p>I read TONS of useless documentation, about<br />
all kind of ancient MacOS X versions and tools<br />
like autodiskmount (<cite>This command is deprecated and exists only for backwards compatibility.</cite>)<br />
and just before giving up, I found this tool:<br />
<code>/usr/sbin/diskarbitrationd</code> that is started<br />
from a startscript in <code>/priv/etc/mach_init.d/diskarbitrationd.plist</code>. I still have to find out who restarts the program after killing it, for testing purposes, I renamed the program and started it with the <b>-d</b> flag. Here is the output:</p>
<p>diskarbitration [2897] -&gt; diskarbitration [2897]<br />
  probed disk, id = /dev/disk2s1, with msdos, ongoing.<br />
  probed disk, id = /dev/disk2s1, with msdos, success.<br />
  mounted disk, id = /dev/disk2s1, ongoing.<br />
  mounted disk, id = /dev/disk2s1, success.<br />
.</p>
<p>Patching the diskarbitrationd seems easy, but the<br />
mechanism itself doesn&#8217;t. I&#8217;m thinking about preventing<br />
mounting of FAT filesystems, or even some execution prevention by a lock file.</p>
<p> This comment was originally posted on 20051005T23:38:28</p>
]]></content:encoded>
	</item>
</channel>
</rss>
