actually in this system:
Slackware 12.2
that returns with an error...
*[~]$ time bash "{ ls }"
bash: { ls }: No such file or directory
real 0m0.002s
user 0m0.000s
sys 0m0.002s
[~]$*
it really seems to be with the version of bash that Slackware uses.
> The reason for this is that time simply passes its argument to
> one of the exec() calls. So, "{ls}" is not the name of any
> command, and it can't be executed. However
>
> time bash "{ ls }"
>
> should work, because then the command is simply bash, which
> *is* found, and bash gets the string "{ ls }" as a command,
> which it can interpret.
>
> Those brackets and things are stuff bash knows how to interpret.
> However, that's a function of bash, not of the program loader.
> The program loader looks for files in the PATH.--
>
======================================================================
"The shortest way to do many things is to do only one thing at a time."
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
