AdSense Mobile Ad

Monday, November 3, 2008

Sun Solaris 10 update 6 (10/08) has been released

Sun just updated its Solaris 10 operating system and began to ship Update 6 this week. There were no big changes since last release, probably the most notable being a bunch of ZFS improvement such as:
  • support for ZFS root filesystems during setup, which is something which makes me think about upgrading a couple of server! ;)
  • ZFS rollback without unmount
  • zfs send supports incremental backup from snapshot
  • gzip compression support for ZFS file systems
  • double parity RAID-Z support
A descriptive list of improvements can be found here and the complete What's new document from the documentation center can be consulted here.

Please consult the list of known bugs before deploying this version of Solaris 10, as usual. The only thing that blocks me from deploying Solaris 10 on my development workstation since version 05/08 is bug 6586621 which hasn't been fixed yet.

Sun xVM VirtualBox 2.0.4 has been released

In less than two months Sun xVM VirtualBox version 2.x has undergone the third minor revision and VirtualBox 2.0.4 has been released.

As a long time VirtualBox user, I'm pleased to see this product evolve. I'm running Debian 4.0 testing, Ubuntu 8.10, Windows Server 2003 and Windows XP on a Solaris Nevada (b101 actually) guest on an HVM capable machines and it's a long time I'm not experiencing any problem during my daily life with VirtualBox. And now that version 2.x introduced support for 64 bits kernels, I think I'm not going to install a brand new image in a very long time: I have a backup of a snapshot of the Virtual Machines in a ZFS snapshot and whenever I rollback or clone an image, it's a no-brainer 5 minutes work.

The product covers almost 100% of my needs: the only thing I would really like to see in VirtualBox is audio input support for Solaris guests.

Looking forward to see Sun xVM server released: http://xvmserver.org/.

Congratulations, Lewis Hamilton

Well well well, if someone told me a long time ferrarist as I am would be saying this as soon as we lost the World Championship at the last bend, I wouldn't believe it. But after seeing the last race of this suffered season, in which one year more the title has been assigned only at the last race, I want to congratulate with Lewis Hamilton. I just think a great pilot has demonstrated who he is and Formula One has a new talent to entertain us in the years to come.

I only hope seeing Lewis wearing a red suit very soon.

Connecting with SSH without typing a password

I'm heavily relying on some remote machines to get some jobs done so SSH is a tool I used daily. The downside of being sit in front of a terminal opening and closing many SSH connections is that you have to type in your password over and over again.

I started looking at SSH documentation hoping to find a way to ease this pain without trading off SSH inherent security. I'm using version 2.0 of the SSH protocol and the solution is authenticating using a key.

The first step is creating RSA private/public keys with a tool which comes with SSH:

$ ssh-keygen -t rsa


ssh-keygen will then produce the following files in the ~/.ssh directory: id_rsa and id_rsa.pub. The complete output of ssh-keygen is the following:

enrico@solaris:~$ ssh-keygen -t rsa

Generating public/private rsa key pair.
Enter file in which to save the key (/home/enrico/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/enrico/prova.
Your public key has been saved in /home/enrico/prova.pub.
The key fingerprint is:
23:63:25:1d:2a:0a:34:c8:47:d9:65:80:43:f6:c9:e8 enrico@solaris

Obviously, a good advice would be using a passphrase: please note that in this case SSH will be asking for user input and instead of your password you'll be typing your passphrase. In my case, I decided to use an empty passphrase and keep keys' files safe.

Once you have your keys generated, you have to copy the public key on every server you want to log on to. The content of id_rsa.pub is a line which must be appended to the .ssh/authorized_keys2 file. If this file does not exist, just create it copying id_rsa.pub in .ssh/authorized_keys2. Even if you use a passphrase, care should be taken to protect files in the .ssh directory. At most, this directory and its content should have 0600 permission level.

Now you have setup your environment and the sshd daemon on the server you log in will encrypt communications (2.0 protocol version) using the public key you provided and next time you'll log in via SSH to that server, you won't be asked your password any longer!

Wednesday, August 20, 2008

Setting up Subversion on Solaris 10

In this series of posts I'm going to describe how I set up Subversion on a Solaris 10 machine. The instructions here are valid for subsequent releases such as Solaris Express Community Edition (Nevada) and OpenSolaris (Indiana), the only difference being the fact that Subversion is bundled with the Operating System.

I decided to host some Subversion (1.4.5) repositories on a Solaris 10 (update 5) server so I downloaded Subversion packages from Blastwave and installation was done in less than 5 minutes with a simple:
# pkg-get -i subversion
Once Blastwave's installer was done, the first thing I wanted to do was registering Subversion's daemon (svnserve) in the Service Management Facility. Writing an SMF manifest is not so hard but fortunately I found a manifest and a management script in OpenSolaris website and the job was done! Great work, guys.

Next steps

You can now: