On May 18, Gustavo Franco <[EMAIL PROTECTED]> wrote: > Good, but i think interested people here are all our users, so what > we're going to do with the 10% performance hit for use bash? I think Nothing. A 10% optimization of init scripts which we already know are highly suboptimal is not worth pursuing. Try benchmarking again the shells after enabling parallel processing of init scripts and let's see how much time dash would save in that situation.
> >Making dash the default /bin/sh would probably break too many non-debian > >packages and changing all init scripts to use dash would mean adding a > >new dependency for no good reason. > I think making dash the default /bin/sh for Etch now would probably be > insane yes, but we should focus on solve problems for our next release > (Etch) and what we can do now to prepare a even better Etch+1. This is > the real problem, i'm not talking only about the 'dash' issue. bashisms in the wild is not something which will be solved by the rest of the world after etch. Time will not help much. -- ciao, Marco
signature.asc
Description: Digital signature
