Remote-controlling desktop computers from mobile devices is an idea that is typically implemented in the form of an Android/Iphone app that connects to the controlled computer over SSH, VNC, RDP or some proprietary protocol typically requiring a closed-source server component.
It had occurred to me a while ago that it shouldn’t be too difficult to write a webapp that would turn any mobile device with a web browser into a remote control for the server its running on, and I was wondering why I didn’t see any implementations of that idea around.
Well now there is one such implementation in the form of “Linux Remote Control“.
One of the things I find most annoying about Linux distributions is that when it comes to distribution-oriented tools, they tend to make other distributions feel like second-class citizens even when compared to Windows. One such example is the Ubuntu One service which had a Windows client released recently and will soon see a Mac client while it is yet to be unsupported on any other distro besides Ubuntu. Another such, albeit smaller, example is the Fedora liveusb-creator tool.
The Fedora liveusb-creator tool is used when one wants to install Fedora while using a USB stick rather then a CD-ROM. While Ubuntu does include a comparable tool called “Startup Disk Creator”, that tool only supports creation of bootable USB sticks for Debian-derivative distributions.
Installation of the liveusb-creator tool is of course extremely easy on Fedora where it is accessible directly from the distribution’s repositories, the tool’s website also provides a Windows installer, but when it comes to other distributions the site resorts to providing a source archive without even including instructions as to what packages might be needed to run it.
Fortunately for users of other distributions, the Fedora liveusb-creator tool is written in Python, therefore running it on other distributions is a rather simple task, following are 3 simple steps required to use the liveusb-creator on Ubuntu, similar steps may apply to other Debian-derived distributions as well.
Syncany is n interesting project, its goal is to create a client for cloud-storage service, similar to what DropBox or Ubunto One provide. The interesting aspect is that it doesn’t come bundled with is own storage service, instead it provides plugins to connect to various different services.
If Syncany succeeds, it has the potential to level the playing field between the various storage providers and put the power to select them back in the hand of users.
But the possibilities don’t end there, suppose for example, Syncany includes a plugin to multiplex your data between more then one storage provider? Or maybe aggregate the space they provide?
Well, I couldn’t let such reconciliation of my hobbies go uncommented, its not often that I get to have a post go simultaneously in the Ubuntu and Anime/Mange categories, its really nicely drawn as well.
Usability bugs are nasty, they tend to be a major point of frustration for novice users, yet their importance is sometimes hard to explain to developers.
An even worse situation occurs when such bugs, once worked around, come back to bite you in a later software release because of a lack of developer foresight.
I am going to discuss a work around for a bug I’ve already discussed in the past. I’m going to skip going into the details of how this bug arises, please read the previous post for those.
Well, I wanted to describe some of the relatively minor sound problems I’ve encountered after upgrading to Hardy, while giving some kind of an overview of how things are with audio and Linux and why are we seeing problems with this release, but this article does a much better job at it then I could.
Very briefly, the solution for my audio problems was to set all the options to “PulseAudio Sound Server” in the “Sound Preferences” administration applet, and install the “libflashsupport” package.
Update: Another class of applications that is affected by the switch to PulseAudio is those appications that use the SDL library. Thos can be configured to use PulseAudio exclusively by installing the “libsdl1.2debian-pulseaudio” package and making sure no other “libsdl1.2debian-*” package is installed.
As experienced computer users know, the fresh-released versions of products are typically not very stable and reliable. It takes a few months (Typically until the x.1 version is released) for the product to really stabilize and become production-ready. This also seems to be true for Free and Open-Source software, though the maturing rate seems to be faster.
Knowing that, I typically wait a couple of months after an Ubuntu release before I take the time to upgrade. When it comes to Hardy Heron, the latest version of Ubuntu, a further reason not to upgrade was provided by the fact that up until now it didn’t include a stable version of Firefox.
I finally decided to take the time and upgrade the Ubuntu version on my personal home computer yesterday. The upgrade didn’t went as smoothly as I hoped it would. Most of the issues can be blamed on the manual tweaks I’ve made to my system. Not all, however.
Below is a list of the issues I’ve encountered during and after the upgrade, and the solutions I came up with (when applicable).