Language Selection

English French German Italian Portuguese Spanish

Cloned Distros: Why Ubuntu Sucks and Should be Banned

Filed under
Ubuntu

To write it down clearly: I don't like clones. There are too many distro's out there as it is. Over the last years I have had many people ask me: I have tried Distro X, Y and Z, can you help me? Just a while back a colleague told me, I have upgraded Ubuntu and now my server won't work, can you help me? Or constantly I get people telling me: "I have tried Clone of Clone X, Y, Z, it looks nice, but then I upgraded and it hosed my system."

In general problems can occur in any software, but more in those who are far from mainline and have been hacked around on code that has been maintained and crafted by original distributions. This is true with a clone, even more so with clones of clones or clones of clones of clones. The more removed from mainline or the original developer the bigger the maintenance issues.

REASON 1: 0 INNOVATION

Cloning one distro and giving it a few different packages and name and logo and call it a new distro with a new installer is not innovation and does not help the community overall. To call it a new distro is just plain and simply confusing to normal people out there. Greg KH, the kernel developer says it better than I could ever do, Ubuntu overall has contributed 100 kernel patches from 2004-2008, which is 25 per year!!!! Where is your innovation Mr. Shuttleworth?

rest here




I'm not going to bother signing up to post there, so...

Look, you can't tell me that clones are bad, and I'm a little bit unnerved in him calling offshoot distros, or "spins" clones. You can't tell me that it's not a good thing that a distro like PCLinuxOS bases itself off a very fine distro like Mandriva, but changes the very things users have been crying about for years (package management, stability, company's lack of listening skills with their community...) and improve upon them, while moving to a rolling release model to boot. I call that innovation. I call that building a better mousetrap.

Why drive a Ford Mustang when you can drive a Saleen or Roush Mustang for the same price?

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)