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 use FC3.
I have a service:command not found problem.
Other commands like chkconfig are also missing.I think I've goofed up the installation a bit.How do I correct this?
IF the solution is mounting one of the FC3 cds..which one to use and how to go about it?
Just a check: do you mean that if you "su" to root and try to do "chkconfig" or something like that, you get a "command not found" error? In that case everything is all right (if you log in as root: press ctrl+alt+f2 for example, and log in there, it should work). Fedora has, for some reason, different $PATH variable for root user and other users; therefore the sbin/ directories are not found on regular user's $PATH variables, and if you "su" to root (and not login really) you'll need to give the full path to the command, for example
well i'd say it's for a *ery* good security reason... normal users have no business messing with things in /sbin, whether they can run them or not, it's none of their business. of course other than logging in fresh, just use "su -" instad of plain old "su" and things will work fine too.
Not bizarre at all - su retains your current PATH, which doesn't have /sbin in it. su - sources root's profile so you get a PATH variable with /sbin in it, hence you can now find those binaries. The thing to remember with UNIX/Linux is that anything you can't explain is because you can't explain it, not because something bizarre is happening.
The thing to remember with UNIX/Linux is that anything you can't explain is because you can't explain it, not because something bizarre is happening.
ANYTHING???!!! I'd be willing to bet that this is not a universal truth. First, it has been my experience that computers are not 100% deterministic. Second, Linux is full of long-standing Unix traditions, many of which have NO relevance to a casual desktop user---and it often takes a bit of digging to get a plausible explanation.
If I were to keep all the goodness of Linux, but simply organize things to be much simpler--optimizing for the application where 4 user accounts would be the upper limit--then it would be a veryy different picture. (I won't do this, by the way, because I value the universal nature of the OS---the fact that everyone on the planet has more or less the same picture of how things are organized..)