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 editing a file in vi and my internet connection
crashed...now when i try open the file it says that it was busy editing the file etc...and that the process is still running...how do i get back to that vi session the id is 56183...any ideas of what i can do? vi -r didnt work
Maybe the process is not running, because the parent (terminal) is gone; however maybe a temporary file of the type .<something> is there. I'm not a vim expert, but the later versions try to keep your last edit place on a file. And what I do know in a similar situation is if I have to force shutdown when I have a truecrypt volume mounted, it leaves a .truecrypt-lock-<myusername> file in my home; and when I boot back up I have to remove that file or it complains that truecrypt is already running. It really isn't, but the error says that because it sees the lock file. Therefore see if vim has some sort of lock file or a directory in your home containing something like that.
You could try lsof to see exactly which file is open and try 'cat' ing that to a new temp file.
you may be able to recover most of it from there.
You can also check for eg a file called 'test.x' should have a backup (swp) file called '.test.x.swp' (note leading '.' .
You can see this using