Language Selection

English French German Italian Portuguese Spanish

Linux: The big misconceptions

Filed under
Linux

I get a lot of emails from users of various types of users, from various industries, and from various levels of skill. But there are two types of emails that I get the most:

* I want to learn more about Linux, but there’s no where to start.
* I can’t use Linux because it’s still archaic and won’t do what I need.

In some ways and in different blogs, I have tried to address both topics. But I thought it time to address both of these topics directly here on TechRepublic. Why? The main reason is because I feel this to be the best podium from which to tackle these issues. The secondary reason is that I feel a certain loyalty to the TechRepublic nation that I do not have with any other site. With that said, let’s see what can be done about these two misconceptions.

Rest here




So much to learn, so little time

Most computer users have been taught Windows. If you want to venture into Linux, you naturally want to retain your existing operating system just in case you need it.

This is what you have to do:
1. Research the multitude of Linux systems available and decide on one.
2. Find out how to make room on your hardware for a second system and do it.
3. Find out how to install the Linux system you have somehow chosen.
4. Learn how to use the system.
5. Find out what software is available for your system, install it and learn it.
6. Spend hours searching, reading howtos and other documentation.

Sorry, most people don't have that much time.

Re: So much to learn, so little time

xanthon wrote:

Sorry, most people don't have that much time.

Good, so the terminally lazy can just keep using their existing OS and leave us and linux alone.

Re: So much to learn, so little time

shadowdeamon wrote:
Good, so the terminally lazy can just keep using their existing OS and leave us and linux alone.

xanthon is right and you're alone allright. That is, except for me Wink

xanthon's points neatly sum up why Linux has such a hard time gaining installed base: it is simply and obviously because Linux gives _people a hard time. Even if a Linux newbie manages to install Linux, he'll soon discover two things: Linux is constantly moving in unpredictable directions, requiring the user to be genuinely interested in Linux as such; and the user must be willing to forego even practically default 'standards', like e.g. flash.

I have been using Linux exclusively for many years, but then I have lots of time to spend reading man pages, searching for howto's, fixing glitches and following Linux antics. Thankfully, most people have different priorities.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

ownCloud Desktop Client 2.2.4 Released with Updated Dolphin Plugin, Bug Fixes

ownCloud is still alive and kicking, and they've recently released a new maintenance update of the ownCloud Desktop Client, version 2.2.4, bringing some much-needed improvements and patching various annoying issues. Read more

Early Benchmarks Of The Linux 4.9 DRM-Next Radeon/AMDGPU Drivers

While Linux 4.9 will not officially open for development until next week, the DRM-Next code is ready to roll with all major feature work having been committed by the different open-source Direct Rendering Manager drivers. In this article is some preliminary testing of this DRM-Next code as of 29 September when testing various AMD GPUs with the Radeon and AMDGPU DRM drivers. Linux 4.9 does bring compile-time-offered experimental support for the AMD Southern Islands GCN 1.0 hardware on AMDGPU, but that isn't the focus of this article. A follow-up comparison is being done with GCN 1.0/1.1 experimental support enabled to see the Radeon vs. AMDGPU performance difference on that hardware. For today's testing was a Radeon R7 370 to look at the Radeon DRM performance and for AMDGPU testing was the Radeon R9 285, R9 Fury, and RX 480. Benchmarks were done from the Linux 4.8 Git and Linux DRM-Next kernels as of 29 September. Read more

How to Effectively and Efficiently Edit Configuration Files in Linux

Every Linux administrator has to eventually (and manually) edit a configuration file. Whether you are setting up a web server, configuring a service to connect to a database, tweaking a bash script, or troubleshooting a network connection, you cannot avoid a dive deep into the heart of one or more configuration files. To some, the prospect of manually editing configuration files is akin to a nightmare. Wading through what seems like countless lines of options and comments can put you on the fast track for hair and sanity loss. Which, of course, isn’t true. In fact, most Linux administrators enjoy a good debugging or configuration challenge. Sifting through the minutiae of how a server or software functions is a great way to pass time. But this process doesn’t have to be an exercise in ineffective inefficiency. In fact, tools are available to you that go a very long way to make the editing of config files much, much easier. I’m going to introduce you to a few such tools, to ease some of the burden of your Linux admin duties. I’ll first discuss the command-line tools that are invaluable to the task of making configuration more efficient. Read more

Why Good Linux Sysadmins Use Markdown

The Markdown markup language is perfect for writing system administrator documentation: it is lightweight, versatile, and easy to learn, so you spend your time writing instead of fighting with formatting. The life of a Linux system administrator is complex and varied, and you know that documenting your work is a big time-saver. A documentation web server shared by you and your colleagues is a wonderful productivity tool. Most of us know simple HTML, and can whack up a web page as easily as writing plain text. But using Markdown is better. Read more