The UNIX and Linux Forums  

Go Back   The UNIX and Linux Forums > Top Forums > UNIX for Dummies Questions & Answers
.
google unix.com



UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !!

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Theory question about the organization of a UNIX file... ti_ma UNIX for Dummies Questions & Answers 1 04-07-2008 02:03 PM
GNU has applied to be an organization in... iBot UNIX and Linux RSS News 0 03-06-2008 02:40 AM
Reading a file and writing the file name to a param file. thebeginer UNIX for Advanced & Expert Users 1 10-05-2007 05:38 PM
Organization in a big file system pascalbout AIX 6 03-27-2006 11:06 AM
Reading file names from a file and executing the relative file from shell script anushilrai Shell Programming and Scripting 4 03-10-2006 05:25 AM

Closed Thread
English Japanese Spanish French German Portuguese Italian Dutch Swedish Russian Norwegian Hungarian Hebrew Danish Bulgarian Greek Powered by Powered by Google
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old 08-14-2008
css136 css136 is offline
Registered User
  
 

Join Date: Aug 2008
Posts: 2
File organization, /bin and /src

The /src file is obviously designed to contain source code, so when I download programs, I should put them in /src (because they contain the source files + the executables)? What do most people do with the executables? Do they copy them to /bin, make links to them in /bin, or just leave them in /src? I am new to Linux, but I would like to start doing this correctly. Thanks!
  #2 (permalink)  
Old 08-14-2008
zaxxon's Avatar
zaxxon zaxxon is offline Forum Staff  
Moderator
  
 

Join Date: Sep 2007
Location: Germany
Posts: 2,323
If you download something, best place it somewhere, where no one accidentally uses it, deletes it or something.

/src is no file but a directory and it is no standard directory on every Unix/Linux.

Depending on what you downloaded, source code, binaries, whatever, you'll have to read the docu for it, before you start putting them somewhere in the filesystem. Many program packages use either the built in package handler of your OS, like rpm or whatever.
Some others that come as source code often have to be configured to your needs, and then compiled using "make".
This info is a very general overview. You have to read the docu if you are unsure what to do next after download.
  #3 (permalink)  
Old 08-14-2008
era era is offline Forum Advisor  
Herder of Useless Cats (On Sabbatical)
  
 

Join Date: Mar 2008
Location: /there/is/only/bin/sh
Posts: 3,652
I'd go even further, and recommend that as a regular user, you simply keep stuff in your home directory, and let the designated system administration interface (dpkg or rpm if you're on Debian or Red Hat, respectively) deal with the rest of the disk.
  #4 (permalink)  
Old 08-14-2008
css136 css136 is offline
Registered User
  
 

Join Date: Aug 2008
Posts: 2
Hi, thanks for the replies. I'll try to be more specific because I think my first post was quite vague. Sorry.

In my home directory, I have the folders ~/bin and ~/src. When I compile a program such as BLAST from source code, it seems that I should keep the BLAST folder in the ~/src directory because it contains the program's source code. Within the BLAST directory, there is a ./bin folder that contains the executables. I was simply wondering -- is it common practice to move these to my ~/bin directory, to make links to them in my ~/bin directory, or to just keep them in my ~/src directory and to execute them from there? If the answer to this question varies depending on the program, I'll just try to do whatever seems best. It is not very important, but I was just curious what the standard practice is in the Unix world. Thanks!
  #5 (permalink)  
Old 08-14-2008
zaxxon's Avatar
zaxxon zaxxon is offline Forum Staff  
Moderator
  
 

Join Date: Sep 2007
Location: Germany
Posts: 2,323
Common practice is that after you do

Code:
configure
make
make install

Last step would place the stuff either in it's default directories or those you have give with "configure".

If this all is not missing you'll have to check what the binaries you compiled depend on, maybe libraries, config files, whatever.
I usually put such programs under /usr/local/<name of that prog> and extend my PATH.
Closed Thread

Bookmarks

Tags
linux download, unix download

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT -4. The time now is 08:13 AM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited. Language Translations Powered by .
vBCredits v1.4 Copyright ©2007 - 2008, PixelFX Studios
The UNIX and Linux Forums Content Copyright ©1993-2009. All Rights Reserved.Ad Management by RedTyger

Content Relevant URLs by vBSEO 3.2.0