Test drive : Ubuntu 13.10 “Saucy Salamander” (Nightly Build)

The upgrade season is coming again. As I do twice a year I downloaded from Ubuntu download page the currently available version (not called beta anymore) of the October Ubuntu release. I prepared my USB disk in order to test the incoming release live on my computers.

On the EEEPC 900

After booting from the USB disk everything proceeded regularly until I arrived to the “Try or Install” screen. The top panel appears oddly expanded down to almost half screen.

Troubles trying to install Deepin Desktop Environment

I have been positively impressed after my latest test of Deepin Linux, especially of its desktop environment (Deepin DE). I so decided to try to install, separately, Deepin DE on my desktop computer.

The beginning

Instructions I found around the 'net, here, there and other similar pages, are roughly all the same: add Deepin sources to “/etc/apt/sources.list” file

deb http://packages.linuxdeepin.com/deepin raring main non-free universe
deb-src http://packages.linuxdeepin.com/deepin raring main non-free universe

Then I imported GPG key for such sources

wget http://packages.linuxdeepin.com/deepin/project/deepin-keyring.gpg
gpg --import deepin-keyring.gpg
sudo gpg --export --armor 209088E7 | sudo apt-key add -

at last I launched the apt-get command as usual

sudo apt-get update

sudo apt-get install dde-meta-core.

Things start going wrong …

Just after the installation process ended nothing happened, I logged out but I didn't find the option to log back with Deepin desktop. I continued working and, after some time, I got a incomplete update error message from Ubuntu update software. The error message suggested to “Upgrade” the distribution. At this point the system was completely wrecked: I rebooted and I got a system who identified itself, using the lsb_release command, as “Deepin Linux”. Unity was barely working while Gnome shell didn't start at all. Looking on the 'net I then discovered Deepin desktop uses its own patched versions of fundamental software like Compiz so installing it on an existing system is definitively a risky business.

Test Drive : Linux Deepin 12.12 on the EEEPC

Some time ago, while looking for some Linux related new on the 'net, I read this review about a Linux distribution I never heard before: Deepin.

Deepin is a Linux Distribution, based on Ubuntu, originally created for the Chinese users pool but also available in English language. Apart from positive reviews what really interested me has been the fact Deepin comes with its own desktop environment (Deepin DE) based on Gnome Shell.

I so decided to test how it works on the EEEPC.

First impressions

I prepared a bootable USB disk with Deepin with the usual process: download the ISO image from Deepin download page then write to the flash disk using Unetbootin.

Here is how Deepin looks like just after boot:

I must say Deepin default theme and wallpaper appear aesthetically well refined. This means nothing on the long run but might be dramatically important to give a good first impression to new users.

Mercurial and Mercurial-server : playing with DVCS (part 2)

In my previous post I moved my first steps with Mercurial DVCS, now I'll install a Mercurial server implementation and configure both my computers to access it using SSH protocol.

Mercurial-server

With DVCS you don't have to use a central server, repositories could be shared over LAN using shared folders, but this doesn't mean you can't have one. Various mercurial server side implementations exists, using different protocols. May be I'm too server-client minded but I didn't feel satisfied by just sharing repositories over a shared folder so I decided to install Mercurial-server.

Installing Mercurial-server is an easy task the command

sudo apt-get install mercurial-server

complete the installation process and the creation of the application user (hg). A bit more complex is configuring SSH for accessing the server, I mainly followed instructions from here and from Mercurial-server documentation.

Mercurial-server uses public-key authentication and SSH-Agent in order to grant access to its clients, so the first step has been to generate a keys couple for SSH. The ssh-keygen command does this interactively.

maxx@VeritonS661:~$ ssh-keygen -t dsa

Generating public/private dsa key pair.

Enter file in which to save the key (/home/maxx/.ssh/id_dsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /home/maxx/.ssh/id_dsa.

Your public key has been saved in /home/maxx/.ssh/id_dsa.pub.

I then copied the public key in mercurial-server keys configuration path and told mercurial-server to refresh its authentication files, using the following commands:

ssh-add -L > maxx.key

sudo mkdir /etc/mercurial-server/keys/root/maxx

sudo cp maxx.key /etc/mercurial-server/keys/root/maxx /veritons661

sudo -u hg /usr/share/mercurial-server/refresh-auth

the usual path for mercurial-server keys is (for root users)

/etc/mercurial-server/keys/root/<user-name>

but if the same user must be accessed from different machines a different path is used:

/etc/mercurial-server/keys/root/<user-name>/<machine-name>

since I was going to add the maxx user from the EEEPC too I had to use, of course, the second from. On the EEEPC side I generated SSH keys at the same manner then, after logging to the desktop computer (the server) with:

ssh -A veritons661

and I eventually registered EEEPC's maxx user like this

ssh-add -L > eeepc900.key

sudo cp eeepc900.key /etc/mercurial-server/keys/root/maxx/eeepc900

sudo -u hg /usr/share/mercurial-server/refresh-auth

Mercurial and Mercurial-server : playing with DVCS (part 1)

Version control systems (VCS) are an indispensable tool when programming and sharing code even for small groups. Even while programming alone, but on different computers, a version control system could easily prove useful for securely sharing code between desktop and laptop computer. I use daily SVN, as version control while at work. For my homely experiments, instead, I decided to install something different: Mercurial, a distributed version control system (DVCS). Distributed version control systems, most famous are Git and Mercurial, do not rely on a central server to keep the code repository, in DVCS every developing computer keeps its own copy of the repository. What interested me in DVCS was the capability to do version control also when off-line and also, of course, the chance to learn something new.

Installing Mercurial (command-line and plugged-in)

Installing Mercurial command-line version it's quite trivial:

sudo apt-get install mercurial

Both Eclipse and Netbeans offers their plug-ins to interface with Mercurial. Netbeans plug-in is already provided with version 7.3.1 I have installed on the EEEPC. On Eclipse, desktop-side, installing the MercurialEclipse plug-in has been as simple as selecting it from the Eclipse Marketplace and following installation wizard.