Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Feb 2017 22:32:35 +0100
From:      Polytropon <>
Subject:   Re: Variable assignment in sh
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Wed, 1 Feb 2017 15:56:03 -0500, James B. Byrne wrote:
> On Wed, February 1, 2017 15:16, Polytropon wrote:
> > In a worst case scenario, rely on what the system provides, and
> > don't try to override those defaults without good reasons and
> > sufficient precaution (like a statically linked /bin/bash for
> > example). There is almost nothing worse than a system that
> > successfully boots into single user mode, but then surprisingly
> > cannot start a shell... ;-)
> >
> I installed bash-static on all our FreeBSD hosts.  I would love to
> solely rely on what the base system provides but sadly I have never
> encountered a case with any OS where that is true.  And rewriting my
> admin scripts to sh from bash is a task that I simply do not have time
> for at the moment.

That is definitely a valid reason to "introduce" bash to the
SUM system. Especially when your scripts rely on functionality
that is present in bash, but not in sh, it's probably easier
to make bash available than to port and test the scripts.

That's where the real modularity of FreeBSD is helpful: With
the setting SHELL=<path to shell>, you can have cron use a
specific shell if the default scripting shell is not sufficient.

> Enumerating bash-static along with postfix, sudo, tmux, tree, vim,
> etc., that we require for FreeBSD is quite natural and poses no
> particular difficulty.

That's right. Oh, and add the Midnight Commander to that list.. :-)

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>