Do this: "sh setup.sh" and it will work fine. I had the same problem.
-Jim P.
--- smn ">smnoldelinux@mediaone.net> wrote:
> I understand what your saying, but even if I set the user and group to
> my user name (scott) I still get the "bash: Permission Denied" error.
>
> Somehow, bash just doesn't want to execute this file.... and another
> ./setup.sh script for the 400A patch.
>
> - Scott
>
> "David S. Jackson" wrote:
> >
> > On Thu, Apr 20, 2000 at 07:03:52PM -0400 smn
> ">smnoldelinux@mediaone.net> wrote:
> >
> > > I'm trying to get UT to run under linux. However, I get the
> following
> > > error:
> > >
> > > [scott@smnolde System]$ ls -la UnrealTournament
> > > -rwxrwxr-x 1 scott root 153630 Nov 29 14:40
> UnrealTournament
> > >
> > > [scott@smnolde System]$ ./UnrealTournament
> > > bash: ./UnrealTournament: Permission denied
> > >
> > > Ther permissions are set properly, but bash pukes. Any ideas?
> >
> > I'm not sure how you have things set up on your system, but
> > hopefully there is something like a "game" group which has access
> > to the sound and disk resources needed by UT? Should still
> > execute, though.
> >
> > Perhaps there are some other binaries that are called that don't
> > have their permissions set correctly? I don't know
> > UnrealTournament at all; these are just general ideas.
> >
> > --
> > David S. Jackson http://www.dsj.net
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> > "Mary had a little key, and it was held in escrow.
> > And everything that Mary said, the feds were sure to know."
>
> --
> Never do Windows again with | Scott M. Nolde
> Linux! No streaks, haze or | ">smnoldelinux@mediaone.net
> glaze! |
> 9:20pm up 3 days, 12 min, 3 users, load average: 0.43, 0.22, 0.36
> --
> To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in
> message body.
>
__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.