[ut2004] /bin/sh: bad interpreter: Permission denied

[Andrew Pilley]

On Tue, 2004-04-20 at 19:46, Frederik Dannemare wrote:
> On Tuesday 20 April 2004 11:10, Andrew Pilley wrote:
> > On Tue, 2004-04-20 at 18:58, Frederik Dannemare wrote:
> > > Why install it as root? Doesn't make sense.
> >
> > What's wrong with installing as root, and just putting stuff in
> > ~/.ut2004 ?
> 
> So you are saying that you install as root into ~/.ut2004. Is this root's 
> homedir or your own homedir? Either way it just doesn't make sense. Let me 
> guess: you run the game as root as well? And you chmod 777 all kinds of 
> files when you can't get something to work?

No. I'm a professional system administrator, I learned effective
permission management long before I started getting paid for it.

The game can be installed as root, and run by ANYONE, as long as there
are enough priviledges to read and execute the game, as there normally
are with the default install. Restrictions on users can come from group
permissions, applied by the site's system administrators.

The game creates ~/.ut2004/ and drops config files in there, as any
properly written linux application should. (Notably annoying exception
to this was Savage: the battle for newerth, much to my irritation, which
insisted on being able to write to the data directory AND ~/.savage/,
sigh.)

> 
> Please tell me why you don't just into as yourself into your own homedir? 

Because my home directory isn't for datafiles I can recover from
original media. It's for my files, that are specific to me, and I'd
prefer it if it could be backed up onto one or two cds without a
convoluted backup system. Having a few saved games and text files leads
to this. KISS applies.

> Alternatively, you could create something like /usr/local/games and let it 
> be owned by you (or some games group and then become a member of this). 
> This way you don't need root for anything - and certainly not for running 
> the game!

Or, I could create /usr/local/games, and let it be owned by root, so
that I can specifically rule out having the game modify its own data
unless I so will it. 
And there's no edict on having to run the game by the person who owns
the main data files, except in instances where the game is poorly
written.

> 
> > It's a sound system administration technique, and has been for years.
> 
> Depending on what you are dealing with, of course. And depending on how you 
> practice security.

I practice security everywhere. My firewall blocks everything, and I
control and log what goes out when it looks weird. I segregate systems
into things that lead to their own protection. I use root where
appropriate, not to get around permission problems.

Since this looks like it'll turn into a pissing match fairly quickly,
I'll clarify something:

I meant 'install it as root into /usr/local/games/, and let it run as a
normal user, and write config files into ~/.ut2004/'

Please don't judge my ethics and methods when there's a possibility for
misinterpretation.

Andrew Pilley


> 
> --
> Frederik Dannemare
-- 
<Berawler> Is there any sanity or light left in this shrivelled husk of
a world?
<SingingDancingMoose> There was, but we had to trade it in for the
internet.