JDPFu.com 2025

Today I visited the skype.com website to get a newer version of Skype for my Nokia N800. The download page has been removed for that and the N810 devices. The N900 has a download, but I don’t want to risk it.

As long as Skype on the N800 continues to work, I’m not too worried. Just like many people, I’m unhappy with my telecom provider.

• They are too costly. They think they compete with AT&T on price, not Vonage or some other $9/month VoIP services
• Calls are dropped mid-sentence
• Connectivity disappears weekly

After a recent kernel update to 2.6.32-24-server, X11 refused to restart. Recall that I’d modified my system to support dual monitors as described in this prior post. Since a new kernel was installed, rebuilding any non-standard kernel modules is expected. That’s probably all we need to do. These instructions should work for anyone using nVidia graphics cards purchased in the last 4 (?) years and running a 2.6.xx kernel. Mine is a Ge-Force 7600-GS, so nothing too fancy.

The symptoms for this new issue were that the console refused to stay on the tty that I’d used – basically, every 10-20 seconds, the dmesg log was displayed on the console and my tty was changed to console regardless of how many times that I manually selected console 1, 2, 3, 4 …. It really sucked. The error displayed was something like “no screens available”, but I don’t have the exact error message anymore.

Anyway, time to follow my prior instructions for dual monitors, perhaps updating them.

We’re on Port 80 Now

Most of you probably don’t care, but this website underwent some big changes today. We are running on port 80 now. For the last 3 years, this blog has run on port 82, which caused some problems for some corporate access where the network admin was too lazy to proxy based on protocol and only proxied based on port. Those people couldn’t access the site.

Going forward, please use http://blog.jdpfu.com/ to access the site. Nothing under that should change, in theory.

We added port 80 as a way to allow access to the blog. We didn’t stop port 82 access so that old links from external locations will continue to work, but slowly, over time, access via port 82 should go away. Initially, port 82 will only have 1 server listening with port 80 getting 4 servers. For faster performance go to port 80.

What should you do?

1. You should update your RSS reader from jdpfu.com:82/articles.rss to http://blog.jdpfu.com/articles.rss
2. Anytime you see :82 in a URL, don’t worry, provided it works. If it doesn’t work, try removing the :82 part. That shouldn’t be necessary, but you never know. http://blog.jdpfu.com/ should be the subdomain that http://jdpfu.com/ redirects to from now on, at least from the top page request.

When you have lots of servers, things can get complicated.

If you see problems, please drop a comment to us.

We run lots of internal only web servers that also listen on port 80, so some of these services could be confused at the reverse proxy server and redirect to the wrong place. Hopefully, it doesn’t become a big issue for the public users. You guys should have priority.

In a few months, we may setup an apache server for port 82 that handles the rewrites automatically and provides a permanently moved error as part of the redirect. Perhaps next week. Perhaps.

In May 2010, I decided to lose a little weight for an Aug 1 occasion. Ok, perhaps not really a little. Anyway, I’ve made some progress since then.

Monthly   Total Lost
05/20/10  0
06/20/10  7.5
07/20/10  11
08/20/10  27
09/20/10  32.5

In a recent study, it turns out that about 1/3rd of all companies with 1,000+ users experience data loss or data leaks The study says this number is probably low, since it is self reported. The data loss can be from stolen laptops or misplaced flash drives or non-working backups. We all know that we should protect the data better, but for some reason it is determined to be too much hassle.

Then your company looses or inadvertently releases some sensitive data. That data was worth a few million or more.

Now you’re working a plan to encrypt all portable devices and trying to ensure no data get release without appropriate approvals first. Yes, it is too late, but this is a prophylactic for the next time.

Every laptop should probably be full drive encrypted. You know that already, now you just need to do it. Here’s how I did it – a compromise solution.

For the last few weeks, caller ID has been showing “800 Service” calls twice a day. Today, I finally decided to deal with it and answered. It was Dell trying to sell an extended warranty on a laptop that I recently purchased. The warranty price was about 30% the cost of the laptop! Do people actually buy these ripoffs? After she read the “in-home” warranty information that I already have, I asked if she had anything that wasn’t in the contract to tell me. Whatever….

So, the best part of this was the fake Minnesotan accent. She slipped a few times into her native Indian accent, but most of the time I was waiting for a “don’t cha know” at the end of every statement. I guess Dell figured that a regional accent was a better sales tool. Basically, I don’t buy anything from someone who cold calls me. I don’t want to encourage that behavior, don’t cha know.

I watch Hak5 on my S2 TiVo. This season, DK is doing everything on Linux. He’s covered a fairly powerful home router already with smoothwall. The home-made commercials are usually the best parts of the show m(seriously!), but episode 804 covers the easy and slightly harder way to record your Linux desktop for screen casts.

gtk record my desktop for you GUI-liking people and ffmpeg for the shell folks like me that prefer a little more control are demonstrated.

The guys over a CommandLineFu also covered the ffmpeg way of doing it with a little more finesse. Don’t you just love that domain name?!!!

ffmpeg -f alsa -itsoffset 00:00:02.000 -ac 2 -i hw:0,0 -f x11grab -s $(xwininfo -root | grep 'geometry' | awk '{print $2;}') -r 10 -i :0.0 -sameq -f mp4 -s wvga -y intro.mp4

Hak5 isn’t the first to cover this topic. A quick search finds thousands of others demonstrating how to do this as well, but a few of the Hak5 commercials are GREAT!

For the last few years, I’ve heard powershell for scripting by IT professionals in the MS-Windows community. Never looked at it until a few days ago. See, I confused cscript with PowerShell scripting. I couldn’t get the hang of cscript and wasn’t able to get it to accomplish what I needed the last time I tried. In June, I actually wrote some .BAT scripts for a client. If I knew then what I know now about PowerShell, I’d have been much happier and written those scripts in PowerShell, assuming it is pre-installed on Win2003 Server.

In my limited time with PowerShell, here are my impressions.

• UNIX has text processing, MS-Windows uses object processing – sorta like the difference between PERL and Ruby scripting.
• Most of the syntax is Perl-like – with some differences. Get used to $var.action calls.
• Pipes work like you’d expect from UNIX, except ….
  • generally, we don’t use `grep`, rather, the regex is used as part of the prior command
  • | `wc -l` becomes action.count – basically, if you want to get a count of something.
  • functions are Perl/Bash-like, except the argument passing is C-like (int x, int y). That is better than Perl, IMHO.
• Objects mean access to the registry, COM, and WMI. That’s a plus AND a minus. How to query a GUI program? That’s the problem.
• As usual, rather than reuse existing commands, Microsoft decided to use, longer, more complex commands. `ls` is `get-selections`, but they did include aliases in the tool. That means that many of the normal UNIX commands used in shell scripts have aliases, but those are not the preferred method name to be used.

As long as you don’t need to press a button inside a GUI, PowerShell can probably be useful.

Mindset Change

To me, the main limitations of PowerShell really aren’t with the language, rather, it is with my mindset and having to change from UNIX/File processing to object processing. Also, the tools on UNIX/Linux systems tend to support command line options to get things done. In MS-Windows, command line options to GUI programs are usually extremely limited – next to worthless. In Linux/UNIX, there are hundreds and hundreds of small applications and tools that come with the system suitable for script use.

References

A few years ago, PowerShell was called msh, Microsoft Command Shell. Here’s an overview.

Here’s a PowerShell Tutorial if you are interested in going further.

Read where someone is porting PowerShell to UNIX/Linux systems. Yep, it is called Pash. According to the project page, it is 40-50% complete and running on Windows, Linux, Mac and Windows Mobile platforms.

VMware is using PowerShell (they call it PowerCLI) as an interface into their ESX virtualization system.

Summary

In summary, it seems that Microsoft has been working hard for years to remove some of the biggest complaints against their systems – the lack of real, usable scripting. Seems they could advertise it a little more widely. Personally, I’d prefer a Perl library that encapsulated all this and for Perl to be included with MS-Windows installations so I don’t need to learn yet another language. Still, msh/psh/pash or whatever they call it this year is a step in the right direction.

Get the free ebook/PDF from Microsoft’s site about being secure online Microsoft is sponsoring the ebook, it is not written by them.

The first download in the list appears to be the complete ebook, so there’s no need to grab each chapter. It is in PDF, so be certain you have a non-Adobe PDF reader program. We don’t like Adobe stuff here due to security concerns.

Updated 12/2014:
Jump to the bottom of the article to see the updates.

People new to Linux or UNIX often don’t understand that built into the GUI system is a way to remote into pretty much any server in the world and have a program running on the remote machine, but displayed back on your Linux desktop. It is built in and has been for 30+ year of X/Windows. It doesn’t matter if you use Ubuntu, Redhat, Solaris, AIX, or if you use Gnome, KDE, XFCE, MWM, TWM – this solution is at a lower level. If you have a GUI on Linux or UNIX, it is built in and actually works really, really well.

Remote Applications over the WAN