Well to run binary executables in formats supported by _your_ Linux
kernel, the wway to go is thus :

<for newbies>
Suppose you are user 'maddog'

Log in as maddog
now you are in /home/maddog.. use pwd to check that if you dont believe me

Create /home/maddog/bin  .. use mkdir /home/maddog/bin. Caution :
Generally , md is DOSsy. It does not work under *NIX, unless you have had
your /etc/bashrc (un)knowingly tampered by Atul and Co. ;)

place the executable in /home/maddog/bin.. eg cp /home/maddog/sweetexec
/home/maddog/bin

Type in sweetexec (the name of your executable, for you this might be
"shotgun" .. or my favourite .. "a" ) 

If it doen't run , you can _try_ this
Fire up your favorite editor and edit .bash_profile
assuming your shell is bash) . You should find the following line there. 

PATH=$PATH:$HOME/bin 

If it is not, there is something wrong with your looks. Force it to be
there and relogin.. ie logout and login 

</for newbies>

<disclaimer>
The way above has its own advantages and is probably more secure.

i NEVER do it this way and the way i do it could be a bad way of
doing things, so i wont recco it. The way i do it (as many do) is to
edit my .bash_profile and append a ":." to the PATH line.
:-) 

 </disclaimer>


Shourya


  --
_______________________________________________________________
Shourya Sarcar         <[EMAIL PROTECTED]>  <Tel:91-033-4710477>
Department of Computer Science and Engineering
Jadavpur University    Calcutta, India 700 032

All the world's a stage..
And I am acting tonight
C - the difference : http://www.eskimo.com/~scs/C-faq/top.html


--------------------------------------------------------------------
The Linux India Mailing List Archives are now available.  Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.

Reply via email to