<?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: Getting Back to (Search) Basics</title>
	<atom:link href="http://systemsboy.com/2005/05/getting-back-to-search-basics.html/feed" rel="self" type="application/rss+xml" />
	<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html</link>
	<description>Big, Honkin' Systems Stuff</description>
	<lastBuildDate>Sun, 29 Apr 2012 08:52:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-22</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 21 Jan 2006 11:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-22</guid>
		<description>Many comments and URGES to make this needed small addition to spotlight have to be made to APPLE.&lt;br/&gt;This can be done via Safari Menu where it says &quot;Report an error to Apple&quot;; It is an error! This quote hint is of some use, my Provider is called 1&amp;1, and if I enter that in Spotlight it finds over 10500 items. If I enter &quot;1&amp;1, I get 12 items, which is a lot better. I have helped myself with Utility FileBuddy, it searches fast, about 3 seconds for 80 GB on a 800 MHz-Mac  (wheras some FindFile Programs take 18 Seconds).  So mention it to Apple!!</description>
		<content:encoded><![CDATA[<p>Many comments and URGES to make this needed small addition to spotlight have to be made to APPLE.<br />This can be done via Safari Menu where it says &#8220;Report an error to Apple&#8221;; It is an error! This quote hint is of some use, my Provider is called 1&#038;1, and if I enter that in Spotlight it finds over 10500 items. If I enter &#8220;1&#038;1, I get 12 items, which is a lot better. I have helped myself with Utility FileBuddy, it searches fast, about 3 seconds for 80 GB on a 800 MHz-Mac  (wheras some FindFile Programs take 18 Seconds).  So mention it to Apple!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: systemsboy</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-21</link>
		<dc:creator>systemsboy</dc:creator>
		<pubDate>Thu, 22 Dec 2005 18:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-21</guid>
		<description>Yeah, that&#039;s great. Except that it doesn&#039;t work. It is by no means a name-only search. It is (as the poster said) name/keyword. Try it. You&#039;ll get LOTS of results that don&#039;t contain your term in the name. If this works for you, great. It doesn&#039;t for me.</description>
		<content:encoded><![CDATA[<p>Yeah, that&#8217;s great. Except that it doesn&#8217;t work. It is by no means a name-only search. It is (as the poster said) name/keyword. Try it. You&#8217;ll get LOTS of results that don&#8217;t contain your term in the name. If this works for you, great. It doesn&#8217;t for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-20</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 22 Dec 2005 15:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-20</guid>
		<description>I was about to try this when half way down the page I saw this tidbit....&lt;br/&gt;&lt;br/&gt;FYI, you can do a name/keyword only search by putting your search string in double-quotes (actually only the front double-quote is needed). This isn&#039;t exactly name-only, but it&#039;s pretty close. &lt;br/&gt;&lt;br/&gt;...   That solves the whole problem soooooo easily!!!   You need to put that at the top of the page!    I can&#039;t believe I&#039;ve been suffering with spotlight for so long when all I needed was a little quote mark.</description>
		<content:encoded><![CDATA[<p>I was about to try this when half way down the page I saw this tidbit&#8230;.</p>
<p>FYI, you can do a name/keyword only search by putting your search string in double-quotes (actually only the front double-quote is needed). This isn&#8217;t exactly name-only, but it&#8217;s pretty close. </p>
<p>&#8230;   That solves the whole problem soooooo easily!!!   You need to put that at the top of the page!    I can&#8217;t believe I&#8217;ve been suffering with spotlight for so long when all I needed was a little quote mark.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: systemsboy</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-19</link>
		<dc:creator>systemsboy</dc:creator>
		<pubDate>Sat, 10 Dec 2005 22:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-19</guid>
		<description>Someone a long time ago wrote:&lt;br/&gt;&lt;br/&gt;&quot;p.s. however, pasting the shell into a plaint text file, saving and chmodding it doesnt work (cannot open binary file...). what could be the problem? the encoding? i will try to enter the commands directly into the terminal...&quot;&lt;br/&gt;&lt;br/&gt;I&#039;ve discovered the source, and the cure for this problem. The problem is the browser. Copying the script from Firefox (which I now use) will put non-UNIX line breaks throughout the text file. The solution is this:&lt;br/&gt;1) Copy the script text.&lt;br/&gt;2) Paste it into a Rich Text document in TextEdit.&lt;br/&gt;3) Then hit &quot;Format-&gt;Make Plain Text&quot; (command-shift-t).&lt;br/&gt;4) Then save the file out and set the permissions.&lt;br/&gt;&lt;br/&gt;Converting the text this way (in TextEdit) converts the line breaks to something usable by the shell.&lt;br/&gt;&lt;br/&gt;Mystery solved. (Whew!)&lt;br/&gt;&lt;br/&gt;-systemsboy</description>
		<content:encoded><![CDATA[<p>Someone a long time ago wrote:</p>
<p>&#8220;p.s. however, pasting the shell into a plaint text file, saving and chmodding it doesnt work (cannot open binary file&#8230;). what could be the problem? the encoding? i will try to enter the commands directly into the terminal&#8230;&#8221;</p>
<p>I&#8217;ve discovered the source, and the cure for this problem. The problem is the browser. Copying the script from Firefox (which I now use) will put non-UNIX line breaks throughout the text file. The solution is this:<br />1) Copy the script text.<br />2) Paste it into a Rich Text document in TextEdit.<br />3) Then hit &#8220;Format->Make Plain Text&#8221; (command-shift-t).<br />4) Then save the file out and set the permissions.</p>
<p>Converting the text this way (in TextEdit) converts the line breaks to something usable by the shell.</p>
<p>Mystery solved. (Whew!)</p>
<p>-systemsboy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Schmidt</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-18</link>
		<dc:creator>Ryan Schmidt</dc:creator>
		<pubDate>Thu, 17 Nov 2005 19:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-18</guid>
		<description>What I like best is that the script calls me &lt;i&gt;Tiger&lt;/i&gt;.&lt;br/&gt;&lt;br/&gt;Spotlight has made my PowerBook (G4 1.5GHz, 80-GB 5400-RPM HD) miserable since installing 10.4.0 so it&#039;s been entirely off, and I&#039;m elated to get filename-based finding working again. Thanks also for the imaginative tip with the disk image for Mail. I&#039;ll definitely try that.</description>
		<content:encoded><![CDATA[<p>What I like best is that the script calls me <i>Tiger</i>.</p>
<p>Spotlight has made my PowerBook (G4 1.5GHz, 80-GB 5400-RPM HD) miserable since installing 10.4.0 so it&#8217;s been entirely off, and I&#8217;m elated to get filename-based finding working again. Thanks also for the imaginative tip with the disk image for Mail. I&#8217;ll definitely try that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: systemsboy</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-17</link>
		<dc:creator>systemsboy</dc:creator>
		<pubDate>Sun, 11 Sep 2005 16:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-17</guid>
		<description>Bruce,&lt;br/&gt;&lt;br/&gt;It&#039;s strange that the script is not behaving correctly for you. The script, as you know, simply runs mdutil -- the same command you ran -- on all drives and partitions listed in /Volumes. The extra &quot;/&quot; is just a precautionary measure to make sure the command runs on the root (system) partition as the system partition was not linked in older versions of OSX the way it is Tiger. It&#039;s probably not necessary, but by the same token, should not cause any problems. Definitely somthing strange going on.&lt;br/&gt;&lt;br/&gt;I agree, though, that the script could be a bit more user-friendly. I was even planning on posting one that disables Spotlight on a per-drive basis, but I just haven&#039;t had time. It&#039;s pretty easy, though, as you discovered. To enable, just type:&lt;br/&gt;sudo mdutil -i on /Drag/Your/Drive&lt;br/&gt;&lt;br/&gt;To disable:&lt;br/&gt;sudo mdutil -i off /Drag/Your/Drive&lt;br/&gt;&lt;br/&gt;Hopefully, by the time I get around to posting a smarter script, Apple will have fixed Spotlight and made my script unnecessary. If not, perhaps I&#039;ll write a new, better disable/enable Spotlight script.&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;systemsboy</description>
		<content:encoded><![CDATA[<p>Bruce,</p>
<p>It&#8217;s strange that the script is not behaving correctly for you. The script, as you know, simply runs mdutil &#8212; the same command you ran &#8212; on all drives and partitions listed in /Volumes. The extra &#8220;/&#8221; is just a precautionary measure to make sure the command runs on the root (system) partition as the system partition was not linked in older versions of OSX the way it is Tiger. It&#8217;s probably not necessary, but by the same token, should not cause any problems. Definitely somthing strange going on.</p>
<p>I agree, though, that the script could be a bit more user-friendly. I was even planning on posting one that disables Spotlight on a per-drive basis, but I just haven&#8217;t had time. It&#8217;s pretty easy, though, as you discovered. To enable, just type:<br />sudo mdutil -i on /Drag/Your/Drive</p>
<p>To disable:<br />sudo mdutil -i off /Drag/Your/Drive</p>
<p>Hopefully, by the time I get around to posting a smarter script, Apple will have fixed Spotlight and made my script unnecessary. If not, perhaps I&#8217;ll write a new, better disable/enable Spotlight script.</p>
<p>Thanks,<br />systemsboy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Young</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-16</link>
		<dc:creator>Bruce Young</dc:creator>
		<pubDate>Sat, 10 Sep 2005 23:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-16</guid>
		<description>Confirming:  even though my 3 other partition volumes did not get indexing re-enabled with the script (while boot vol did), using the manual mdutil command did get the indexing find-by-content re-enabled.&lt;br/&gt;&lt;br/&gt;Thus: &quot;sudo mdutil -i on /Volumes/D-Data&quot; does get indexed find-by-content activated.&lt;br/&gt;(again, tested by creation of small text text file with unique nonsense word)&lt;br/&gt;&lt;br/&gt;The only difference with your command is mine does not have an extra &quot;/&quot; in it...&lt;br/&gt;Tested with the extra &quot;/&quot; removed, and this re-enabled indexing on three vols (which is an improvement on first results), but got the &quot;Could not set indexing...&quot; on the fourth volume. Something strange here.  Oh well, at least the command line mdutil -i on gets it all back.</description>
		<content:encoded><![CDATA[<p>Confirming:  even though my 3 other partition volumes did not get indexing re-enabled with the script (while boot vol did), using the manual mdutil command did get the indexing find-by-content re-enabled.</p>
<p>Thus: &#8220;sudo mdutil -i on /Volumes/D-Data&#8221; does get indexed find-by-content activated.<br />(again, tested by creation of small text text file with unique nonsense word)</p>
<p>The only difference with your command is mine does not have an extra &#8220;/&#8221; in it&#8230;<br />Tested with the extra &#8220;/&#8221; removed, and this re-enabled indexing on three vols (which is an improvement on first results), but got the &#8220;Could not set indexing&#8230;&#8221; on the fourth volume. Something strange here.  Oh well, at least the command line mdutil -i on gets it all back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Young</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-15</link>
		<dc:creator>Bruce Young</dc:creator>
		<pubDate>Sat, 10 Sep 2005 23:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-15</guid>
		<description>Oops, I mean, it only re-enabled on my boot volume. the other three returned a message: &quot;Could not set indexing status for volume.&quot;&lt;br/&gt;  I verified this with a new test text file containing a unique nonsense word, which was found on my boot volume, but not on the other vols.</description>
		<content:encoded><![CDATA[<p>Oops, I mean, it only re-enabled on my boot volume. the other three returned a message: &#8220;Could not set indexing status for volume.&#8221;<br />  I verified this with a new test text file containing a unique nonsense word, which was found on my boot volume, but not on the other vols.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Young</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-14</link>
		<dc:creator>Bruce Young</dc:creator>
		<pubDate>Sat, 10 Sep 2005 23:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-14</guid>
		<description>Follow up on the disable, re-enable on my main HD.&lt;br/&gt;It re-enabled indexing for two of my partition/volumes, which are bootable &amp; journaled. But did not re-enable for the two non-journaled data-only partition/volumes.&lt;br/&gt;&lt;br/&gt;So perhaps I have to enable journaling on the data partition/volumes to get the indexing back?&lt;br/&gt;&lt;br/&gt;or perhaps I should use the mdutil command directly on them?</description>
		<content:encoded><![CDATA[<p>Follow up on the disable, re-enable on my main HD.<br />It re-enabled indexing for two of my partition/volumes, which are bootable &#038; journaled. But did not re-enable for the two non-journaled data-only partition/volumes.</p>
<p>So perhaps I have to enable journaling on the data partition/volumes to get the indexing back?</p>
<p>or perhaps I should use the mdutil command directly on them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Young</title>
		<link>http://systemsboy.com/2005/05/getting-back-to-search-basics.html/comment-page-1#comment-13</link>
		<dc:creator>Bruce Young</dc:creator>
		<pubDate>Sat, 10 Sep 2005 23:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://systemsboy.com/2005/05/getting-back-to-search-basics/#comment-13</guid>
		<description>I would add the phrases: &quot;This applies to ALL MOUNTED VOLUMES!&quot;  and  &quot;Control-C cancels the operation.&quot;&lt;br/&gt;&lt;br/&gt;I have modified a copy of the script to just apply to my external FireWire connected HDs, since I have a unique prefix for those volume names; ie: &quot;/Volumes/WD160*&quot;&lt;br/&gt;&lt;br/&gt;Seems to work during command execution.&lt;br/&gt;... checking on a test &quot;name&quot; search on the external HD ... ... Yes, file name found! &lt;br/&gt;&lt;br/&gt;Yay!&lt;br/&gt;FINALLY I can search on my external HD without having to have the Gigabytes indexed.&lt;br/&gt;&lt;br/&gt;P.S., the chmod I applied to first script seems to be carried over to the copy I made for my external HD, even after I modified it.&lt;br/&gt;&lt;br/&gt;THank you.  B.Y.</description>
		<content:encoded><![CDATA[<p>I would add the phrases: &#8220;This applies to ALL MOUNTED VOLUMES!&#8221;  and  &#8220;Control-C cancels the operation.&#8221;</p>
<p>I have modified a copy of the script to just apply to my external FireWire connected HDs, since I have a unique prefix for those volume names; ie: &#8220;/Volumes/WD160*&#8221;</p>
<p>Seems to work during command execution.<br />&#8230; checking on a test &#8220;name&#8221; search on the external HD &#8230; &#8230; Yes, file name found! </p>
<p>Yay!<br />FINALLY I can search on my external HD without having to have the Gigabytes indexed.</p>
<p>P.S., the chmod I applied to first script seems to be carried over to the copy I made for my external HD, even after I modified it.</p>
<p>THank you.  B.Y.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 2/13 queries in 0.009 seconds using disk: basic
Object Caching 366/366 objects using disk: basic

Served from: systemsboy.com @ 2012-05-18 10:09:51 -->
