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.
Oh....ok - anyway I guess I got to learn vi - because I have access to server - but not a fully dedicated one - managed one. So they woundt install stuff that they think is not required. Guess I'll go back to CUI.
Distribution: Debian Etch (w/ dual-boot XP for gaming)
Something to add is that according to POSIX standards, vi is guaranteed to be installed on any UNIX-based system, anywhere. It's probably worth learning to use it (at least to a basic level) for this reason alone. Once you get used to the idea of having two modes, there are really very few commands you need to know for the purposes of changing a few lines in a file.
In my opinion the problem with vi is not with modes. Modes are actually quite handy once you get used to them. I dislike the little oddities it has (pressing ESC on insert mode moves the cursor backwards, so you'll have to compensate it with l, cursor keys up and down or k and j won't work on wrapped lines, in vim undo is u and redo CTRL+R, etc.) Yes, I know these can be fixed, but why don't they work right in a "sane" way in the first place? In my opinion it's also a really bad idea to use control keysequences in a modal editor like vi, it makes it (even more) confusing. Controlling open windows in vim for example can't be said to be very handy, why isn't it simply done in command mode? And then there is of course the size question, >12 MB for a text editor without the graphical mode (which is a joke anyway ), oh come now...