All the content of other websites but none of the music!
I recently set up a IPv6 tunnel with Hurricane Electric’s free tunnel broker. Once your tunnel is created, HE provides instructions for setting the tunnel up on your system. Easy peasy. I decided that I wanted to setup a tunnel on my laptop. That’s a little tougher since my laptop will be getting a dynamic IP from the various wireless networks I connect to. Even more fun, since most wifi networks I connect to in hotels and airports, etc.
One of my problems at work is that I always want my mail and chat windows visible while I’m working. Sure, I could set up multiple windows and hope they stay where I put them. But it’s a pain to set those windows up every time. Since I’m using mutt for email and irssi for chat and instant messaging with bitlbee, I thought, why not use screen to organize the windows and, as a special bonus, I can pull up my session from anywhere over ssh.
There are a number of ways of using RT from within emacs. A quick google search will find them. Here’s what I use. RT First, you’ll need to snag a copy of the rt perl script from /opt/rt3/bin/ or from the source package. This can go almost anywhere on your local system but I put it in $HOME/bin/. Make sure you make it executable. Next, create $HOME/.rtrc. This will contain the information rt needs to access your RT install.
I spent a couple of days a while back trying to figure out why I was seeing bizarre bridge and network errors in my KVM host’s syslog and a VM that only two of three NICs worked at a time. Turns out that there is a very simple fix for both problems. First, let’s start with the KVM host network configuration. Here’s the basic config for a host with two NICs.
One of my criteria for choosing a virtualization platform is that it had to run Windows and Linux guests. Linux, of course, works out of the box on most VM hosts. Windows is a whole other story. The good news is that Windows Server 2003 and Server 2008 work just fine on KVM. There are, however, a few weird things that I’ve noticed so I thought I’d share some of them with you today.
I thought I would take a few minutes and share some of my experiences with Linux KVM. In this first post, I’d like to share some things about live migration. First, live migration works great … if you have the right version of KVM. Kvm-69, which is included with Ubuntu Hardy, is broken. Starting with kvm-70, live migration works again and works very well. You hardly even notice at all if you’re logged into the machine remotely while it migrates.
We’re in the process of trying to virtualize our data center at work. I was given the task of testing and evaluating the various VM technologies. I have to say that I am not impressed. VMWare ESX Let’s start with the big player in the VM world, VMWare ESX. The Banner team uses ESX for a few of their servers. ESX stood head and shoulders over everything else that I looked at.
Ok, I have to get this off my chest because, 1) it drives me fracking bonkers everytime and see it and 2) I want a place I can point people at when they ask why this is a bad idea. What I’m talking about is the excessive number of HOWTOs that think it’s a good idea to use the same home directory for all virtual users. Most of these HOWTOs discuss using postfix with courier, but I have seen courier-mta HOWTOs that do this too.
Needed FreeBSD Ports lang/perl5 SpamAssassin requires Perl 5.6 or higher. Note: Remeber to run use.perl ports before builing SpamAssassin. mail/p5-Mail-SpamAssassin databases/mysql40-server databases/p5-DBD-mysql Needed so SpamAssassin can talk to MySQL /usr/local/etc/mail/spamassassin/local.cf I like to store users’ settings in a MySQL database. See the SpamAssassin SQL README for instructions on setting that up. user_scores_dsn DBI:mysql:Accounts:localhost user_scores_sql_username sa user_scores_sql_password <password> user_scores_sql_table SA_userprefs MySQL Table CREATE TABLE SA_userprefs ( username varchar(128) default '' NOT NULL, preference varchar(30) default '' NOT NULL, value varchar(100) default '' NOT NULL, prefid int(11) UNSIGNED NOT NULL auto_increment, PRIMARY KEY (prefid), INDEX (username) ) COMMENT = "Accounts' SpamAssassin preferences.
I currently use SpamAssassin on the mail cluster at work and it works pretty well. Unfortunately, it doesn’t work well enough according to many of our customers and, more importantly, my boss. So, I worked out this way to use dspam and SpamAssassin. “Why use both?” you might ask. The answer is “I don’t, really.” What I do is provide dspam as an opt-in service and leave SpamAssassin as the default filter for those that don’t want to be bothered with the reporting that dspam requires.