i dont want to discuss the logistics of how this will be done just yet ... the idea is to remove 'sash' from our system target and replace it with busybox ... there are a few applets that sash implements and busybox does not (chattr ed file lsattr printenv sum where), but i added chattr, lsattr, printenv, and sum to busybox yesterday :) ... i've never heard of 'where' and going by its behavior in sash, it's basically 'which' ... that leaves us with 'ed' and 'file' which i think we can ignore and be OK ...
for those of you who do not know, busybox is a single binary which implements the functionality of most system utils ... it does not completely implement some features, just the most common ones, but then again sash does the same thing :) details: - busybox implements a *ton* more applets ... it can be configured to replace over 100 system funcs while sash provides about 35 ... - size wise, busybox would be larger, probably by about ~150k - ~200k - busybox commands are transparent while sash requires you to prefix internal commands with a '-' ... so running `cp` in busybox will use busybox's cp while sash needs to run '-cp', and you can still execute the real cp by doing /bin/cp in busybox feedback !? -mike -- [email protected] mailing list
