[patch] prevent ash executing non-files

[Rob Landley]

On Monday 11 September 2006 7:47 am, walter harms wrote:
> my target is to make a test environment like that of bash
> working for ash. therefore i/we need some understanding what
> right. i understand i should discuss that mainly with denis and berhard.
> ok ?

My eventual goal for bbsh as a project is to make a reasonable small bash 
replacement (at least when you enable all the config options).  But I'm not 
going to use any of the ash code, and I'd someday like to remove ash because 
it's enormous and bloated, can't configure down as small as lash, and doesn't 
strike me as a good basis for future shell work.  Before I started bbsh there 
were four separately implemented busybox shells that only share some add-on 
code.

I want to unify the mess.  The previous unification attempt (hush) failed 
because it couldn't configure down as small as lash and thus replace it.  In 
that context, basing the unifcation attempt on the largest, ugliest, and most 
bloated of the shells would have been insane.

I've bookmarked all the test cases you've posted so far because I want to make 
bbsh handle them all.  If you come up with more test cases (or a shell test 
suite), I'm interested.  If you come up with patches to ash, I'm not.

Rob
-- 
Never bet against the cheap plastic solution.