Linux Format forums

Re: RE: hard coding keyboard input in a Bash script

drws — Wed Jan 11, 2006 6:22 pm

Author: drws

Posted: Wed Jan 11, 2006 6:22 pm

CJLL wrote:

Bash scripts accept upto 9 parameters on the command line, they are named $1 to $9

Don't forget ${10} ${11} ${12} etc. if you need more than 9 parameters

RE: hard coding keyboard input in a Bash script

TonyLB — Wed Jan 11, 2006 3:40 pm

Author: TonyLB

Posted: Wed Jan 11, 2006 3:40 pm

Thanks folks - I should have thought of echo!

Neltz's one does just what I needed.

Tony

RE: hard coding keyboard input in a Bash script

CJLL — Tue Jan 10, 2006 11:03 pm

Author: CJLL

Posted: Tue Jan 10, 2006 11:03 pm

Bash scripts accept upto 9 parameters on the command line, they are named $1 to $9

Code:

#!/bin/sh

echo "Param 1: $1"

update-alternatives --config $1

Alternatively if you want your script to get interactive

Code:

!/bin/sh
echo -n "Enter your name: "
read -e NAME
echo "Hello $NAME"

update-alternatives --config $NAME

RE: hard coding keyboard input in a Bash script

nelz — Tue Jan 10, 2006 2:58 pm

Author: nelz

Posted: Tue Jan 10, 2006 2:58 pm

Code:

echo "xxx" | update-alternatives --config <&0

echo sends the command to stdout
the pipe sends the stdout to stdin for the next command
&0 is the file handle for stdin, so <&0 redirects it to the command.

hard coding keyboard input in a Bash script

TonyLB — Tue Jan 10, 2006 2:45 pm

Author: TonyLB

Posted: Tue Jan 10, 2006 2:45 pm

I'm trying to write a couple of Bash scripts which use utility programs that take keyboard input (eg update-alternatives --config xxx needs a choice from the keyboard.

I want to automate it from a parameter passed when the script is used. At the moment my best effort writes a file using the input parameter, runs update-alternatives redirecting input from the newly created file, then deletes the file.

There must be a better way I'm sure. How can you pass a parameter rather than use keyboard input without writing it to a file first?

Tony