Things That Went Right

On the flip side of the things that went wrong, we have the things that went right. Most of the Ubuntu experience went right and has been covered previously, so this is going to be a catch-all for other things about Ubuntu that impressed me, but don’t necessarily fit anywhere else.

One of the nicer features of Mac OS X that you don’t see mentioned very much is the Keychain, a credential management framework for applications to use to securely store passwords and the like. Such systems aren’t rare – even Windows has something similar through its Credentials Manager – but Mac OS X is unique in that its implementation at least gets used, at times.

I had not been expecting something similar in Ubuntu, so it caught my eye when a Mac OS-like password box came up when I was logging in to my file server. As it turns out Ubuntu has similar functionality through the Passwords and Encryption Keys application. And since Ubuntu heavily uses the GNOME desktop environment that this application is a part of, a number of its applications are built against the keyring and use it.

It’s not quite as tightly woven as Keychain is under Mac OS X, but it’s better utilized than Windows and used enough that it makes sense to visit the keyring application. The biggest holdout with a stock install is Firefox, which uses its own password manager regardless of what platform it’s on.

Another thing that caught my eye was Ubuntu’s archive manager, called File Roller here. As we’ve lamented many, many times before, Windows’ archive management abilities are terrible. Files are slow to compress, files are slow to uncompress, and just supporting Zip files isn’t quite enough. Mac OS X does a bit better by being faster, but it also has absolutely no support for browsing Zip archives, it just packs and unpacks them. Most power users I know will have something like WinRAR or BetterZip installed to get a proper archive browser and wider archive support.

File Roller is a complete archive manager, and it supports slightly more exotic archive formats like RAR along with the customary Zip and *nix standard of GZip. The biggest knock against it when it comes to archive formats is that it can read more than it can write, RAR again being the example here.

This also brings up an interesting quirk with archives under *nix that you don’t see under Windows. The Zip format specifies it as being both a container for multiple files and a compressor for those files. GZip on the other hand can only compress a single file – so when it comes time to compress multiple files, they must first be packed in a compressionless tarball (TAR), and then the tarball is compressed, resulting in .tar.gz. The quirk is that the Zip format compresses each file separately, while .tar.gz by its very nature compresses all the files together at once; this is commonly known as solid archiving.

Depending on the files being compressed, solid archives can have significant space advantages over individually compressed files by taking advantage of redundancy between the files themselves, and not just the redundancy in individual files. This is also why WinRAR is so common on Windows machines, since the RAR format supports solid and individual archiving.

Now the downside to solid archiving is that it takes longer to pull a file out of a solid archive than an individually compressed archive, since everything ahead of the file must be decompressed first in order to retrieve the data needed to recreate the desired file. So solid archiving isn’t necessarily the best way to go.

Ultimately with the wider support for archive formats under Ubuntu, in some situations it can achieve much better compression ratios than what can be done under Windows. Windows isn’t entirely helpless since when it comes to installers they can use MSI installers (which use solid compression), but as far as plain archives are concerned the only built-in option is individual archiving. It’s a small benefit that can pay out nicely from time to time for Ubuntu.

Things That Went Terribly, Terribly Wrong Wine
Comments Locked

195 Comments

View All Comments

  • Eeqmcsq - Wednesday, August 26, 2009 - link

    for your time spent on writing this article. I've made the jump to from Windows to Ubuntu (and Xubuntu for my older computers) back around 7.10 and 8.04 and I went through some of the headaches in adjusting to Ubuntu, but I eventually solved all of them and I'm quite settled in now.

    One comment about finding help in the form of command line instructions, rather than GUI instructions. GUI instructions for Ubuntu would not be useful for Kubuntu or Xubuntu, since they use different window managers. The command line solutions usually work for all three.

    Also, boot times were noticeably improved in 9.04. Perhaps you can run a quick retest on it.

    And you CAN install stuff when using the live CD. I've installed a couple of temperature monitoring utilities when I was stress testing my motherboard.

    Finally, thanks again for writing such a thorough look into your Ubuntu experiences. It was a great read in seeing how far Ubuntu has come and what it still lacks.
  • fepple - Thursday, August 27, 2009 - link

    Yeah, you can set the APT sources to use a CD. There is an option for it 'system' > 'administor' > 'software source', or you can edit the /etc/apt/sources.list file
  • clarkn0va - Wednesday, August 26, 2009 - link

    [quote]since SMB is the predominant protocol for consumer file server gear, it’s a fair test of such use.[/quote]

    While this comment is not false, it presents a lazy approach to comparison; it's a one-sided contest, and Linux, pitted against Windows on home turf, doesn't stand much of a chance.

    You as much as acknowledge this in the article, so why not provide some counterpoint? For example, consumer file server gear, even if it supports SMB almost ubiquitously, is usually *nix-based. So instead of just showing Windows and Linux clients interacting with Windows servers, show them interacting with *nix servers as well. Do some NFS transfers as well; NFS is well supported in consumer NAS these days.

    You also really missed the boat on the video drivers. 8.04 was not the first Ubuntu release to include the Restricted Drivers Manager (known simply as "Hardware Drivers" in later releases). This handy app will identify hardware, such as AMD and NVIDIA GPUs, that can take advantage of proprietary drivers, and will offer to to install the same via synaptic (APT) with just a click of the mouse. No CLI, no headaches.

    Still, a thorough review, and generally well-researched. I'm looking forward to the 9.04 follow-up.

    Since you mentioned hardware HD decoding, I recommend taking a look at smplayer from the testing ppa (https://launchpad.net/~rvm/+archive/testing)">https://launchpad.net/~rvm/+archive/testing). Unfortunately vdpau doesn't work with the nvidia blobs in the default Ubuntu repos, but I believe there's a PPA providing vdpau-compatible blobs for anybody not wanting to do CLI installs.

    db
  • VaultDweller - Wednesday, August 26, 2009 - link

    [quote]While this comment is not false, it presents a lazy approach to comparison; it's a one-sided contest, and Linux, pitted against Windows on home turf, doesn't stand much of a chance. [/quote]

    This isn't Linux pitted against Windows on home turf, it's Linux pitted against Windows in the real world.
  • clarkn0va - Wednesday, August 26, 2009 - link

    Well, no doubt SMB is the dominant method of sharing files for consumers in general. Obviously comparing Linux to Windows makes sense in a world where Windows is the incumbent, but it's not the whole story.

    I hope Part 2 will address some of the objective benefits of Ubuntu, and not fall into the trap of "worse because it's not the same as Windows".
  • VaultDweller - Wednesday, August 26, 2009 - link

    I agree in principle, but there has to be a distinction between "Worse because it's not compatible with Windows," "Worse because it's not as easy as Windows," and "Worse because it's not the same as Windows." Die-hard *nix advocates tend to dismiss the first two as if they were the latter, and this tends to undermine their argument.

    Also, in some cases "Worse because it's not the same as Windows" can be a valid point, because the public has been trained to the point that the Windows way is the "intuitive" way. Of course, this isn't truly intuitive, as people who learned Linux first would find Linux methodologies more intuitive - but that's largely a moot point, as that's not the reality we live in today. You could say the same thing about the color red - in the western world, when we see red we can intuitively guess that it means Stop, or Warning, or Error, etc. The fact that this is not an understanding we're born with but rather a socially acquired intuition does not mean it would be any easier to suddenly change the color of traffic lights and expect people to adjust without problems.
  • Ryan Smith - Wednesday, August 26, 2009 - link

    All of the NAS gear I can get my hands on is either SMB only, or is a Time Capsule which is SMB + AFP. I don't have anything that does NFS, which isn't so much a comment on testing (I could always set up another box) as it is usefulness. NFS just isn't common on consumer gear; SMB is a more important metric if you're looking at file transfer performance, because that's what most people are going to be working with. This doesn't preclude doing NFS at a later time though.

    And the Restricted Drivers Manager is limited to the drivers in the Hardy repository, which means they're a year+ out of date.
  • amrs - Wednesday, September 30, 2009 - link

    Interestingly, if one checks the SmallNetBuilder NAS charts, it looks like out of 87 NAS devices, 49 have NFS. 56% in other words. And you say NFS isn't common? Really now? Seems a little biased to me.
  • ekul - Wednesday, August 26, 2009 - link

    While a lot of your issues have complicated solutions or lengthy technical backstories I can solve your complaint of smb shares mounted in nautilus not being useful in non-gtk applications in one simple command (or as you seem to hate commands the gui can do it too).

    theory: make a symlink to the directory nautilus mounts to so it can be easily accessed. Symlinks to directories or files are transparently (to users and applications) identical to the location they refer to. Windows doesn't have symlinks (only useless shortcuts) so it isn't surprising you were not aware to do it.

    howto: gvfs uses the directory /home/$USER/.gvfs as a mount point so link to it:
    ln -s ~/.gvfs ~/linkname

    howto gui: in nautilus go to your home folder then choose view -> show hidden files. Right click on .gvfs and choose make link. Then you can rename the link to whatever you want and hide hidden files again.

    hint: symlinks are your best friend. My home dir is littered with links to places on the filesystem I visit a lot to avoid a lot of clicking/typing
  • Ryan Smith - Wednesday, August 26, 2009 - link

    I suddenly feel very humiliated...

    The symlink is a very elegant solution, I'm embarrassed I didn't think of that myself. It's a bit of a lousy solution in that there even needs to be a solution, but as far as things go that's a very insightful suggestion.

Log in

Don't have an account? Sign up now