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.
Nah. You use hardlinks (called sym [symbolic] links in *nix) to place the same file in more than one place, or even in the same directory with a different name. Deleting the original file wont delete all of the symlinks, but it will make them useless. Deleting a symlink wont touch the original file. Hope this helps.
If you create a hard link to a regular file, what you are really doing is creating another directory entry for the file. A directory entry contains a name and a pointer to the file's inode on the filesystem.
Note the second column in the long listing. The kernel only removes the inode if all links to the inode are deleted. For file3, there is only 1. The third listing prints the inodes as well (-i). Note how the inodes for file1 and file2 are the same. A directory entry is actually a hard link. However creating another hard link to a directory is prohibited unless the -d or -F option is used by the root user, but the kernel deny this (CAP_LINK_DIR). This is to prevent infinite recursion in the filesystem.
Next I changed the group owner of the file1. The change also effects the group ownership of file2.