bodom_lx at task3 dot cc

About a year after the creation of bd-theme-zen Wordpress theme, I decided to switch to a new theme. The new theme is monochrome

The reasons behind are simple: unfortunately, 2009 has totally been not a Zen year for me. Many things have not gone as I thought they should have been. Many other important things have been melted. Lot of things have changed.

I hope 2010 will be the year of the Phoenix, in which everything aggressively changes again and turns better. For everyone, for sure.

Therefore, I decided to switch to a new theme, monochrome by mono-lab.net. This theme is very modern, yet minimalistic and elegant. And surely, more nice-looking than those themes written by me.
I’m still happy with bd-theme-zen, I liked its initial orange version and I appreciated the glacial blue one I decided to switch to around August (the color switch was also significant for me).

But this is not time for being Zen. It is time to be reactive.

I wish everybody a fucking explosive 2010.

For those of you asking if I was spending my time to write this post on 2009-12-31 at 00.00: I wrote this post on 2009-12-26 and scheduled the publish to the beginning of the new Year.

Related posts

• 2009 is a Zen year! Announcing BD-theme Zen (0)
• Introduction To Software Testing (0)
• BD-theme-zen (0)
• BD-theme (0)
• Projects (0)

At the end we decided to adopt OpenTrip. I could propose the Dynamic extension of the protocol, over XML-RPC.
By the way, I opened a GitHub repository to host the source code of Dycapo. At this moment I just implemented and documented the models.
Dycapo project source code is hosted on: http://github.com/BodomLx/dycapo.

Related posts

• Introduction To Software Testing (0)
• Announcing Dycapo 0.0.2 (1)
• Announcing Dycapo 0.0.1 (0)
• Finally, the site has entered top 20000 Netcraft Most Visited Web Sites (0)
• Projects (0)

I love to be back to Slackware, my very first distribution. However, there are a couple of things that I’m missing from the other more comfortable distributions. From among them, I totally miss Network Manager.
I saw many people asking in forums on how to install Network Manager in Slackware 13.0. There is Wicd, already present in Slackware “repositories”. Every Slackware maniac will tell you that it does the same job of Network Manager, but I don’t agree. It does not always work and is more complicated to be configured than NM.

Anyway, I’m going to explain to Slackware newbies the dirty way to have a fully working Network Manager on Slackware 13.0. This method is totally against Slackware philosophy and will also replace some important libraries of the system! Anyway, the packages being replaced are prepared from the guys behind GNOME SlackBuild, a project to bring Gnome in every Slackware release.
You have two way to have Network Manager in your Slackware: either install the entire Gnome from them (or any other similar project) or use slapt-get against their repositories and just install Network-Manager. Here are the instructions. All the following actions must be performed as root user:

1. Download, install and configure slapt-get. Instructions are provided on their website.
2. Update your system with:
   

   slapt-get –update
   slapt-get –dist-upgrade

3. Add GNOME SlackBuild repository in /etc/slapt-get/slapt-getrc:

   SOURCE=http://mirror.switch.ch/ftp/mirror/gsb/gsb-current/

4. Update the list of available packages and replace some system packages:

   slapt-get –update
   slapt-get –add-keys
   slapt-get –install –reinstall alsa-lib bluez glib2 gtk+2 libwnck

5. Now install Network Manager and its GTK applet:

   slapt-get –install NetworkManager network-manager-applet

6. Be sure that dbus, hal and NetworkManager daemons will be loaded at boot time:

   chmod +x /etc/rc.d/rc.messagebus /etc/rc.d/rc.hald /etc/rc.d/rc.networkmanager

7. Add your user to the plugdev group. Edit /etc/group, find the line

   netdev:x:86:root

   Add your username after root (bodom_lx is my case)

   netdev:x:86:root,bodom_lx

8. You are quite finished now! Log back as normal user and create a startup script for network-manager-applet:

   cd ~/.kde/Autostart/

   Create a file called nm-applet.sh with the following content:

   #!/usr/bin/bash
   nm-applet –sm-disable &

   Give it execution permission:

   chmod +x nm-applet.sh

   .

Reboot your system. Everything should work fine now.

To uninstall Network Manager and restore the system as it was before the installation follow these instructions, as root::

1. remove any GNOME SlackBuild package using:
   

   removepkg /var/log/packages/*gsb

2. Comment GNOME SlackBuild entry in /etc/slapt-get/slapt-getrc:

   #SOURCE=http://mirror.switch.ch/ftp/mirror/gsb/gsb-current/

3. Update your slapt-get sources and re-install the replaced Slackware packages:

   slapt-get –update
   slapt-get –reinstall –install glib2 libwnck alsa-lib gtk+2

4. Toggle execution permission to the auto-started network-manager-applet. Log back as normal user and type:

   chmod -x ~/.kde/Autostart/nm-applet.sh

Feel free to comment any suggestion.

Related posts

• Testing Ubuntu 8.10 (Intrepid Ibex) beta on a Macbook (updated!) (6)
• Fedora 10, thank you very much! (macbook review and fixes) (3)
• gOS 3 Gadgets (Beta) Review (11)
• Pomotux (0)
• Introduction To Software Testing (0)

While I am waiting for my wiki to be setup, I’m updating here my first week of work. I read lots of papers regarding dynamic car pooling and friends. Most of them are listed on this MIT website and on dynamicridesharing.org. The second site is maintained by Dan Kirshner, the author of three (unlucky) experiments regarding dynamic car pooling.
I actually selected 13 publications for my scope. I’m going to publish the list as soon as I’ve got my wiki. What I’m going to do is to review them, comparing my work with the excellent one done by Hannes Zimmerman and Yann Stempfel (Current Trends in Dynamic Ridesharing, identification of Bottleneck Problems and Propositions of Solutions).

Related posts

• Internship: Dynamic Carpooling (0)
• Introduction To Software Testing (0)
• Wiki set up, first meeting (0)
• Some systems analyzed, thinking about protocols (0)
• Object Oriented Memory Management (0)

If you are running Debian Sid (i386) and are trying to install Gnome using

apt-get install gnome

You will probably might be disappointed because of problems regarding gnome-desktop-environment, ekiga, ptlib (libpt2.6.4) and opal (libopal3.6.4). Everything seems related to a missing 386 version of libpt2.6.4 on Debian Sid. Also libpt2.6.4-plugins is missing. Packages are also reported to be broken.

Well, I was tired to wait for the right solution of Debian’s Gnome maintainers (respect to all of them!) and have just built my version of ptlib with built-in plugins. If you download it, install it and try again to install gnome, everything works fine.
Obviously, there are reasons behind the absence of a i386 version of libpt2.6.4 and libpt2.6.4-plugins from Debian Sid repositories. My workaround is surely not the right way to fix the problem, as I don’t know the reasons of the blocks on those packages. It may be either serious technical reasons or “simpler” political reasons. You might prefer to wait for the heroes to fix the problem in the Debian way. You are advised, anyway.

If you feel brave and just want to see your Gnome Desktop Environment appear on your Sid box then follow these steps:
1) Download my libt2.6.4 Debian Sid package. It provides libpt.2.6.4 and libpt2.6.4-plugins required by Ekiga, which is required by gnome-desktop-environment
2) Install it:

dpkg -i libpt2.6.4_2.6.4-1_i386.deb

3) Try again to install gnome:

apt-get install gnome

Stop here if everything is fine!

If it doesn’t work:
4) Try first to install libopal3.6.4:

apt-get install libopal3.6.4

If it works, go back to step 3.

If it doesn’t:
a) Try first to install Ekiga:

apt-get install ekiga

If there are still problems with libopal:
b) Download my libopal3.6.4 Debian Sid package. It provides libopal3.6.4, which is also required by Ekiga.
c) Install it:

dkpg -i libopal3.6.4_3.6.4-1_i386.deb

Go back to step 3.

Good luck!

Related posts

• Testing Ubuntu 8.10 (Intrepid Ibex) beta on a Macbook (updated!) (6)
• Fedora 10, thank you very much! (macbook review and fixes) (3)
• Introduction To Software Testing (0)
• How to install MintMenu on Debian (lenny, sid) (2)
• Curriculum (0)

Elements and Concepts – A brief overview

---

Download PDF version of the whole document. You can browse the article online but I encourage the download of the PDF since it is written with accuracy.

---

Introduction

This document contains some basic concepts and definitions about software testing. It has been written for studying a part of the Software Engineering Project course at my University. It is composed by a summary of the intersection of more than 10 different sources, all of which are cited. If you feel that some contents of this publication belong to your intellectual property and it is not cited, please contact the author who is willing to correct any mistake.

The first part of the paper focuses on the definition of the most important key aspects of software testing. Then some information about input partitioning are given. What follows is a research about code coverage and two useful and famous tools, Control-flow coverage and Data-flow analysis. A complete example on using those tools is then given. The second half of the document also contains the definition of the most important software testing practices.

The goal of this tiny document is to clarify key terms and therefore become a base start for the reader to go in deep with the interested topics. Another goal is to give a simple but clear example about data flow analysis, as I realized that not all the people understand the examples around the Net.

Software Testing

Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate. Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It can also be stated as the process of validating and verifying that a software program/application/product meets the business and technical requirements that guided its design and development, so that it works as expected and can be implemented with the same characteristics. ¹

Read more…

Related posts

• Publications (0)
• Some definitions for Introduction to Programming (Java) (3)
• Object Oriented Memory Management (0)
• BD-shell (0)
• BD-review (0)