Vixta and Zombu

Read a few articles today and taught that these 2 things were interesting: Vixta and Zonbu. I wish Vixta had some Tablet PC features because I would be reformating my tablet PC in no time. Vista is just a pain. It amazes me that you can go backward with an upgrade. Zonbu is a nice PC but I am not looking for hosted storage. I want a small quiet PC with Linux.

More mobility dreams not happening

I went to Bell last week to check what services they had from someone that wanted to work on the road (or just outside the house). They have the “unplugged Internet” but the sales person was not too thrilled about it and was not looking forward to clients wanting it. Bad experience with a return?! I did not ask. I also looked at the usb/PCCard/Xpress Card service but to get unlimited service you pay 75$/month. It seems a bit high for a 512 kbps connections. I am sure that it is fine for some customers but signing a 3 years deal on that service to get the card at $50 did not appeal enough for me to try it. I guess that it will not be easy to find a solution in this area that makes sense for my budget.

Cisco VPN Client and Linux Kernel 2.6.21

I had some problems installing the Cisco VPN client 4.8 on my Slackware 12.0 workstation so I searched a bit on the net and fond a page that had almost everything to the t: A few very small differences that are due to the fact that the kernel has changed a bit more since this doc. So here are the very quick steps:

  1. cd /usr/src/linux/
  2. make menuconfig – and check that everything is good
  3. make bzImage
  4. cd include/linux
  5. ln -s autoconf.h config.h
  6. cd /whereever/vpnclient/
  7. perl -p -i -e ‘s/CHECKSUM_HW/CHECKSUM_COMPLETE/g’ interceptor.c – to replace references of CHECKSUM_HW with CHECKSUM_COMPLETE; there are only 2 to fix
  8. perl -p -i -e ‘s/skb_checksum_help(.*)/skb_checksum_help(skb)/g’ interceptor.c – to replace the 5 references to skb_checksum_help() with the proper parameters
  9. ./vpn_install – to install the Cisco VPN client

If you have a different experience don’t hesitate to let me know how it works for you.

Mobility shut down

I tried the Rogers Portable Internet and it did not work from anywhere I went. It is very simple to setup and the modem has these lights at the top that tells you the strength of the signal. Even when the 5 lights were on I could not keep the signal from more than a few seconds. I tried it for 2 days and then gave up since I was not able to transfer any traffic.

Mobility Worker Nirvana

The title of this post could probably read as “the pursuit of working anywhere on a budget”. Since I work from home I figured that it means that I can work from anywhere. I have been looking at some possibilities for the last few weeks on where and how I could work from elsewhere than my home office.Connectivity is quite important since I do all my work remotely. I need to be able to connect to servers in different locations to do my work. Rarely can I work in an isolated mode. Here they are only a few options if I want to get wireless access from anywhere. Rogers has a modem for only $99CAD plus the data plan. Maybe that could be the solution. The only thing it needs is a power outlet. We will test and see.

Requirement Based Testing

This morning, I went to a Borland Seminar about Requirement Based Testing (RBT). I don’t think that we can justify the spending for the tools that Borland propose to achieve this concept but none the less the information was very valuable to me. Sometimes the simplest concept are the most effective.The first thing they said that got my attention is that a requirement that you can’t test is not a valid requirement. You simply need to reword it to be measurable. So the requirement of an application to be fast is not valid but saying that step x can only take y seconds is valid.

The other thing that they repeated over and over was traceability. You need to be able to see the link between your requirements, the test and the results. That is where their tools helps you greatly. Doing all this in a spreadsheet is the poor man solution to it.

I also liked hearing that you need to have the least amount of test case for your requirements. Simplify! If you have more than 5% of your test case on a specific requirement you should look at it again.

Something else that I will mention that I liked was the fact that your tester, developers should be made aware of all the requirements early on and when you make changes to them you have to communicate them effectively. The goal to get everyone on board early on is to avoid the separation of the teams and the “ennemy mentality” that “sometime” happens.

The last funny tidbit for me was the mention that 60% to 70% of work in IT is actually rework. Work that will not get used or you are simply redoing what you (or someone else) has done. So easy to believe without any need for proofs.

Blade Boot

BladeBoot seems to be all that I am doing this month. It is an IBM technology to use the builtin NICs in a blade to iSCSI boot from SAN. A little bit of firmware update, a java app to configure the NVRam of the NIC (you can also do it with DHCP) and you need a SAN with iSCSI. IBM has good documentation on how to do it with Windows and with Suse Linux. The only glitch we had to fight with was that the MS iSCSI software initiator that support boot to SAN was not available at the link advertise. I found it by “mistake” at the EmBoot site. I downloaded the WinBoot/i software and it is part of it. On the Suse installation we are waiting for the SLES 10.0 sp1 to address the need for a DHCP server. As with many technology it looks much better on paper than in reality but we have a good start now.