<?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: Linux find command</title>
	<atom:link href="http://www.thelinuxblog.com/linux-find-command/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thelinuxblog.com/linux-find-command/</link>
	<description>The Linux Blog, General Linux, Shell Scripts</description>
	<lastBuildDate>Fri, 17 May 2013 01:16:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: abhilash</title>
		<link>http://www.thelinuxblog.com/linux-find-command/comment-page-1/#comment-5090</link>
		<dc:creator>abhilash</dc:creator>
		<pubDate>Tue, 21 Dec 2010 18:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/#comment-5090</guid>
		<description><![CDATA[how to find all files contating a particular text 
for eg
i want to list all files in folder /home which contains &quot;linux&quot;]]></description>
		<content:encoded><![CDATA[<p>how to find all files contating a particular text<br />
for eg<br />
i want to list all files in folder /home which contains &#8220;linux&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Linux Blog &#187; Linux History Command</title>
		<link>http://www.thelinuxblog.com/linux-find-command/comment-page-1/#comment-4368</link>
		<dc:creator>The Linux Blog &#187; Linux History Command</dc:creator>
		<pubDate>Wed, 17 Nov 2010 09:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/#comment-4368</guid>
		<description><![CDATA[[...] are doomed to repeat typing. A lot. Seriously, the history command can help you remember the exact Linux find command with the intricate search options you typed a while ago. It could help you open up your x2x or [...]]]></description>
		<content:encoded><![CDATA[<p>[...] are doomed to repeat typing. A lot. Seriously, the history command can help you remember the exact Linux find command with the intricate search options you typed a while ago. It could help you open up your x2x or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anarchy1</title>
		<link>http://www.thelinuxblog.com/linux-find-command/comment-page-1/#comment-4362</link>
		<dc:creator>anarchy1</dc:creator>
		<pubDate>Wed, 17 Nov 2010 04:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/#comment-4362</guid>
		<description><![CDATA[true grep isnt required but for anyone like me ..
I just love grep if you dont know the exact name of the file lets say the file is called 
foobar1.txt

and all i can remember is it starts with 
foob 
then find wont necessarily find the resault you want
while 
find \ &#124; grep -i foob
will probably give you the closest match with no effort, and if you have multiple foobar.txt for example
foobar1.txt
2foobar.txt
and 
101foobar.txt
then grep will show you these easy.
and color the exact mach to 
what more could i ask for..?]]></description>
		<content:encoded><![CDATA[<p>true grep isnt required but for anyone like me ..<br />
I just love grep if you dont know the exact name of the file lets say the file is called<br />
foobar1.txt</p>
<p>and all i can remember is it starts with<br />
foob<br />
then find wont necessarily find the resault you want<br />
while<br />
find \ | grep -i foob<br />
will probably give you the closest match with no effort, and if you have multiple foobar.txt for example<br />
foobar1.txt<br />
2foobar.txt<br />
and<br />
101foobar.txt<br />
then grep will show you these easy.<br />
and color the exact mach to<br />
what more could i ask for..?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheLinuxBlog.com</title>
		<link>http://www.thelinuxblog.com/linux-find-command/comment-page-1/#comment-4008</link>
		<dc:creator>TheLinuxBlog.com</dc:creator>
		<pubDate>Mon, 08 Nov 2010 15:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/#comment-4008</guid>
		<description><![CDATA[Hey Kaleb, you don&#039;t need to use grep to find a file, if your filename is blaa.txt you can do find / -name &quot;blaa.txt&quot; or find / -iname &quot;blaa.txt&quot;]]></description>
		<content:encoded><![CDATA[<p>Hey Kaleb, you don&#8217;t need to use grep to find a file, if your filename is blaa.txt you can do find / -name &#8220;blaa.txt&#8221; or find / -iname &#8220;blaa.txt&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kaleb</title>
		<link>http://www.thelinuxblog.com/linux-find-command/comment-page-1/#comment-3971</link>
		<dc:creator>kaleb</dc:creator>
		<pubDate>Sun, 07 Nov 2010 12:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/#comment-3971</guid>
		<description><![CDATA[pretty good and its deffintly one of the more commonly ignored commands and it is deffintly a great tool to have in your box. but what im seeing here in your article is that you forgot to mention grep and pipe. while not directly related to the find command they are related to narrowing down resaults. for example when i want to find something i typicly use 

&lt;code&gt;find / &#124; grep blaa.txt&lt;/code&gt;

find / will find every file on the filesystem which in linux is a fairly instant resualt but is huge and it doesnt show me anything i want to know. but i can easiy add &#124; grep blaa.txt which will find that file anywhere on the filesystem almost instantly.

just my two cents on the subject]]></description>
		<content:encoded><![CDATA[<p>pretty good and its deffintly one of the more commonly ignored commands and it is deffintly a great tool to have in your box. but what im seeing here in your article is that you forgot to mention grep and pipe. while not directly related to the find command they are related to narrowing down resaults. for example when i want to find something i typicly use </p>
<p><code>find / | grep blaa.txt</code></p>
<p>find / will find every file on the filesystem which in linux is a fairly instant resualt but is huge and it doesnt show me anything i want to know. but i can easiy add | grep blaa.txt which will find that file anywhere on the filesystem almost instantly.</p>
<p>just my two cents on the subject</p>
]]></content:encoded>
	</item>
</channel>
</rss>
