• Home

CodingExperiments.com

$ sudo make money

Search

Category:

  • Apple Inc.
  • Facts
  • Fun
  • Google
  • Google Android
  • Ideas
  • Internet
  • Linux
  • Microsoft
  • Programming
  • Rants
  • Security
  • Uncategorized
  • web 2.0

Archives:

  • April 2010
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007

Pages

  • About
  • About
    • The Authors
  • Commenting your code
  • How to Write Papers with Groff
  • ModCMS Anti-Spam Component Set
  • ModCMS Technical Specifications
  • Regular Expressions Guessing Game
  • Saving code directly to a web server
  • The (Almost) Perfect PHP 404 Page

Meta:

  • RSS
  • Comments RSS

Awesomeness tracker

CodingExperiments at Blogged View blog authority
Free Page Rank Tool

A Few Problems With Ubuntu

June 7th, 2008 by i80and

Userfriendly strip on Linux distro fanboys.
UserFriendly and everything related to it copyrighted and trademarked by J.D. Frazer. Used with permission.

Since before the dawn of time, Linux users have argued over which distribution to use. Me, I’m a Slackware man. But by far, Ubuntu, a massively popular[1] Debian-based distribution, is the one most recommended by everybody. Even I recommend it for newbie users simply because it’s easy to use. But under that famous shiny orange surgery coating, I believe lie some annoying problems. And so I will give an outline of why exactly it may not be the best choice for at least some users.

  • Package manager. Ubuntu, as with its father distribution, Debian, uses the dpkg package manager. Of course, people tend to use apt-get or Synaptic as a frontend to it. But I believe that it has one problem: interactive package installation. This is one problem that, for a wonder, the RPM developers dodged. When I’m installing a truckload of packages, and suddenly a sparse and somewhat ugly dialog interrupts whatever I’m doing and halts the installation just to ask me what services should be restarted for the installation of package X, am I going to be happy? Quite simply, I don’t care. I just accept the defaults And a more newbie-ish user is definitely not going to care. All in all, this makes package installation sometimes look annoying and unpolished. If I want to configure something, give me a post-installation summary of what needs to be done, and I’ll handle it myself, thank you very much. Either that, or I’ll ignore it. But that’s my choice to make, not some packager’s.

    EDIT: The author of the seemingly excellent PackageKit remarked on linux.com on what’s wrong with debconf, agreeing with me on the pointlessness of asking most users for things they don’t care about.
  • Package Documentation. This is related to the above. Basically, Ubuntu/Debian splits every library into three packages: the shared library, the development headers, and the documentation. As a software developer, I think I can say that this is incredibly annoying. I can deal with the splitting of development headers; that makes sense. But if you want the development headers, generally you want the API documentation with them. For the life of me, I can’t find what package contains the man pages for POSIX functions. This was never a problem on Slackware.
    I certainly can see why this would be done; but sometimes, it just causes more hassle than it’s worth.
  • Package Naming. I’m really beating the package manager horse, aren’t I? Finding a library in Ubuntu/Debian is all too often a somewhat hit-or-miss proposition. Hmm, I want to install GTK+. Every other distribution names it gtk+2.0, or something along those lines. Makes sense; that’s the LSB recommendation. But Ubuntu/Debian just has to be different and name it libgtk2.0-0. Small issue, but is kind of annoying. What black magic do they use for figuring that one out? I don’t know, nor should I have to know. It’s fairly common to see seemingly random integers added to the end of package names; probably it’s some sort of transitional thing, but it’s still annoying. And against the LSB standard.
  • Bootsplash. Ubuntu uses USplash as its graphical boot system currently. However, this choice has been critisized, and for good reason. First of all, I have never seen a computer on which it doesn’t have visual glitches. Either the throbber flickers, stuff gets repeated and mistiled, or it just doesn’t show up. Furthermore, creating themes is quite simply a headache. As a poster on the above forum thread pointed out, when you need a makefile and C programming experience to make a theme, something is wrong. That’s right; themes are written in C, and therefore must be recompiled for every target platform. Lastly, themes are capped at 8-bit color. Compared to the likes of Splashy (a brother to USplash that supports 24-bit color), this is downright 90s-esque.I will grant that bootsplash is kind of a trivial thing; however, trivial things do matter. And does this represent a flaw in the Ubuntu developers’ mindsets?

All in all, when I come down to it, some of my more major complaints are somewhat illogical; Ubuntu seems slower than Slackware, but how much of that is just GNOME’s bloat? I recall running Xubuntu and Slackware/Xfce on an old 400mhz system, and while Slackware was a bit faster as I recall, both crawled. And upstart isn’t actually too bad, when I look at it. Sure, it seems like change for the sake of change to some degree, but it does offer some interesting advantages (although I’m not sure any of them other than parallel startup are being taken advantage of currently). My other traditional problem of stability also seems somewhat unfounded when I come down to it; since I stopped using Kubuntu, I’ve only had one real “crash”. And booting problems seem to be specific to 7.04 Gutsy Gibbon. There are some annoying problems with Ubuntu, but the ones that actually irritate me are general to Debian/Ubuntu.

It seems that I’ve been unfair to Ubuntu to some degree. I’m sure that it’s slower than Slackware, but it does seem to have fewer issues on this whiny laptop. It’s still not my favorite distro, mind you, but I will be less likely to veto it when planning an installation.

[1]: 2346 hits per day according to DistroWatch as of June 7th, 2008.


Posted in Uncategorized | View Comments

  • MatÄ›j Cepl

    libgtk2.0-0 is a product of the fact, that dpkg doesn't use file dependencies. You see in RPM package you can say (or rpmbuild says, it doesn't matter) that package empathy requires libtelepathy-glib.so.0 (which is the file name in /usr/lib of the particular library). Debian packages don't do that -- they can have dependencies only on the names of the other packages (either written in debian/control file manually or supplied during the building process automagically). However, libraries are tricky -- you don't want to have anyversion of binary library, but only such version which supports some particular version of ABI. Which leads to the final .0 in libtelepathy-glib.so.0 And if you want to have all this in the name of the package (because packages can depend only on the name), you have to have pretty strict policies about how to call the package. The result is that package empathy in unstable (http://packages.debian.org/sid... requires libtelepathy-glib0.

    There are two important results from this (and that's the reason why I tried to avoid any value judgments on RPM/Debian supporting/not-supporting file dependencies). From this Red Hat employee's point of view nice result is that packaging of a library to RPM is no more complicated than packaging any other package with anything else. I remember from my Debian days, that I fought six hours (and I was not a packaging newbie then) to make library packaged, and I still was not able to satisfy lintian to be happy with the result.

    Negative result of that is that depsolving during the package installation/update is by magnitude more complicated -- both in terms of requirements of time and CPU/RAM. Which is one part of the story that yum is slow (and although it isn't that much anymore, it is probably still slower on the similar sized distribution than apt-get), and other result is that probably there won't be anything as comfortable and fast for Fedora as is aptitude for Debian.

    You just have to pick your poison.

  • John Dalton

    I'm an Ubuntu fan, though I don't think distro preference should be a religious issue. ;) Regarding dpkg vs. rpm, I find them to be pretty much equivalent. I also avoid using either of them directly without some sort of front-end. Unattended installation is certainly possible with apt - if you're interested, start with --assume-yes and --trivial-only in the man page for apt-get.

    As for package naming, they're different - but consistently different, so that's ok with me ;)

    I've never had a problem with the splash screen, and I've usually run it on decent machines where speed wasn't an issue.

    But yeah, ideally people will try multiple distros and find the best fit for them!

  • Evets

    Ubuntu's package manager is actually what made me decide to stay with ubuntu. After trying MANY different distros, I foudn that despite the fact that I didn't like Debian, I like apt-get over RPM or any of the other package managers I tried, and so I looked for a good debian-based distro. Behold! Ubuntu! \o/

    It seems to me that many of your complaints against Ubuntu are simply a matter of preference, or just plain "That's not the way I'm used to doing it," which is perfectly fine and understandable. Coming from slackware world to ubuntuland must be a rather disorienting experience.

    Anywho, interesting blog post. Cheers from ubuntuland!

  • GregE

    Package management is a lot to do with what you are used to. I am a long time Debian and Ubuntu user. I recently tried SUSE and found Yast the most unfriendly cludgy piece of crap in the universe. I am sure if I persisted I could learn to use it, but it seemed to take forever to do the most simple tasks.
    Ubuntu's big strength is the shear weight of numbers, there are howtos and user guides by the tens of thousands, so that any problem can be solved by a simple google search. I still use vanilla Debian on one of my machines, but the other four are Ubuntu.
    I do not like the latest xorg.conf as used by Hardy Heron where all config is just device "as configured" which is most unhelpful when it does not work. Luckily the old config files still work, I still have to do manual tweaks on my venerable Dell 1100 Inspiron to get the Intel graphics to work.
    No Distro is perfect, nor suits everybody. I like Ubuntu, but then I used to be a Red Hat person, a Suse user, a Gentoo person, then Debian testing, then Ubuntu. Next year?

blog comments powered by Disqus

 
Wordpress Themes by and Website Templates by Blogcut Blogged Blog Directory Blog Directory - Blogged