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 have a slightly different problem: I want requests for:
to go to:
I don't want to use a re-direct as this should be transparent to the user.
alias / /thisdir
but that caused an error: "Forbidden, you do not have access to /" and blocks ALL accesses to my site.
I apologize for posting to a dead thread. I couldn't find a live one with this topic. The solutions posted do not solve my problem, but I did find a REALLY simple one (see below).
My website has 4 entry points:
0. mysite provides a simple "home page" that provides links to "sites" 1 and 2 below
1. mysite/Pix sends users directly to an index list of programs to run. They don't have to add the /~me/somefolder. Also, due to other considerations, /Pix is outside Public_html
2. mysite/~me sends users to my regular site (homepage, links, etc)
3. mysite/subdir sends users to my development site (using index.php, etc.) built with Drupal
My primary concern was to be able to export "site" 3, as-is, to a production server, leaving all links relative to the subdirectory the files are in. This way both systems use the exact same link structure and don't interfere with "sites" 1 & 2. I suspect that this may not be the "best" way to do what I wanted, but it is what I came up with.
A redirect would not be transparent on the production system.
Changing Document Root would break my other "sites".
the live thread is the one that YOU start yourself.
If I started a thread with a topic that someone was already posting to, wouldn't that be as bad as posting to a dead thread? Responses would be split across 2 sets of postings, making it hard for anyone to follow logically and maybe not even find the answer they want. I was TRYING keep my posting with a topic appeared TO ME to be relevant. As it turns out, it isn't really a Linux question.