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, try dropping back to the command prompt (ctrl+alt+backspace should work).
From there you can do the whole xconfigurator thing.
Here's a little bit of home-brewed advice (I've had X problems before new, too):
Ensure that unless you really need to, you do not have X start on boot. You want it to give you a text mode login. That way, you can login and type startx to get X started (fairly obvious, that one). Here's why I found it to be so much more useful. If you find that X stops, but you can still get to the other 'virtual consoles' (by pressing ctrl+alt+f1, f2, f3, etc) then you can go back to the original console you were at before you typed startx (usually f1) and you can see X running (or at least the commands it's passing). All you need to do is press ctrl+c to stop it.
I found that it's a god send when you're trying to do things like install the new NVidia drivers.
Oh, you might want to get used to a text mode editor aswell. Personally I like jed, but there seems to be a remarkably large camp that it vi/vim all the way.
I'm beginning to hate Linux, is there no actual how to book? Something as simple as changing the screen resolution should not require a PHD in computer sience to do. I agree that Mickysoft sucks, but at least the simple minded can do the simple stuff on the real Windows....
there are plenty of books on linux and if you bought a retail version I'm sure you would have received a book. Did you even try using that nifty feature called help? For me, the obstacles is what make something new fun, also gives you skills to fix other problems thay may arise.
go to half.com, search for linux under books and see how many hits you get.
Last edited by Glock Shooter; 01-21-2002 at 05:41 PM.
Then under the "Section "Screen" check what is the default depth.
For me it is DefaultDepth 24
Then find the subsection display with the default depth you have
and under modes add the resolution of your screen. For me I added the
Distribution: Debian Etch (w/ dual-boot XP for gaming)
Good advice - except vi(m) is likely to be horrendously frustrating for those who haven't used it before, and just want to change a few lines in a file. If you're used to it, great, or if you have another favourite command-line editor, use that.
If you don't have a favourite editor, it's time to get one. Pretty much everything in Linux can be (and is) controlled by text configuration files, and it's not always practical to use graphical editors. Editors that are supposedly easy to pick up include pico and nano, though if you're willing to put in a little learning time, vim becomes increasingly useful (plus vi is guaranteed to be installed on any UNIX, wherever you are). Or you could learn to use emacs, but as a vim user, that's the dark side. (There's a big holy war between vim and emacs users, avoid if at all possible!)