Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You have various options here. One school of thought is to install them to /usr/bin, or /usr/local/bin, or /usr/share, as these directories are likely to be in your path. (To display the path, type 'echo $PATH'). Just have a look at your system to see where currently installed program directories are stored.
However, unless you are very careful, this can get messy, and it seems to be increasingly popular to create subdirectories under /opt for your programs instead, and to make sure that you have a symbolic link to the program in /usr/bin.
This way, it is easy to see and manage the programs that you have installed yourself, as they are kept seperate from the programs installed by your original setup. The symlink in /usr/bin is just there to ensure that you can just type the name of the program to launch it, without hving to specify the whole path.
My preference is to install to a subdirectory of /opt, and to create a symlink to the startup script in /usr/bin. this way, it's much easier to keep track of what you have installed when it comes to managing updates.
/usr/local is for applications that are compiled locally on the system, ie. that aren't installed by a package management system such as RPM or DEB but where the files are still seperated into the standard Linux sub-dirs - bin, etc, lib, share/man and so on. http://www.pathname.com/fhs/pub/fhs-...FTWAREPACKAGES
So really you can choose - if your app is intended to be distributed in an RPM or DEB one day then put it in /usr/local/ so it can easily be changed to /usr in the configure by the packager. If not or if you want a Windows-style 'program folder' install then put it in /opt.
Nothing wrong with that, opt would make the most sense for programs like Adobe that install into a Windows-style 'Program Folder' directory rather than spread across a Linux-y bin, lib, share structure.
Just keep in mind that what you've got there isn't the program's source code - Adobe Reader is a closed-source application. They only distribute pre-compiled binaries like on Windows. Its your choice but you don't need to go making new top-level directories like /ProgramSource, just put all your downloaded files into your home dir somewhere. That way when you backup your home dir you keep all your stuff.