On 1 Feb 02 at 10:55, [EMAIL PROTECTED] wrote: >I don't think setenv is an executable. This is all I can find:
Hi Steven, thanks for your help again. I understand 'setenv xxx yyy' is equivalent to 'export xxx=yy' in bash scripts. Last days and weeks I spent quite some I time debuging install scripts of all kinds. I learnt a lot about script language, but also realized that your Busybox solution for BasicLinux has some drawbacks. Commands line options are somehow limited and a beginner can even be puzzled by man pages describing the commands in their binary form. I have no idea whether it is common to alter the syntax of commands in Linux world. Regarding BasicLinux I would suggest the following approach: 1. Leave Busybox and reduced commands in the RD version where space is critical (BTW: how much did you actually save this way?) When you substitute options by scripts (eg. untar) there could perhaps be another script catching the non existing option parameter (eg. tar - u etc.). 2. If a user decides to migrate to the HD version he should be given the possibility to upgrade to the 'real' commands. A few files can be replaced already in the HD packet and this is what you did. But what about a documented add-on for download on your site that replaces every command that is not 100% syntactically identical with man pages? After I installed 'which' (you sent me the file), I was really disappointed and asked myself why this binary is necessary. But it seems to be used in many scripts. The same is probably true in regard to some command features left out in Busybox. For beginners it would be most important to avoid ambiguity. Christof Lange _______________________________________________ Christof Lange <[EMAIL PROTECTED]> Prokopova 4, 130 00 Praha 3, Czech Republic phone: (+420-2) 22 78 06 73 / 22 78 20 02 http://www.volny.cz/cce.zizkov
