From: drew@romeo.cs.colorado.edu (Drew Eckhardt) Subject: Re: programs that don't run Date: Sat, 7 Aug 1993 14:14:05 GMT
In article <CBCqAv.9AJ@trystero.com> steve@trystero.com (Steve Woodward) writes:
>I'm having trouble getting programs that I've compiled to run. I try to
>run them and they say Command not found. I'm proably doing (or not doing)
>something stupid. But I can't think of why it's happening. Here's
>a sample file:
>
>-rwxr-xr-x 1 root root 121409 Aug 2 18:45 rogue
>
>I've been trying to run them as root. What am I doing wrong? Thanks!
1. . must be in your path or explicitly specified when you run the program
./rogue
Having . in your path is a security hole, if you insist on having
it put it at the end.
2. Don't run as root unless there's no alternative, ie, when installing
programs. If you forget where you are, and accidentally type the
wrong command you can wipe out your entire Linux system. When
root, after typing the command you think you want to run, sit on
your hands and think "do I really want to do this" before pressing
enter.
Even if you are treating Linux as a "single user" system, create
a separate, unpriveledged account for yourself so you don't
accidentally (ocassionally, one of our sysadmins with a year
or two of experience does one of these) obliterate your password
file, shared libraries, some directory, the entire hard disk.
-- Boycott USL/Novell for their absurd anti-BSDI lawsuit. | Condemn Colorado for Amendment Two. | Drew Eckhardt Use Linux, the fast, flexible, and free 386 unix | drew@cs.Colorado.EDU Will administer Unix for food |