> >> So besides "sleep", the other ksh93 builtins that are not Solaris ksh >> builtins (and not Solaris binaries) are getconf and printf. >> Are there dependencies on these being ksh93 builtins? >> >> And there are the builtins from libcmd, which are not available >> by default, but seem to be activated via "builtin <command name>" >> although I am able to activate only a subset in ksh93: >> >> basename >> cat >> chmod >> cmp >> cut >> dirname >> head >> logname >> mkdir >> uname >> wc >> >> Would ksh93 users need to have these builtins available? >> > >printf is needed since it contains extensions that are not >in the standard printf that are used in several shell scripts. > >The ones on this list are provided primarily for performance since >builtins are 10 to 100 times as fast.
There are, of course, many issues with the compatibility of the builtins and the Solaris versions; e.g., chmod has grown a number of new options relating to ACLs recently. In some cases, perhaps, ksh93 could parse the options and when it decides it doesn't like them fall back to the external command? Their remain cases like "uname -a" which probably doesn't much the builtin. And we can also see whether the standard Solaris utilities should grow additional options to accomodate what ksh93 scripts might expect. Casper
