Yeah.. Anything Unix-like won't put "." (current directory) in your path (where the shell looks for executables), as it introduces a small security risk (mostly) for system administrators. For example, if you go to somebody else's home directory and type "ls", you want to be sure you don't run an "ls" program that person has put in their directory. This forces you to prefix commands in the current directory with ./ so you're paying more attention to what program you are running.
> Type ./startup & that will work for ya. > > > > > Okay, guys, bear with me (I'm sure I sound like a total newbie, but hey, > I'm > > new to the world of Linux, so cut me some slack. ;-) ) > > > > Anyway, I got my code to (finally) compile cleanly. However, when I try to > > run the startup script (by entering the /area directory and typing > "startup > > &") all I get is: "bash: startup: command not found". Now, I'm not > positive > > what this means...I checked the startup script and it seems to be > > executable, but it's just not flying. > > > > Oh, and I'm running Linux 8.0, in case that helps.
