Chit chat


Did an  update on the old 10.x ltsp server. That maybe the last one. Want a new machine and then load the latest and greatest The old amd800 has had better days.

The other dtv converter looks like it is about to bite the dust. Looking at options.

Still getting a lot of requests for people curious about OTA TV antennnas



Was trying to get a list of systems up on the network. would not work at all. It was driving me nuts. So I went to another system and it worked.

$ cat
for i in {1..254}
ping 192.168.1.$i -c1 -w1 -v  | grep “icmp_seq=1″

$ ./
64 bytes from icmp_seq=1 ttl=64 time=0.623 ms
64 bytes from icmp_seq=1 ttl=64 time=0.113 ms
64 bytes from icmp_seq=1 ttl=255 time=4.77 ms
64 bytes from icmp_seq=1 ttl=64 time=1.26 ms
64 bytes from icmp_seq=1 ttl=64 time=0.306 ms

Went back to the original system and decided to do just one ping.

$ ping -c 1
PING ( 56(84) bytes of data.
64 bytes from icmp_req=1 ttl=64 time=0.363 ms

— ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.363/0.363/0.363/0.000 ms

After looking at it about a thousand times, it finally hit me. The difference was reg vs seq. So I changed the batch file and all was well,

$ cat
for i in {1..254}
ping 192.168.1.$i -c1 -w1 -v  | grep “icmp_req=1”

$ ./
64 bytes from icmp_req=1 ttl=64 time=0.527 ms
64 bytes from icmp_req=1 ttl=64 time=0.293 ms
64 bytes from icmp_req=1 ttl=255 time=5.08 ms
64 bytes from icmp_req=1 ttl=64 time=0.264 ms
64 bytes from icmp_req=1 ttl=64 time=0.068 ms

Whew….  details details details…….


Money for school test equipment down the drain.  Since  #Android does not want to support #ethernet , I no longer want to use android. Saying you do not support ethernet is amateurish. Not getting a new unit to get left out in the cold again. Android is getting the Apple/Microsoft  disease. Update: waiting to see if a5.1 fixes the issues.

Whoopie!! Ethernet is fixed, but still have to test a direct connection to the Arduino, Could not find a setting to set the ip address, so it looks like I will have to use a router to make it work.


Sous vide idea in progress

Remark: Logic for a sous vide system

Set lo
Set high_temperature
Set start_time
Set end_time
Turn on heat
Turn on led
if end_time < start_time then stop.

loop until time > end_time.
Get temperature
if temperature > high_temperature then turn off heat and turn off led
if temperature < low_temperature then turn on heat and turn on led
get time

turn led off


Really feel for Mr. Banzi and the fact that everyone is making their own version of the Arduino. You can get the bare  chips and make your own. You can get the boards as low as ten dollars even at a retail outlet. Had a spare ethernet board I bought from Radio shack on sale. So when I saw a compatible board for only ten dollars, I had to get it.

The main reason, I wanted this version of the board is that I have some Arduino chips that that can be plugged and played on the board versus the surface mounted versions which not not plug and play.

Speaking the Arduino, they have a newer IDE. When I downloaded it the

Published on

4/3/15, 5:46 AM

Central Daylight Time


other day, it had problems. The one I downloaded

today seems to work. Tested the new Arduino board and the extra ethernet board we had. Seemed to work. The page for the new software is:

One thing I like about the new ide is that if gives you a basic form to start with, which saves time. In fact you cut and paste the minimal code in the olde ide software;

Time to go back and work on the Sous vide project.


Old computer power supplies can still deliver +5, +12,  ground and more. Great for conversion to workbench supplies.

Pin Name
1 +5V
2 +5V
3 +5V
4 +5V
5 GND1
6 GND2
7 GND3
8 GND4
9 +12V
10 KEY
11 -12V
12 +5V USER
13 -5V


Ethernet splitter.variant cable saver.


Take the other end of the cable, cut it to 9 inches and punch down the four pairs using the following wiring scheme: You will need two of them.

Jack #1:

1 White/Orange to pin 1keystone jack
2 Orange to pin 2 keystone jack
3 White/Green to pin 3 keystone jack
6 Green to pin 6 keystone jack

Jack #2:

4 Blue to pin 2 keystone jack
5 White/Blue to pin 1 keystone jack
7 White/Brown to pin 3 keystone jack
8 Brown to pin 6 keystone jack

Once all the pairs are punched down, you can glue together side by side the two keystone jacks.


Screenshot from 2015-03-30 00:22:51


What was the diagnosis from the famous MSWindows PC Tech doctor say about the linux box?

“It’s terminal.”


Picture of Part III LTSP Maintenance.

This is for LTSP,  mainly for keeping software installed via the standard repositories up to date.  You definitely really need to be at least an intermediate linux user to accomplish this project. Ask for help for an expert if you fell uncomfortable with it. With ltsp you really have two separate file systems to update. One for the regular file system and one for the file system clients. Actually you could have several file systems to update if you are supporting more than one kind of thin client hardware. By now you should be handy enough with the command line that I do not have to put a picture of every result. Quick hint: you can ssh into your sever and then cut and paste all the commands from a file or ths web page. That is what I am doing now.

Update the sources (where the upgrade/update files will come from).
$ sudo apt-get update

Do the upgrade
$ sudo apt-get upgrade

In some cases if you did a system upgrade instead of a clean install, you might not get all packages upgraded.
$ sudo apt-get dist-upgrade will usually do the job.

Last of all some clean up.
$ sudo apt-get autoclean

With the client directories, you want to make sure that the list of sources for the client file system is the same as the server or there will be some incompatibilities. (note: i386 is the architecture type.)
$ sudo cp /etc/apt/sources.list /opt/ltsp/i386/etc/apt/.

$ export LTSP_FILE_DAEMONS=false

Now you need to temporarily need to change file systems so that the updates go to the proper file system.
$ sudo chroot /opt/ltsp/i386

$ mount -t proc proc /proc

Here we go:
$ sudo apt-get update

$ sudo apt-get dist-upgrade

$ sudo apt-get clean

$ exit

$ sudo ltsp-update-kernels

$ sudo umount /opt/ltsp/i386/proc

$ sudo ltsp-update-sshkeys

$ sudo ltsp-update-image

One of the few times that rebooting the might be a good idea.

$ sudo chroot /

$ sudo reboot

So nice only to have to update just one computer instead of a whole lab full or more of computers. You would still work with user accounts and etc as you would with a standalone system.


Tex-mex nachos (Some recipes may be available at


Good day.