"A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects." (Robert A. Heinlein)

Wednesday, 6 January 2016

Ubuntu 15.10: Some post installation fix


After upgrading my desktop computer to Ubuntu-Gnome 15.10 I went on with installing software packages I needed and it took me a while to notice there were problems in my network disk mounts. I had the configuration copied from the previously backed-up “fstab” configuration file. Everything was working fine before upgrading but in the new installation the system started with the configured Samba shares unavailable. Manually re-executing the mount sequence (with command “sudo mount -a”) solved the problem until next reboot.
I checked the system log and got the following error message:

Jan 3 11:15:05 veritons661 kernel: [ 20.826880] CIFS VFS: Error connecting to socket. Aborting operation.
Jan 3 11:15:05 veritons661 kernel: [ 20.827770] CIFS VFS: Error connecting to socket. Aborting operation.
Jan 3 11:15:05 veritons661 mount[680]: mount error(101): Network is unreachable
Jan 3 11:15:05 veritons661 mount[680]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Jan 3 11:15:05 veritons661 kernel: [ 20.828593] CIFS VFS: cifs_mount failed w/return code = -101
Jan 3 11:15:05 veritons661 systemd[1]: media-nas.mount: Mount process exited, code=exited status=32
Jan 3 11:15:05 veritons661 systemd[1]: Failed to mount /media/nas.
Jan 3 11:15:05 veritons661 systemd[1]: Dependency failed for Remote File Systems.
Jan 3 11:15:05 veritons661 systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Jan 3 11:15:05 veritons661 systemd[1]: media-nas.mount: Unit entered failed state.
Apparently, during the boot process, the system tried to mount network drives before the network was up and ready. I quickly discovered I wasn't alone with my problem, AskUbuntu pages offered some solutions. The first I tried, using the “_netdev” mount option in order to force the system to wait for the network to be ready, didn't work for me. The second solution has been configuring the network shares to be mounted only at the first access using “noauto” and “x-systemd.automount” mount options.
Here is how my “fstab” configuration looks like:

# NAS
//192.168.0.110/sh_maxx /media/nas cifs noauto,x-systemd.automount,x-systemd.device-timeout=3,uid=maxx,credentials=/home/maxx/.smbcredentials,iocharset=utf8,sec=ntlm,file_mode=0777,dir_mode=0777 0 0
# Public
//192.168.0.110/public /media/public cifs noauto,x-systemd.automount,x-systemd.device-timeout=3,guest,uid=maxx,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
The network shares are now correctly mounted and there is no noticeable delay at first access. Only Nautilus seems to have been driven a little crazy about it since it shows drive icons doubled.

Thursday, 24 December 2015

Thursday, 3 December 2015

Ubuntu 15.10 “Wily Werewolf” on Veriton S661 (full install)

After almost one year I managed, just in these days, to change my Internet provider and have back my land-line ADSL connection. First things first, I started with updating my home desktop computer (the Acer Veriton S661) I left mostly unattended during this period since my mobile Internet contract was barely enough for daily connectivity needs. Unfortunately it seems my computer has been left too much without upgrading and the update process halted signaling many “404” errors while accessing to different repository locations. May be I could find another solution to upgrade my system but, since I usually keep the “/home/” folder on a separate partition, I decided to go for a complete re-installation of latest Ubuntu-Gnome release.

The installation process

I proceeded with installing as usual, prepared a USB disk with Ubuntu's tool, booted from it and went on with installing. On order to maintain my separate home partition I selected the custom “Something else” installation type



Monday, 23 November 2015

Blog-Birthday Seven

Also this seventh year of blogging has passed. Unfortunately this year I have expereinced many Internet connection problems: my land-line appears to have been caught in a undeclared war between two of the biggest and greediest italian Internet providers. So I'm tied to connecting to the internet using my cell-phone since almost one year. This kept me from most of the upgrading (my computer) and updating (myself) and, of course, from posting about it. 
By the way this is no gain in complaining (at least here) so let me thanks all my readers and visitors and hope next blogging year will be more proficuous.

Friday, 25 September 2015

The quest for new languages: Python

It happens, sometimes, that I download a “new” programming language or a framework or library in order to give it a try. Of course the word “new” is relative to my personal or professional experience, mostly orbiting around the Java galaxy. This time the “new” programming language is Python. Python is, of course, a widely used and far from being a new programming language but I never had the thought of giving it a try before.

Python on Eclipse: PyDev

I'm willing to learn new languages but I'm not so eager to install and use a new IDE while doing it. I so went looking for a Python development Eclipse plug-in and the choice fell on PyDev. Installing PyDev on Eclipse has been quite simple, just matter of selecting it on Eclipse Market Place and completing the installation wizard.
Before creating the first project PyDev plug-in needs to know where python interpreter is. There is a handy automatic search feature but I preferred the manual configuration in order to have more meaningful configuration names.