SlackwareThis Forum is for the discussion of Slackware Linux.
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.
So I'm working off of a clean slackware 10.2 install now. Terminal works perfectly, and I can still be productive without any sort of window manager, but having one would be nice. The X11 and window manager packages where installed upon setting up the system, however, when I type startx or xorgconfig I get a command not found error. What might this be from and how do I fix it? I've confirmed that the xorg.conf file exists and makes sense (/etc/X11/xorg.conf) but still the command is not found. First time I've encountered this. Thanks.
wow thanks, the ls command showed that startx exists and upon running it by absolut path it can't find more commands, such as xauth and so on. When I booted, I logged into root, created a new user, and then su'd back to root. is the suing what caused the problem? Also, should the new user I created be able to run startx upon logon in the terminal? Sorry for my relative ignorance on the details of linux.
Thanks, apparently the su was the problem. When I log on initially as either root or my user I now can exicute startx. Thanks. As an aside, could some one breifly explaine why switching the user causes this to happen? Thanks.
Kaamoss, take a look at su's man page by issuing the command: man su
You'll see that if you execute su <user> (if you ommit user it will default to root) it will change to it, but won't load the enviroment values. To do that, you need to add a - to the command, like su - <user> .
The default search directories for executable files when you don't specify a full path is given by a enviroment value called PATH (you can see this by typing echo $PATH). If you don't use the - in su, it won't load the default profile which sets this variable (/etc/profile). So, if you don't use the -, the user you switched too won't "know" where startx or other files are.
Awesome. Thank you for the explaination, I appreciate it. I finally made the full linux leap on my main machine and have no windows partition so I'm sure I'll be reading many more man pages and making more posts on here.