also you would wanna add requires: bash for initscripts rpm.
not sure how portable initscripts package was designed to be, would anyone
ever use it outside redhat? if not making a commitment to bash could be
reasonable.
just my .02
v
On Sun, 28 Sep 2003, Jonathan Bartlett wrote:
> The reason t
The reason that normal startup scripts don't, is that there's no guarantee
/bin/sh will point to bash, or even that bash is installed.
If you want to use bash, the first line should be /bin/bash instead of
/bin/sh, so it's obvious it needs bash specifically.
Jon
On Sun, 28 Sep 2003, [iso-8859-1]
Hello,
A common problem is corrupt software. This can be due to improper
shutdowns, careless administrators/developers, etc. Many times hardware is
not to blame and reinstalling the OS is all that is needed.
I would like to use Parted to reconstruct several partions from image files
in the even
On Sunday, Sep 28th 2003 at 14:31 +0100, quoth Manoj Kumar:
=>Is there any reason not to use bash features in init
=>scripts?
=>Consider, for example, this fragment from
=>/etc/sysconfig/network-scripts/ifup-post:
=>
=>DEVICETYPE=`echo $DEVICE | sed "s/[0-9]*$//"`
=>REALDEVICE=`echo $DEVIC
Is there any reason not to use bash features in init
scripts?
Consider, for example, this fragment from
/etc/sysconfig/network-scripts/ifup-post:
DEVICETYPE=`echo $DEVICE | sed "s/[0-9]*$//"`
REALDEVICE=`echo $DEVICE | sed 's/:.*//g'`
if echo $DEVICE | grep -q ':' ; then
ISALIA
