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.
Ok, so i am doing a course at college, and i am using tuxcards to take notes.
The problem arose today when i opened up the xml file that that my notes are stored in ( it is stored on an NTFS nas mount ), everything was fine at first, all the data was there. i closed that down, and opened up an older xml file that had much less data, decided i no longer needed it and deleted it. i opened up the newer once again, which was suppose to have all the data i needed, only to find that it was a clone of the 'deleted' one ( ie it had no data ). So i checked the recycler of the NAS, found the document that had the correct data, and restored it. but once i restored it, it didn't have all the data i needed, it was the old document with no data. so i went back to the recycler again, found the correct document and changed the document name ( as i thought it was a bug ), but as soon as i changed the name, it reverted to the xml file with very little data in it. i have no idea why this has happened, i made 2 backups, and it happened to both.
1. why did this happen? can i pinpoint the problem?
2. is there anyway to recover the original document on an NTFS volume?
referring to case-sensitivity of NTFS I found this: http://support.microsoft.com/kb/100625/en-us
I was suprised about this.
So far I was only aware that Windows is case-insensitive when dealing with network-pathes (UNC-pathes).
Thanks guys, it's not a.. uhm.. case of case?? although i did manage to find another copy, i would still like to resolve this issue.
I use all lower case when naming files or creating directories. even if it were case, it wouldn't explain why deleting a completely different file would cause another file to change. the second time round, i simply changed the name from notes.tuxcards to notes, and the file completely changed. i checked the entire directory and there was nothing of significance to be found.