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.
How ambiguous... Better for what? Simple text editing, such as maybe a journal you keep, sure, give nano or pico a try.
Better for config files, not really. You could use another text editor, however you will find less headache at the end of the day if you just stick with vi(m). It keeps your syntax together better, helping to ensure you don't break your code and such, plus it's the one that'll be there in a pinch since all distros (?) have it by default whereas some won't have joe/pico/nano or whatever.
Also, in rescue mode, vi(m) will be the easiest to use since you won't have to execute with full path as you would with one of the others.
Originally posted by WarriorWarren i thought this was the newbie section, maybe I should have an ultra newbie section. Ive been studying this for 6 weeks now and am finding vi (i ont know what the (m) means) very difficult to use.
Anyways thanks for adding a little, confusing a little and for VIM, whatever that may mean
vi(m) can be difficult. It's more of a practice-til-you-learn tool than a read-til-you-learn since it has some oddities. Like I said before though, you can use nano, or pico or joe or gvim, kate, kwrite... whatever, if this is simple text editing in a free text type file. However, if the syntax is strict or this is a conf file, it is usually worth the struggling to use vim to edit with. Find a good vim "quick usage guide" and print it out. Then pull it out when you need to do some vim editing.