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.
There's nothing wrong in having a GUI on a server as such.
Theoretically it does increase the 'attack surface' / places where things can break, but its not that big a deal really.
Also, it doesn't provide any noticeable overhead. If you're not actually typing/clicking into it, most of it it gets swapped out.
That being said, in 'serious' environments, most admins don't run a GUI. Its also worth learning the CLI for when things break. Also, you'll be wanting to automate stuff and that means CLI programming.
Do go through the whole system and remove any SW you don't actually use.
thanks for your responses. I will give it a shot running a file server with no GUI. I'm a newbie and I'm learning shell scripting. I actually love the CLI, I actually run it most of the time on my OpenSuse box unless I need to do some GUI work but I never run a system without any GUI at all BESIDES M$crosoft DOS when I was 9 years old!
Well, there's nothing to stop you starting with an install that runs at level 5 (X-win/Gui), then opening xterms to work at for stuff you understand and use the gui for stuff you don't.
Eventually, when you've learnt everything you need, you can set /etc/inittab initdefault to level 3 and reboot and all you get loaded is cli.
Also means if you get stuck again, you can 'startx' and use the gui.