Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site zeus.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!mtuxo!mtunh!vax135!cornell!uw-beaver!tektronix!teklds!zeus!bobr
From: bobr@zeus.UUCP (Robert Reed)
Newsgroups: net.unix
Subject: Re: Automatically logging in root
Message-ID: <197@zeus.UUCP>
Date: Fri, 15-Nov-85 13:36:40 EST
Article-I.D.: zeus.197
Posted: Fri Nov 15 13:36:40 1985
Date-Received: Mon, 18-Nov-85 05:30:31 EST
References: <3088@brl-tgr.ARPA> <2490@uvacs.UUCP>
Organization: Tektronix, Beaverton OR
Lines: 23

> I don't know how to automatically login as root.  Like the original poster,
> I also like to be root only when necessary.
> 
> What I do is login as myself and then su to root...So when I get a
> "permission denied" error on a long command, I can "fg" to my root shell,
> and re-do the command from history.

We have a utility called ".do" which examines the UID of the invoker,
and if it is contained in a selected set of validated numbers (which are
compiled into the program), does a setuid or setgid (depending on the
options) before exec-ing the rest of the line.  So, if you get a permission
denied, you can simply do a ".do !!".  Most of the time you sit in an
unpriveledged process, so there is less concern about making mistakes that
will horribly disfigure the filesystems.  But the power is there when you
need to use it.  It does mean that you have to be careful not to leave
unattended logins, but this comes as a simple matter of habit.
---
I got a postcard from my friend George with a satellite picture of
the entire earth.  On the back he wrote, "Wish you were here."
--Steve Wright

-- 
Robert Reed, CAE Systems Division, tektronix!teklds!bobr