<div dir="ltr">Thanks for the response;<div><br></div><div><span style="font-size:12.8000001907349px">If this is not just a contrived question to learn about</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">argument quoting,</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"> <i>Actually, I just wanted to make sure grep should be returning the same data for that particular statement with or without quotes. </i></span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"> "find" is usually a more reliable way to</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">retrieve files matching criteria. For example, to see</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">everything under /usr/bin with the setuid bit set, you can</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">do the following:</span><br style="font-size:12.8000001907349px"><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">find /usr/bin -perm -u+s</span></div><div><br></div><div><i>Interestingly, the manual we are working through suggested using find with the -perm switch but followed by 4000 would give the same result as -u+s, which, of course, it does not. Which led me to question the assertion that quotes were necessary for the grep of ls.</i><br style="font-size:12.8000001907349px"><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">Note that find works recursively, but you can limit its</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">depth with the -maxdepth option.</span><br style="font-size:12.8000001907349px"><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">Take a look at the man page for "find" as it has tests</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">available for just about anything you can think of.</span><br></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"><i>Thanks again.</i></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 15, 2015 at 11:34 AM, Matt Meinwald <span dir="ltr"><<a href="mailto:meinwald.1@osu.edu" target="_blank">meinwald.1@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 04/15/2015 08:51 AM, zach villers wrote:<br>
> Is there a difference between;<br>
><br>
> ls -l | grep ^...s<br>
><br>
> AND<br>
><br>
> ls -l | grep "^...s"<br>
><br>
> *trying to find files with setuid permission*<br>
><br>
> A trainer told me using quotes with the grep statement was necessary,<br>
> but it doesn't seem to be.<br>
><br>
> Thanks!<br>
><br>
<br>
</div></div>If this is not just a contrived question to learn about<br>
argument quoting, "find" is usually a more reliable way to<br>
retrieve files matching criteria. For example, to see<br>
everything under /usr/bin with the setuid bit set, you can<br>
do the following:<br>
<br>
find /usr/bin -perm -u+s<br>
<br>
Note that find works recursively, but you can limit its<br>
depth with the -maxdepth option.<br>
<br>
Take a look at the man page for "find" as it has tests<br>
available for just about anything you can think of.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</div></div></blockquote></div><br></div>