Re: [OE-core] [PATCH 1/1] sysvinit: start .sh scripts correctly

2013-02-26 Thread Burton, Ross
On 26 February 2013 01:39, qi.c...@windriver.com wrote: - - case $1 in - *.sh) - # Source shell script for speed. - ( - trap - INT QUIT TSTP - scriptname=$1 - shift -

Re: [OE-core] [PATCH 1/1] sysvinit: start .sh scripts correctly

2013-02-26 Thread ChenQi
On 02/26/2013 07:04 PM, Burton, Ross wrote: On 26 February 2013 01:39, qi.c...@windriver.com wrote: - - case $1 in - *.sh) - # Source shell script for speed. - ( - trap - INT QUIT TSTP - scriptname=$1 -

[OE-core] [PATCH 1/1] sysvinit: start .sh scripts correctly

2013-02-25 Thread Qi.Chen
From: Chen Qi qi.c...@windriver.com Previously, scripts which end with '.sh' were sourced, so the arguments like 'start' and 'stop' were just ignored. This resulted in some init scripts not being able to start correctly. For example, sourcing hwclock.sh in busybox actually does nothing. It

Re: [OE-core] [PATCH 1/1] sysvinit: start .sh scripts correctly

2013-02-25 Thread Saul Wold
On 02/25/2013 05:39 PM, qi.c...@windriver.com wrote: From: Chen Qi qi.c...@windriver.com Previously, scripts which end with '.sh' were sourced, so the arguments like 'start' and 'stop' were just ignored. This resulted in some init scripts not being able to start correctly. For example,

Re: [OE-core] [PATCH 1/1] sysvinit: start .sh scripts correctly

2013-02-25 Thread ChenQi
On 02/26/2013 10:00 AM, Saul Wold wrote: On 02/25/2013 05:39 PM, qi.c...@windriver.com wrote: From: Chen Qi qi.c...@windriver.com Previously, scripts which end with '.sh' were sourced, so the arguments like 'start' and 'stop' were just ignored. This resulted in some init scripts not being