Language Selection

English French German Italian Portuguese Spanish

Church of Linux

Filed under
Linux

Linux, or Loonix as some of my layman friends like to call it has been around for years now and with the emergence of Ubuntu we’re starting to see greater uptake in the consumer arena that has been ruled for so long by Windows. Microsoft has even gone as far as mentioning Linux as a threat to it’s business. However, much like the Christian Church, the Church of Linux has seen many schisms. Often they are completely non-confrontational and are motivated by good reasons but with the vast number of Linux distributions (Distrowatch lists 312 variations) it’s difficult to choose which one to try.

For the new user, Ubuntu is an obvious choice, but do they really want Ubuntu or Kubuntu? Until they have tried both they won’t know which is better for them.

rest here




It doesn't seem like the blogger wants any comments

I don't whether he only approves comments in favour or if he just doesn't care if anyone uses the comment feature. Anyway, I post my comment here, not because it's important, but that it annoys me that I spent 5 minutes of my coffee break on this matter.

"If you use Distrowatch as a reference then your suggestion is already implemented. Check out the “Major Distributions” link, it will lead you to a selection of a few, each with a list of “Available editions” and “Alternatives” (in many cases spinoffs).

The rest of the argument is futile, and has been around for a long time. Basically you would need to kill the basic idea behind free software to achieve what you’re talking about. If all distributions are good at sending bug report upstream, the main development of software used will progress just as good.

The 312 distribution argument, changing only by current number, is totally out of context, except if you’re actually using embedded firewalls also as desktops, how that now would work. A lot of distributions are remasters to give better language support, and as such maybe also aimed at serving educational or other systems with well integrated operating system. Some are just personal projects made available to the public. Others are limited to work as jukeboxes or other multimedia boxes. Usually the massive number of distribution argument is used by supporters of proprietary software.

The biggest infrastructure to push Linux development ahead is anyway in the hands of a few big distributions, something that doesn’t change in either direction because of your “totalitarian” approach to free software. Just because you block some from using their freedom to fiddle with whatever they want, it won’t translate in 100 blocked developers equal to 100 more developers added to development of the chosen ones.

Linux is software made by users for users. Besides some crucial battles for user rights, which in a sense is a cross-platform concern, Linux evolves spontaneously. Is it really a good idea to out of sudden kill off spontaneity and expect all to join a corporate style of management?"

Comment viewing options

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

More in Tux Machines

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)