SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Linux isn't "meant to be a command-line OS". Yes, it has a command line. Yes, some distros (Slackware included) boot to a command line after you first install them. However, Linux itself is "meant to be" whatever you want it to be. Saying that Linux is "command-line based" is somewhat more accurate.
I appreciate the fact that I am able to use a graphical interface (more efficient for many tasks), while still being able to pull up a command line whenever I need to. Sure, most casual users don't want or need to use the command line to accomplish many things, but this ties into my original point:
Linux can be whatever you want it to be. You could run the whole thing using GUI tools and (almost) never touch a command line, or you can use the command line for everything. Most people don't go to either extreme, but the option is there.
See, the beauty of this OS is the fact that it's oriented both to end-user and network administrators. In other words, you can use OpenOffice to write a document or set up a network cluster with the same OS if you are a network administrator...
Could this be more open-minded, as an OS mentality?
Would anyone like to write a GUI program(eg. web browser) using assemble language, which could provide full control over hardware?
Would anyone like to read through tens of thousand lines of the source code of a word processor to understand how it works before starting writing a word of an essay?
Not while one can say, "They should make Linux work better for me."
Democracy in action.