Bug 206035 - Bash3 only features in init scripts
Summary: Bash3 only features in init scripts
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-11 16:38 UTC by Daniel Qarras
Modified: 2014-03-17 03:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-09-11 17:18:07 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Daniel Qarras 2006-09-11 16:38:35 UTC
There is only one occasion of a bash3-only feature that prevents one to use
other shells as /bin/sh. It is at /etc/init.d/functions in function
resolve_dm_name() and it is the operator =~. Please consider using another
method to allow replacing of bash3 as /bin/sh.

Another thing causing some headaches is the style to source function libraries
in this manner:

cd /some/path
. functions

This does not work with all shells as /bin/sh, eg zsh, as they always require a
path:

cd /some/path
. ./functions

Please consider also fixing this one.

Thanks.

Comment 1 Bill Nottingham 2006-09-11 17:18:07 UTC
This is why there is:

Requires: bash >= 3.0

in the spec file.

'.' usage fixed in CVS.


Note You need to log in before you can comment on or make changes to this bug.