Language Selection

English French German Italian Portuguese Spanish

Ubuntu 13.10 (Saucy Salamander) review: Smart Scopes in, Mir out

Filed under
Ubuntu

With relatively little that's obviously new, the final release of Ubuntu 13.10 (Saucy Salamander) seems a somewhat obligatory event. Of course it does feature a new revision of the Linux kernel (version 3.11.0-12) and a new revision of Unity. Also, as with every release, a lot of work has been done improving the various modules that make up the operating system, fixing bugs, eliminating vulnerabilities and improving performance. However, Ubuntu 14.04 LTS, due for release on 17 April next year, will now perhaps come as even more of a shock if its promised big changes are fully realised.

Mir fails to make the cut

Canonical has said that Ubuntu 14.04 and the Unity Next interface, which will support desktop, TV, tablet and smartphone form factors, are dependant on Canonical's new display server, Mir. With this in mind, the Ubuntu developers had hoped to have an early release of Mir running in Ubuntu 13.10 — and indeed it did feature as an option in the beta release, as noted in our Beta 1 preview. Unfortunately, Mir has now been dropped from 13.10 due to technical difficulties and the final release reverts to the X Windows server. Officially this is due to problems with multi-monitor support, but Linux developer Matthew Garrett blogs that, in his opinion, there is rather more to it than that.

rest here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more