Re: bash, dash and sh
On Wed, Apr 22, 2015 at 11:43:17PM -0600, Glenn English wrote:
>
> On Apr 22, 2015, at 9:22 PM, Bob Proulx <bob@proulx.com> wrote:
>
> > jeremy bentham wrote:
> >> I am finally abandonning my fifteen-year-old computer and Lenny
> >> for a six (?) year old used Gateway 2802 (as a Bad Consumer
> >> (tm) I never buy anything new if I can avoid it) and, right now,
> >> it has a start at Wheezy on it.
> As a consumer running an elderly server with Lenny on it, I too
> congratulate you -- Wheezy is more fun than Lenny. They fixed a
> lot of stuff that gave me trouble with Lenny.
> >> I have a bunch of scripts
> >>
> >> (ls -1 ~/bin | wc
> >> 138 139 1302)
> >>
> >> with the first line #!/bin/sh that use bashisms, and the above
> >> would be a lot easier than editing each one (of course, maybe
> >> just editing each one would be easier than doing this ;-) ).
> May I suggest just changing the pointer from Dash back to Bash.
> You sound like somebody that stays with a release for a while,
> and this is would be a lot less work than editing all those
> scripts.
I probably wasn't clear enough in my Real Question, which is,
will doing this--what I really want--Seriously Break Something?
Lots of stuff uses "/bin/sh".
> Or maybe editing the top line of them from #!/bin/sh to
> #!/bin/bash, for the time being.
And this was what I was trying to avoid, while possibly learning
something without having to type "man dash". Terminal Laziness
(again, (TM)).
I'll use this reply to say, thanks for the suggestions--
especially that sed command line. I know about sed, of course,
but I use it so seldom that I basically have to relearn it every
time I need it.
> --
> Glenn English
--
Dave Williams When the professional politicians decide to
dnw@eskimo.com solve a problem, the best we can hope for is
that they won't make it worse.
Reply to: