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.
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:
slapt-get –update
slapt-get –dist-upgrade
SOURCE=http://mirror.switch.ch/ftp/mirror/gsb/gsb-current/
slapt-get –update
slapt-get –add-keys
slapt-get –install –reinstall alsa-lib bluez glib2 gtk+2 libwnck
slapt-get –install NetworkManager network-manager-applet
chmod +x /etc/rc.d/rc.messagebus /etc/rc.d/rc.hald /etc/rc.d/rc.networkmanager
netdev:x:86:root
Add your username after root (bodom_lx is my case)
netdev:x:86:root,bodom_lx
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::
removepkg /var/log/packages/*gsb
#SOURCE=http://mirror.switch.ch/ftp/mirror/gsb/gsb-current/
slapt-get –update
slapt-get –reinstall –install glib2 libwnck alsa-lib gtk+2
chmod -x ~/.kde/Autostart/nm-applet.sh
Feel free to comment any suggestion.
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 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. 1
I really like (and miss) Linux Mint Menu (mintmenu), so I installed it on my Debian Sid box and here is how I managed it:
ln -s gnome-applications.menu applications.menu
ln -s gnome-preferences.menu preferences.menu
ln -s gnome-settings.menu settings.menu
et voilà! Here are the two deb files I’m using:
mintsystem_61_all
mintmenu_4.2_all
MintMenu complete under Debian Sid
If you also want to enable beagle or tracker, be sure to add the correct search command in the preferences of mintMenu (see the screenshot)
It’s a very long time since I abandoned Ubuntu, 1 year and 9 months being precise, although I continued to use Ubuntu derived distros.
I decided today to give Ubuntu 8.10 beta a try. Obviously, every time I decide to try a Gnu/Linux distribution it happens that a new release comes out: I downloaded Alpha 6 yesterday, I fell into problems with it and a apt-get update && apt-get dist-upgrade brought me Ubuntu 8.10 beta, correcting some of them 
Read more…
Il mio amore/odio verso Archlinux non é un gran segreto, come non lo é neanche il mio pessimo vizio di formattare il portatile ogni 5 secondi per provare nuove distribuzioni Gnu/Linux. Le ho provate quasi tutte, ma quelle che a lungo si sono soffermate nel mio disco rigido sono, in ordine cronologico:
Dal 3 giugno fino a ieri ho tenuto Gentoo, con la quale mi trovo benissimo eccetto per alcuni piccoli particolari. Ma ieri ho voluto dare un’altra possiblitá alla mia distribuzione preferita, installandola via ftp partendo da un sistema minimale.
Mi sono giá lamentato in passato per le sue lacune (vedere il post Perché Archlinux non decolla) e devo dire che queste 24 ore di prova sono molto soddisfacenti.
Al momento il sistema é piuttosto stabile pur mantenendo la caratteristica di punta di Archie, ovvero le prestazioni.
Il kernel 2.6.23, gcc 4.2.2, glibc 2.7.6 sono molto recenti e non hanno dato problemi. Anche Gnome 2.20.1 é parecchio bello e non é mai crashato.
Due piccoli appunti: se installando Gnome notate dei fonts parecchio brutti, installate il pacchetto ttf-dejavu, dal repository “extra”:
pacman -S ttf-dejavu
Purtroppo tracker, presente nella sua ultima release stabile, non funziona a dovere, crasha dopo essere partito. Questo succede anche con la versione svn installabile via AUR. Vedremo cosa succederá nei prossimi giorni (i pacchetti di Archlinux sono soggetti a parecchie modifiche, essendo generati poco dopo le release dei programmi).
I repositories che uso sono core, release, extra, community.
C’é da dire che tre giorni fa é stato annunciato un re-build di tutti i pacchetti “core” di Archlinux con i nuovi pacchetti che fanno parte della Toolchain. I pacchetti verranno messi mano a mano nel repository “testing”, e spostati nel core una volta dichiarati “stabili” (non sono molto d’accordo con la celeritá degli sviluppatori di Archlinux nel dichiarare un pacchetto stabile, speriamo in bene).
Non fate stronzate, cari Archie developers
Faró sapere nei prossimi giorni cosa funziona e cosa non va.
Vedremo quanto durerá questa mia agognante storia d’amore con una delle potenzialmente migliori distribuzioni Gnu/Linux ^_^
Twitter
Recent Comments