Language Selection

English French German Italian Portuguese Spanish

Why I hate Ubuntu (even though it's awesome)

Ubuntu pisses me off.

A new release of Ubuntu means another attempt for me to come to terms with Debian's Celebrity Wild Child. I have installed every Ubuntu release since Warty. Each time, I start out being impressed and enthusiastic, become angry when something ridiculous happens, uninstall it in a fit of pique, and then post something on the internet about why I hate it. This time, I am resolved not to uninstall it. I have a second computer, so that living with Ubuntu doesn't mean living with all the time. I want to come to terms with Ubuntu, which is now the most popular Linux distro that ever was, and for good reasons. It's also the most despised distro among the established Linux community... also with good reason. In the past few days, I've read blogposts mocking Ubuntu users as "sheeple" and accusing Ubuntu haters of pettiness and jealousy.

My vague ambivalence toward the Ubuntu Humanity Juggernaut sharpened into dislike when I spent a good part of a frustrating afternoon trying to find KDE in the Butnut repositories. I repeated the experiment last night, with my latest install, and this problem still hasn't been fixed. There is no "kde-desktop" in the Ubuntu repositories. An apt-cache search finds a whole gaggle of KDE applications, but not the desktop itself.

The reason? Because Ubuntu has renamed KDE "Kubuntu-desktop".

Now, at first I was annoyed by the rechristening. I thought it was a pointless inconvenience, but I came to see that this kubuntu-fluxbuntu-xbuntu thing is a great idea for making the major desktop environments comprehensible to new converts to Linux. Looking back to my early days, it was a long time, more than a year, before I understood that Knoppix looked one way because it ran with KDE,and the reason why Red Hat 9 looked so different was because it used Gnome as a default, and that Red Hat 9 could easily be made to run KDE and look more like knoppix. Ubuntu's approach will make this a lot easier for a new user to take in.

This is why Ubuntu deserves its success, because it takes Debian-- one of the most reliable distros, and certainly the one with the richest arsenal of software applications, and makes it available to the Windows-afflicted with some very slick engineeering, engineering that is beyond intuitive. It's actually empathetic. Ubuntu is designed with some real insight into the thought processing of the beginning user.

So why am I pissed off? Because of a lack of empathy for me, the experienced linux user. In reeenginnering Debian, Ubuntu creates detours in the familiar highway of GNU-Linux administration, and then doesn't bother to put up a sign. And so, before I know it, I'm off the road.

The description of "kubuntu-desktop" in the repositories goes like this:

kubuntu-desktop - Kubuntu desktop system.

Redundant, isn't it? The desktop so nice, they named it twice.

Now, here's the thing that bugs me. Suppose they had put it in the repositories like this.

kubuntu-desktop - The KDE desktop for Ubuntu.

That's actually a better explanation, and I also believe that it would have put "kde" and "desktop" where apt-cache my apt-cache search would have found them. That's all that it would have taken for me not to spend an afternoon trying to find the KDE desktop, trying to visually scan all of the hundreds of listing generated by "apt-cache search kde", trying to find something that wasn't there.

I'd love for somebody to explain to me why I shouldn't be angry about this. A huge amount of time, effort, ingenuity and money has gone into adding very slick and intuitive interfaces and features so that the "everyday (i.e., Windows) users" can easily use Ubuntu. But it really looks like not one thought was wasted on me, the demographically insignificant Linux user, trying to find KDE the way he always has, after they've made their changes. It would have taken no time,no money, no ingenuity, to anticipate and solve this problem, and it wouldn't have interfered one iota with their grand design. All it would have required is for them to care. But why should they care about us? We're just the ones who gave them the software.

This is one particularly blatant example of how Ubuntu seems to punish me again and again for being a Debian user. You can grumble about Ubuntu being a mediocre product, but it's not. It's the most important Linux distro in years. In many ways, and, it's the breakthrough we're all waiting for, but I feel like those of us who have worked so hard for so long for Linux to succeed are not being considered at all. I'd just like to be invited to the party, that's all.

Another example, somewhat less blatant, and more geeky: I've often complained about the fact that Ubuntu has no /etc/inittab file, which I am used to editing to change the runlevel (to disable the X server and run from the plain console), and sometimes to add additional console screens. For a number of reasons, I prefer to run X from the console, rather than a desktop manager like kdm or gdm. For the first time in any Linux distro in my experience, the file isn't there in Ubuntu. So how about a text file, telling me what the hell is going on? It could be called "inittab-removed.READ_ME or something. Just a little sign post? Maybe some suggestions of what to look for, so I'm not just left standing in the middle of nowhere with my dick in my hand? If the runlevel can be changed, tell me how. If the runlevel can't be changed, tell me so I'm not wasting any more time on it. What would it cost for you to to show us that much respect for the veteran Linux user, since you've gone so far out of your way to do everything for the Windows user short of wiping his nose for him?

The Ubuntu Code of Conduct says that when there are disputes, consult the community... and that's what I have done here. If anybody has another point of view, I'd like to hear it.

Comment viewing options

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

I'm posting this tonight.

Because if I leave it in my browser window all night, I'll lose it... but I'll edit it tomorrow. You might want to wait until the final version before you post your flames about how I'm a paid troll for Microsoft.

Okay, it's essentially complete... FLAME ON!

IIRC it works the other way, too

If you install Kubuntu, and later want to install GNOME, you have to install the "ubuntu-desktop" meta-package, instead of firing up Synaptic and choosing the individual GNOME components you want.

If you don't, you might reboot to find that (even though you can still choose it, instead of gdm, with the "dpkg-reconfigure xdm" command) kdm no longer works. If you prefer kdm over gdm, this is very frustrating. I don't know if that's been fixed in v7.10 or not.

Personally, as a user of Debian, my problem with Ubuntu and its siblings ("hate" is too strong a word; it's just an OS, after all) was said much better than I ever could by Martin Krafft, the guy who wrote The Debian System, in a blog post he made in July, 2006. It's still relevant today.

It's a love-hate thing.

I never thought about it before, but "hate" is a word that is defined by its context with an amazing degree of precision. If I say that I hate oatmeal, or Windows Vista, or "Seinfeld", or Dick Cheney, or my parents, or Catholics, the word means something dramatically different in each case. (None of these statements are true, by the way. Okay, maybe the one about Dick Cheney.)

More in Tux Machines

GitLab Web IDE

  • GitLab Web IDE Goes GA and Open-Source in GitLab 10.7
    GitLab Web IDE, aimed to simplify the workflow of accepting merge requests, is generally available in GitLab 10.7, along with other features aimed to improve C++ and Go code security and improve Kubernets integration. The GitLab Web IDE was initially released as a beta in GitLab 10.4 Ultimate with the goal of streamlining the workflow to contribute small fixes and to resolve merge requests without requiring the developer to stash their changes and switch to a new branch locally, then back. This could be of particular interest to developers who have a significant number of PRs to review, as well as to developers starting their journey with Git.
  • GitLab open sources its Web IDE
    GitLab has announced its Web IDE is now generally available and open sourced as part of the GitLab 10.7 release. The Web IDE was first introduced in GitLab Ultimate 10.4. It is designed to enable developers to change multiple files, preview Markdown, review changes and commit directly within a browser. “At GitLab, we want everyone to be able to contribute, whether you are working on your first commit and getting familiar with git, or an experienced developer reviewing a stack of changes. Setting up a local development environment, or needing to stash changes and switch branches locally, can add friction to the development process,” Joshua Lambert, senior product manager of monitoring and distribution at GitLab, wrote in a post.

Record Terminal Activity For Ubuntu 16.04 LTS Server

At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands. Read
more

Linux Kernel Maintainer Statistics

As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems. Read more

Security: Updates, Trustjacking, Breach Detection

  • Security updates for Monday
  • iOS Trustjacking – A Dangerous New iOS Vulnerability
    An iPhone user's worst nightmare is to have someone gain persistent control over his/her device, including the ability to record and control all activity without even needing to be in the same room. In this blog post, we present a new vulnerability called “Trustjacking”, which allows an attacker to do exactly that. This vulnerability exploits an iOS feature called iTunes Wi-Fi sync, which allows a user to manage their iOS device without physically connecting it to their computer. A single tap by the iOS device owner when the two are connected to the same network allows an attacker to gain permanent control over the device. In addition, we will walk through past related vulnerabilities and show the changes that Apple has made in order to mitigate them, and why these are not enough to prevent similar attacks.
  • What Is ‘Trustjacking’? How This New iOS Vulnerability Allows Remote Hacking?
    This new vulnerability called trustjacking exploits a convenient WiFi feature, which allows iOS device owners to manage their devices and access data, even when they are not in the same location anymore.
  • Breach detection with Linux filesystem forensics
    Forensic analysis of a Linux disk image is often part of incident response to determine if a breach has occurred. Linux forensics is a different and fascinating world compared to Microsoft Windows forensics. In this article, I will analyze a disk image from a potentially compromised Linux system in order to determine the who, what, when, where, why, and how of the incident and create event and filesystem timelines. Finally, I will extract artifacts of interest from the disk image. In this tutorial, we will use some new tools and some old tools in creative, new ways to perform a forensic analysis of a disk image.