On Thu, 2010-07-15 at 12:09 +0200, Giacomo A. Catenazzi wrote: > System initialisation and in general system script are outside POSIX > scope, as well many common command executed by such scripts > (administration tools are also outside POSIX). Well yes,... nevertheless I guess that it's always a good idea to restrict to scripts to the bare minimum... of course as far as possible. > Additionally system initialisation is very complex and it should handle > to many different setups (from no local disks to very complex local > disks setup, etc.). That's what I've meant... and with such complex setups, not having many coreutils available could be a problem. > Our "boot people" take care about init scripts, their requirements > and thus what it should be moved from /usr to root. > It is a case-by-case analysis. Uhm... looking at coreutils, I find many programs which I guess can be used (or are actually) during system initialisation, e.g.: env base64 dirname [ test stat timeout id printf just to name a few. > not portable? Do you have some real/widely used examples of > incompatible use? Especially "-n",... which is widely used,... but not portable. > BTW GNU/Linux is not fully POSIX compatible by design. It follow the > LSB (an other standard) and there is a ISO groups to find and try > to correct the differences. "echo" is one of "required" difference. Yeah I know,... but it does not automatically mean that this were the "right" choice. I guess LSB&Co. just made it because it was already so widely used, that you could never convince people to do different. Cheers, Chris.
Description: S/MIME cryptographic signature