Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
yes, it definitely looks like a mistake. The root cause is that the command ln -s <from> <to> will give different resuslt depending on the <from> (if it was a file or a dir) and depending on <to> if it exists or not and <to> is a dir or file.
usually creating link into a non-existing dir will give you surprising result. Using relative path may also lead to strange results (especially when the current working directory is not the one you need to use). I think that happened in your case.
Actually, you can't make a hardlink to a directory - it is already set. The problem with making hard links to directories is that it makes fsck fail (the directory tree is no longer a tree).
A directory file can only have two links - one pointing to itself (.) and the one from its parent directory.
During fsck, a symbolic link is treated as an ordinary file with data. Directories though must have a parent directory, and must have an entry for themselves. A parent directory must exist, and there can only be one parent directory.