On 1/5/2012 4:44 AM, Patrick O'Callaghan wrote:
You might be surprised. For some of us, the first question is "how can I
do this with the Shell?" Only if the answer is "you can't", or "it would
be too slow", do we resort to programming. The whole Unix toolkit
philosophy is based on this, or at l
On Wed, 2012-01-04 at 16:59 -0800, Paul Allen Newell wrote:
> Somehow I just never hit the need for using the shell above and beyond
> a
> quick whack to get me through something that couldn't be done with a
> programming language. Its one of those things that I would regret not
> having picked
On Wed, 2012-01-04 at 19:06 -0600, Dave Ihnat wrote:
> An interesting little ditty, if you don't know it. Steve Bourne
> really
> loved ALGOL. So much so that he wrote the original shell *in*
> ALGOL...kind
> of. It was ostensibly 'C'...but he created an entire set of #defines
> to
> allow him t
On 1/4/2012 5:06 PM, Dave Ihnat wrote:
On Wed, Jan 04, 2012 at 04:59:29PM -0800, Paul Allen Newell wrote:
I've always tried to make sure everything is lowest common
denominator between Microsoft and Linux unless there is a good
reason. I learned the hard way the first time I had to port from
Lin
On Wed, Jan 04, 2012 at 04:59:29PM -0800, Paul Allen Newell wrote:
> I've always tried to make sure everything is lowest common
> denominator between Microsoft and Linux unless there is a good
> reason. I learned the hard way the first time I had to port from
> Linux to Microsoft. I really dislike
[inline]
On 1/4/2012 4:08 PM, Dave Ihnat wrote:
Just be aware if you've any directory paths with funny characters in
them--especially spaces (think Microsoft files hosted on your
filesystem)--xargs has kittens. There are ways around that, but.
I've always tried to make sure everything is low
On Wed, Jan 04, 2012 at 03:51:01PM -0800, Paul Allen Newell wrote:
> Your suggestion regarding xargs helped. This is the second time its
> been suggested to me and I am going to go off and read about it as I
> get a sense it will make my life alot easier.
Just be aware if you've any directory path
On 1/4/2012 1:38 PM, Patrick O'Callaghan wrote:
They're quite different but overlap to some extent. 'find' is the
reliable way of searching the current system according to a whole bunch
of criteria (man find). 'locate' just does a quick search on a database
which is updated regularly (usually ni
On 1/4/2012 12:46 AM, Ed Greshko wrote:
Well, we always will put the files/command (end product of compilation)
in directories that tend to clue one in on the purpose. /bin /sbin
/usr/bin, etc. And, we only put +x on the files that really need them.
Hardly ever needing to use the "file" comman
