also @ TechSpot: AMD Radeon HD 7770 & Radeon HD 7750 Review
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.

Go Back   TechSpot OpenBoards > Software > The Alternative OS

Download Now:

Quick Question RedHat 9

Thread Tools Search this Thread
  #1  
Old 08-07-2003
XtR-X's Avatar
TechSpot Maniac
 
Location: Orange County, CA
Member since: Jun 2003, 1,040 posts
Quick Question RedHat 9

I'm having trouble extracting and executing bin files. I'm trying to do it from the terminal and I have all the directories set properly. I try to execute/extract/run the files and and it says it wasn't found! But then, I open up the root folder and it's all there! WTF. I'm logged in as root and I went into the properties and made all the folders and files chmod'd 777, since I can't do it in terminal.

I'm in [root@localhost csserver]# and that's where all my files are! I'm like wtf!

What am I doing wrong? What do I need to do to get the contents of the .bin files working?

HELP! Urgent plz!
  #2  
Old 08-07-2003
XtR-X's Avatar
TechSpot Maniac
 
Location: Orange County, CA
Member since: Jun 2003, 1,040 posts
Acutally, I discovered an alternative and somehow I made a new directory aside to the directory root, weird.

Nvm, I think I've got it.
  #3  
Old 08-08-2003
Nodsu's Avatar
TechSpot Evangelist
 
Location: Estonia
Member since: Feb 2002, 9,431 posts
System specs
For security reasons unixoid systems don't run things in the current directory like DOS. So if you want to run something from the non-PATH directory you are at, you need to do "./proggy.bin" instead of just "proggy.bin"
  #4  
Old 08-08-2003
Phantasm66's Avatar
TechSpot Evangelist
 
Location: Glasgow, Scotland
Member since: Feb 2002, 6,504 posts
Quote:
Originally posted by Nodsu
For security reasons unixoid systems don't run things in the current directory like DOS. So if you want to run something from the non-PATH directory you are at, you need to do "./proggy.bin" instead of just "proggy.bin"
Correct - because the present working directory is never in your $PATH environment variable.

This is because I would write a malicious program and then call it "ls" and then put it in your home dir, when you opened a terminal window, and it defaulted to your home dir as present working directory, I would have tricked you into running it if pwd was listed early enough in your $PATH.
Closed Thread

Similar Topics
Topic Replies Forum
Just a quick question 4 Windows OS
Just one quick question 4 Processors and Motherboards
quick question 6 Processors and Motherboards
Quick question about RAM 3 Processors and Motherboards
ok quick question 2 Storage and Networking

Thread Tools Search this Thread
Search this Thread:

Advanced Search
All times are GMT -4. The time now is 12:31 PM.