Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
If your going to install software globaly into your filesystem........like if you want a piece of software installed for all users on the system to use.......maybe like jre........or an mplayer that each user can use.......what would be the best place in the filesystem tree to begin to build that application?
In other words......im not asking where the program should be installed on the system, because generally make install will put the proper files in the proper place........Im asking what directory within the filesystem tree is the proper place to put the tarball ........and unzip it.......and build it.
In other words.........im not asking what bash mode to enter into to build the directory......like user or root.......instead whats the usual file within the filesystem tree to build software in? Would it be /opt...since that file is set aside for "optional software"........or /usr..........or /usr/local?
Just wandering. I have a habit of building within the /opt directory. Just wandering where other linux gurus do this at?
Originally posted by matthewa ok.what Im saying is this:
If your going to install software globaly into your filesystem........like if you want a piece of software installed for all users on the system to use.......maybe like jre........or an mplayer that each user can use.......what would be the best place in the filesystem tree to begin to build that application?
The build tree should be kept private (/home), and not placed into the generally accessible areas unless you want your user population to have access to the source. The /usr, /opt hierarchies are generally for the binaries. /usr/local/src is generally where you would place globally accessessible source/builds.
Interesting.......thank you for your posts. Im putting together a linux learning site and trying to gather the correct information for my tutorials. Instead of just teaching the way that I do, I really wanted to get as many opinions from other users as I could. There seems to be different opinions on this particular subject, so I gather that it depends on the Distro the person is using as much as the persons preference?
The only standards, if your distribution adheres to them, are in the Linux Standards Base. While some file locations are defined (and more will be), there are many areas that are outside the standard. Most of the larger distributions are now LSB compliant, which makes life easier for developers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.