Greg Wooledge wrote:
> I wrote this after learning of a security hole in $"..." expansion.
> (See http://www.gnu.org/software/gettext/manual/html_node/bash.html
> for details of that.)
It seems to me that the security hole is the possibility of command
substitution, rather than arbitary word expan
Hello,
I'm a fairly new user in Linux, and I've been studying and attempting to
use the commands available to me at the command line by reading the man
and info pages. I'm running into lots of problems determining the proper
syntax for many of the commands due to very sketchy documentation.
Ray Parrish wrote:
> Hello,
>
> I'm a fairly new user in Linux, and I've been studying and attempting to
> use the commands available to me at the command line by reading the man
> and info pages. I'm running into lots of problems determining the proper
> syntax for many of the commands due to ver
Chet Ramey wrote:
Ray Parrish wrote:
Hello,
I'm a fairly new user in Linux, and I've been studying and attempting to
use the commands available to me at the command line by reading the man
and info pages. I'm running into lots of problems determining the proper
syntax for many of the command
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/a/local/share/
On Monday 02 March 2009 00:22:15 Ray Parrish wrote:
> but it would be nice if the man pages would at least mention things like
> "this parameter has to be quoted to work" or use a * on the end of the
> path to activate the --recursive option. It took me hours to find that
> out with the ls command,
