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.
I've been using linux on & off for a few years, and one thing that was never clear to me was a common knowledge on where to install programs. I usually just end up making new folders in my home directory, which seems a little messy.
Trying to make sense of the default install setup when you install a distro isn't much help. While binaries are in /bin directories, they're spread around in different /bins, and it's hard to figure out the logic of it. /usr/local seems like a logical place for things that aren't installed as root, but then that brings up another question: when to & when not to install something as root. I've been told it can be dangerous, but some programs require root access, and further, help documents don't always explicitly state whether or not that's required.
So, does anyone have any tips, links, or advice that could give insight into common conventions & efficient use of a *NIX file tree?
Well, for the most part, when you install something, it picks where its going to install. For example, installing from a package of any sort (.rpm, .tgz, .deb) will install wherever it's told to by default. If you install from source, most applications will choose to install somewhere (usually /usr/local/bin, but there are exceptions) and will only install elsewhere if you tell it explicitly to do so. If, however, you are downloading a binary (like Firefox is), I just throw mine in /usr/local/bin, as it seems to work the best for me, and I know where everything is.
The tarball will install into either /usr or /usr/local. Some files will go into the bin dir and some into the lib directory, and some in doc.
According to the Linux Filesystem Hierarchy Standard (LFHS), /usr/local should be the base directory for the installations. Upgrading a distro will not change the files in these directories.
The part I don't understand myself is using a common /usr/local directory for a network. Shouldn't it be called /usr/shared then?
This sounds a lot like the phrase 'wireless cable'?
Originally posted by jschiwal According to the Linux Filesystem Hierarchy Standard (LFHS), /usr/local should be the base directory for the installations. Upgrading a distro will not change the files in these directories.