#This section builds the MOD part of the server

echo    "I will now build the MOD Installation based on your selection
below:"
echo
echo    "1. Team Fortress Classic (TFC)"
echo    "2. Firearms (FA)"
echo    "3. Day of Defeat (DoD)"
echo    "4. Counter-Strike (CS)"
echo
echo -n "Enter the number of the MOD you wish to install:"
     read var_mod

        if ["$var_mod" -eq "1"]
        then
          echo $var_mod
          mkdir /home/$var_username/hlds_l/tfc
          cp -v /home/hl_files/hl/tfc/tfc.tar
/home/var_username/hlds_l/tfc
          cd /home/$var_username/hlds_l/tfc
          tar -xvf tfc.tar
        else
          exit
        fi

It doesn't get past the if [$var_mod -eq "1"] - I get './setup.sh: [1:
command not found' as the error message.  This is my first attempt at
any kind of bash scripting...really this is my attempt at Linux so be
gentle :)

That should be if [ "$var_mod" = "1" ]
Spaces around [ and ] are required.

--
M?ns Rullg?rd
m...@users.sf.net

Ask on cold.apps in the future.

You need spaces:

  if [ $var_mod -eq 1 ]

Also, note I removed the quotes.  `-eq' operates on integers, not
strings.  It doesn't really matter for -eq, but it might cause bizarre
things to happen if sh starts thinking one of those is supposed to be
a string.

Don't do this, do

  tar -C /home/$var_username/hlds_l/tfc -xvf tfc.tar

It will run twice as fast.

Why this?  You don't _need_ an `else' (and `exit' is supposed to take
an argument).

--
Eric McCoy (reverse "ten.xoc@mpe", mail to "ctr2sprt" is filtered)

"Last I checked, it wasn't the power cord for the Clue Generator that
was sticking up your ass." - John Novak, rasfwrj

I meant to mention the reason for this in my post, but I think I
forgot to.  So, to the OP: You need spaces because `if' and `[' must
be distinct tokens, and sh delimits tokens using only spaces.  The
reason they're different tokens is that `[' is basically a program (it
actually is a program, but usually you're using a shell builtin
instead) that performs the enclosed tests.  All `if' does is check the
return code of its argument (`[ ... ]') and figure out where to
branch.

This lets you do things like:

  if grep -q thing file; then
    echo "matched (grep returned success)"
  else
    echo "no match (grep returned $?)"
  fi

And strange but useful things like:

  [ -e filename ] || exit 0

(...which is more commonly written `test -e filename'.)

--
Eric McCoy (reverse "ten.xoc@mpe", mail to "ctr2sprt" is filtered)

"Last I checked, it wasn't the power cord for the Clue Generator that
was sticking up your ass." - John Novak, rasfwrj