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 was trying to find all symlinks under a specific folder to do this i used:-
find /bar/foo/ -type l
This works fine on the most part and produced expected results appart from one of the results returned was very odd...output something like...
Get the meaning?? everything was returning from inside /bar/foo as i would expect apart from this one line which appears to have come from somewhere completely different and i've not been able to even find the location yet as there is no such place as:-
As in not possible to go "cd /nothing/to/do/......"
If possible, please copy paste the actual command and the actual results. As you describe it, it looks weird, but maybe you are missing something that a fresh pair of eyes can spot, given the original data.
Hi There, i think that sounds about right...it certainly looked like it was not working correctly even when trying to traverse back out of the folder to the top of the tree (so to speak). That it wasn't possible to do cd ../../
It would fail with some weird error....anyway sorted now thanks for the info