Comments on: Mac OS X hidden files: why??? http://www.gilluminate.com/2007/03/14/mac-os-x-hidden-files-why/ Tue, 07 Sep 2010 16:57:40 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Jason Gill http://www.gilluminate.com/2007/03/14/mac-os-x-hidden-files-why/comment-page-1/#comment-5256 Jason Gill Thu, 10 Apr 2008 00:51:52 +0000 http://blog.gillumiante.com/2007/03/14/mac-os-x-hidden-files-why#comment-5256 Thanks! I removed them. Thanks! I removed them.

]]> By: jampe http://www.gilluminate.com/2007/03/14/mac-os-x-hidden-files-why/comment-page-1/#comment-5255 jampe Wed, 09 Apr 2008 15:21:53 +0000 http://blog.gillumiante.com/2007/03/14/mac-os-x-hidden-files-why#comment-5255 the spambots got you..! the spambots got you..!

]]> By: Lewis Francis http://www.gilluminate.com/2007/03/14/mac-os-x-hidden-files-why/comment-page-1/#comment-367 Lewis Francis Wed, 14 Mar 2007 16:16:00 +0000 http://blog.gillumiante.com/2007/03/14/mac-os-x-hidden-files-why#comment-367 Yeah, they can be annoying on non-Mac machines. We bought a tool from this website to prevent our Mac users from writing these invisible files to our non-Mac servers: http://www.zeroonetwenty.com/blueharvest/#faq Yeah, they can be annoying on non-Mac machines. We bought a tool from this website to prevent our Mac users from writing these invisible files to our non-Mac servers:

http://www.zeroonetwenty.com/blueharvest/#faq

]]> By: Nick C http://www.gilluminate.com/2007/03/14/mac-os-x-hidden-files-why/comment-page-1/#comment-2170 Nick C Wed, 14 Mar 2007 16:16:00 +0000 http://blog.gillumiante.com/2007/03/14/mac-os-x-hidden-files-why#comment-2170 google 'disable DS_store' gave this: http://docs.info.apple.com/article.html?artnum=301711 google ‘disable DS_store’ gave this:

http://docs.info.apple.com/article.html?artnum=301711

]]> By: Nick http://www.gilluminate.com/2007/03/14/mac-os-x-hidden-files-why/comment-page-1/#comment-3420 Nick Wed, 14 Mar 2007 16:16:00 +0000 http://blog.gillumiante.com/2007/03/14/mac-os-x-hidden-files-why#comment-3420 I believe the reason relates to the fact that legacy Mac OS systems used a dual fork fiel system where each data file also had an associated metafile containing info like filetype and creator. Since Windows machines don't support this dual fork system, Apple has moved away from using resource forks so as to make documents work better across platforms, but they still need this data in order to enance the Mac desktop experience (if you save a file without an extention, the Mac still knows what application should open it, etc) and for this reason the data is saves in an invisible file. The files are tiny and harmless, so there's really no performance penalty - they just make your directory look a bit untidy. I believe the reason relates to the fact that legacy Mac OS systems used a dual fork fiel system where each data file also had an associated metafile containing info like filetype and creator. Since Windows machines don’t support this dual fork system, Apple has moved away from using resource forks so as to make documents work better across platforms, but they still need this data in order to enance the Mac desktop experience (if you save a file without an extention, the Mac still knows what application should open it, etc) and for this reason the data is saves in an invisible file. The files are tiny and harmless, so there’s really no performance penalty – they just make your directory look a bit untidy.

]]>