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 don't think this can be done, for you must be able to read /usr/bin, /usr/lib etc to be able to run anything for that user (a desktop manager for starters!). the only way is to create, perhaps an entire system in a hidden folder (eg. /home/user/.sys/)..... no that won't work either!
Check out the various options for restricted shells. Both bash and (I think) ksh have a way that they can work in restricted mode (don't allow a user to cd or run any command outside his $PATH). If you grep for rbash you'll find some good info, I think. I'm not sure if this will prevent the user from ls'ing other dirs though, so it may not be as secure as a chroot jail, but easier to set up.