So been playing around more with my EeePC 1000.  Still really like it, but I’ve got two major complaints now besides the security issues I’ve mentioned before.

  1. There is NO English spellchecking installed for StarOffice.  The install of StarOffice includes spellchecking for Polish but apparently not English.  I’ve checked all over and that’s it, no English spell checking and no easy way to add it yet.  This is a major problem for me, I’m a terrible speller.
  2. The right shift key is too far to the right.  I’m a touch typist and key placement is important.  I’m used to having the right shift key and instead I hit the up arrow while typing.  I’ll probably solve this by remapping the shift key and the arrow key, but it’s a bad design.  Luckily it’s something I can work around, just annoying.

I really do need to find a solution to the spell check, or bite the bullet and do the Fedora install.

Wrote another article about Grids.  This one is about migrating from WS-RF to WS-RT.  It covers some of the general issues and components of each standard you’ll have to focus on and provides links to more detailed information for implementing your solution.  I had some experience with WS-RF and this article helped me learn more about WS-RT myself.  Hope it help others as well!

Migrating from WSRF to WSRT 

The latest version of Pidgin (used to be gaim) was released. I haven’t found any nice rpm’s for Fedora Core 6 yet (that would install) so I went ahead and made my own. No warranty whatsoever on anything about them. They work on my FC6 box, and that’s about all I know.

The rpm files are here.

UPDATE: Ok as many are well aware of Fedora Core has now switched over to Pidgin and the pidgin group now has a YUM repo setup and working for Fedora. So my rpm’s aren’t needed, just go to pidgin.im and use their YUM repo.

Ok, I was trying to help a friend who is replacing WordPress with another system and needed to redirect the WordPress URLs for old posts to the new URL and the new posts. Doesn’t seem like that would be too much of a problem, except that the default WordPress uses html get values and not URLs to direct to a specific post. Given I’m not a mod_rewrite expert, it took a little digging and playing to figure out how to do it. Below is an example of how to do it using mod_rewrite and the .htaccess file in the root of the WordPress install:

Options +FollowSymLinks
RewriteEngine On
RewriteCond %{QUERY_STRING} ^p=1$
RewriteRule ^$ http://www.thenewdomain.com/the/new/url/story.html [R=301,L]

This assumes that your hosting provider allows mod_rewrite and that .htaccess overrides are allowed. The only problem with this is that the new url get the ?p=1 part tacked on to the end of the new url after redirect. In this case it didn’t cause a problem, but it doesn’t look perfect. I’m still trying to figure out how to dump this.

Looks like there is a bug in GPG that would allow someone to inject misc. data into a cyptographically signed or encrypted message without invalidating the signature of the message. Basically, it means that checking the signature status of a GPG email will not guarantee that the message is what the original sender sent.

Seems to effect all versions prior to 1.4.2.2, there are updates available.

More information here.

Copyright © 2015 · All Rights Reserved · Cafaro's Ramblings