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.
If this is a hard link then it is in fact "the same file" and there is no need to copy from one to the other.
Run "ls -l /home/casper/clearing/" if you see a number higher than 1 in the second column (between mode and owner) then the file is a hard link. If you run "ls -i" on both files they should show the same inode number if they are the same.
Are you doing this copy after updating /home/clearing.txt? If the other one is a hard link to this one then there is no reason to do the copy at all. Any changes to the first one are also changes to the second one as they ARE "the same file".
You're not transferring a file with the above - you're ssh'ing into the other machine then doing a local copy on it.
You'd need to use scp rather than cp to "copy" from one machine to another. Of course you can also do rsync for such copies. If you type "man scp" and "man rsync" you can see options including those for overwriting if the file is already there. However, one of the main benefits of rsync is to only copy those things that don't already exist - thereby saving network bandwidth.