[BusyBox 0001149]: Problem with '[' command used internal to busybox ash
Eric Spakman
E.Spakman at inter.nl.net
Tue Jan 9 21:56:06 UTC 2007
Hi Bernhard,
> On Tue, Jan 09, 2007 at 01:39:16PM -0800, bugs at busybox.net wrote:
>
>>
>> The following issue has been SUBMITTED.
>> ======================================================================
>> http://busybox.net/bugs/view.php?id=1149
>> ======================================================================
>> Reported By: espakman
>> Assigned To: BusyBox
>> ======================================================================
>> Project: BusyBox
>> Issue ID: 1149
>> Category: Other
>> Reproducibility: always
>> Severity: minor
>> Priority: normal
>> Status: assigned
>> ======================================================================
>> Date Submitted: 01-09-2007 13:39 PST
>> Last Modified: 01-09-2007 13:39 PST
>> ======================================================================
>> Summary: Problem with "[" command used internal to
>> busybox
>> ash
>> Description:
>> Ash revision 17084 introduced a problem with (at least) the "[" command
>> when configured internal to ash. When I use the following snippet in
>> linuxrc:
>>
>>
>> #!./busybox sh
>>
>>
>> #DEBUG=1
>>
>>
>> if [ $DEBUG ] ; then echo "test" fi
>>
>> The response with revision 17084 is:
>> /linuxrc: /linuxrc: 37: [: not found
>>
>>
>> (37 being the line number)
>>
>>
>> The attached small patch reverses a small part of the 17084 patch and
>> fixes the problem.
>
> heh. http://busybox.net/lists/busybox/2007-January/025808.html
> And what if you don't have test built-in?
>
In my case it won't work with the current linuxrc I use, because I do a
/bin/busybox --install -s
after "if [ $DEBUG ]".
Because the first line in the linuxrc script is "#!./busybox sh" it counts
on the internal "test" implementation. That's why I saw this particular
problem.
Eric
More information about the busybox
mailing list