Hooray! Two more one-line patches! That brings my total up to 12 or so one-liners.

From Horde:

Date: Mon, 25 Dec 2006 09:59:06 -0800 (PST)
From: “Chuck Hagenbuch”
Subject: [cvs] commit: hordeweb/bounties bounties.php
To: cvs@lists.horde.org
Message-ID: <20061225175906.3B6D4351DE@coyote.horde.org>

chuck 2006-12-25 09:59:06 PST

Modified files:
bounties bounties.php
Log:
fix bug number
Submitted by: Eric Garrido

Revision Changes Path
1.175 +1 -1 hordeweb/bounties/bounties.php

Chora Links:
http://cvs.horde.org/diff.php/hordeweb/bounties/bounties.php?r1=1.174&r2=1.175&ty=u

and from ViewVC:

http://viewvc.tigris.org/issues/show_bug.cgi?id=189

FIXED:
Sending INSTALL
Sending viewvc.org/index.html
Transmitting file data ..
Committed revision 1226.

Thanks, Eric.

I sent this a while ago to my suitemates in an attempt to motivate them to be cleaner. Some people found it funny. (It was intended to be half humorous).

Gentlemen,

The kitchen was filthy. Food particles were everywhere. RICE was
everywhere. Nastiness in the microwave. Dirty dishes in the sink.
Dirty dishes on the counters. A heaping pile of clean dishes in the
dish rack. There were things superbly adhered to surfaces. When
*things* are *superbly* adhered to *surfaces* shit hits the fan.
Luckily for us, we don’t have a fan.

You all should be ashamed of yourselves for not respecting the other
members of the suite, for not respecting guests that we might have
over. This is our temporary home and homes are not something to
disrespect. If your friends are the types that appreciate filth or
like to eat the days-to-weeks old pieces of rice on the floor, that’s
my problem. My friends would rather drink boxed wine before they’d do
that.

We cleaned this evening. Not that you noticed. I did counters,
microwave, floors, trash, first pass range, and some dishes. Casey
did dishes and trash. Varun cleaned the range with care.

Mr. Clean was nowhere to be found.

Six’s mom did these things weeks ago. I query you: how many times did
I or Six’s mom make a mess with the range? How many times did I or
Six’s mom make rice? How many times did I or Six’s mom explode a food
item in the microwave?

The answer, my dear sirs, is zero. Zero. What percentage of time did
our cooking behavior in a common area affect other members in a
suite? NaN. But, we still find ourselves on the other end of a mop.
Our hands are still stained with bleach. Our tears are made of PineSol.

And what am I going to ask you to do in the future? Nothing.
Absolutely nothing. You’ve demonstrated that you’re comfortable with
mess in shared spaces and you’ve demonstrated you don’t care. I have
no incentives to make you care.

And why should you really? Because the happiness of a person is
apparently based on hunting and southerners, not the cleanliness of
our homes. What a northern ideal. Hmph. Damned northerners.

There is no economic incentive for you to care. Maybe the rest of us
should start eating your cheese. Then you’d get the message. A man’s
cheese is nothing to tamper with, but neither is a man’s right to a
untainted, comfortable common room. But if we started to eat your
cheese, you would just stop buying it and continue to make a mess.

There are no environmental activists that are campaigning for a
cleaner kitchen. Steve Jobs is not getting on stage and preaching for
a mopped floor. There are no Linux User Group meetings about the
efficacy of clean common rooms in system administration.

There is just no reason for us to care.

Yes, it could have been worse. Yes, it could have been much worse.
Yes, other suites are worse. Those are defeatist arguments and I have
no regard for defeatists. I defeat defeatists before taking breakfast
every morning.

Ask yourselves: WWMMS? (What would my mother say?) Or perhaps more
importantly: WWSMS? (What would Six’s mother say?).

They wouldn’t say anything. They’d be clean, stay clean, and clean
anyway.

We need a Suite Mom. Unfortunately, the only girlfriends of h305ers
are not in the running for the position. More unfortunately for me, I
seem to be the de facto top candidate. I don’t want any MILF jokes,
you hear?

Enjoy the cleaner suite. More specifically, enjoy dirtying it up in
the coming weeks so I/we can clean up your mess again. And then, I’ll
send this exact email again. It’ll just become a routine.

Eric

I just received my two Seagate 7200.9 250GB drives and have already installed them into my Thecus N2050 RAID DAS device (both hd and das on NewEgg). I was initially worried because the 7200.9 drives are not listed on the Thecus approved drive list, despite the 7200.7 and 7200.10 devices being there. They work fine. The 7200.9 250GB drives were $10 cheaper than the 7200.10 drives. Since I don’t really need performance but do want space, the older model was fine for me.

I’m fairly impressed with the setup. The box was easy to install: I slapped the two drives in, installed the included SATA card (Silicon Image, Inc. SiI 3512) in my Linux box, compiled modules for siimage and sata_sil (I’m not yet sure if I need the former; there is no documentation for installation on Linux).

My future plans are to purchase another N2050 in which I’ll place the two 250G 7200.9 drives I already have in my Linux box (currently doing LVM to extend the partition space to 500GB, but no RAID). The only problem is that I’ve run out of PCI slots in my server, so I’d either have to use another server or buy a SATA PCI card with two eSATA connectors. Oh the problems of a geek.

I should also buy another 7200.9 250GB for the event that a drive fails. I’m not sure whether to buy this extra drive now as the 7200.10s are hitting the market or to wait a while. Or, I may not even do this and just rely on Seagate’s ridiculous 5 year warranty. On second thought, I’ll probably just do that.

Update 12/26/06: I’ve been using the sata_sil driver without any problems. Below are my (fairly decent) stats for the drive:


/dev/sdc:
Timing cached reads: 1728 MB in 2.00 seconds = 864.08 MB/sec
Timing buffered disk reads: 156 MB in 3.02 seconds = 51.58 MB/sec


More CEOs should be this candid. From an interview with hard drive manufacturer Seagate’s CEO Bill Watkins, entitled “Seagate CEO: I help people “watch porn”:

The secret to managing a board of directors: “You never ask board members what they think. You tell them what you’re going to do.”

“In Defense of Rosé Champagne” highlights why men should not be afraid of buying pink alcohol.

Somudro links to two extremely well written articles about the lost culture of pidgets, “A Review of Pidget Sexual Culture” and “Pidgets: A Historical Overview” (both PDFs). Well worth the read.

From somudro.info:

Anthropologists believe that in ancient Africa the most common form of currency was the “pidget.” Pidgets were in fact an enslaved race of short and stout people, resembling a cross between pygmies and malformed midgets… But how did such a cruel societal modus operandi arise? Was it effective as an economic system? And what was life like for a member of this noble yet ill-fated race? These questions will be examined in the series of articles that follow.

Duck Tape definitely was not requirement for high school history class. Oh Dan.

These are the articles in my RSS reader that I’ve flagged so that I think more about them:

• Virtualization Links
• A performance comparison of DB2 9 pureXML and CLOB or shredded XML storage
• More Trouble with Programming (Interview with Bjarne Stroustrup, Part II)
• Lego Programming (no, not the toy)
• Web OS (but currently down)

1. Optional prerequisite, proctools: If you’re going to use the init script to start imapproxy, you need to install proctools to let the script kill the process on shutdown. Installation is a little different than normal, but is explained nicely in the README.
2. Do the normal thing
   1. wget up-imapproxy-1.2.5rc2.tar.gz
   2. tar -xzf up-imapproxy-1.2.5rc2.tar.gz
   3. cd up-imapproxy-1.2.5rc2
   4. ./configure
   5. make
3. Install executable files: `make install` is broken as the user and group is hardcoded as bin. You can either edit the makefile or copy the necessary files manually, as below:
   1. sudo cp bin/in.imapproxyd /usr/local/sbin/
   2. sudo cp bin/pimpstat /usr/local/sbin/
4. Install configuration files: sudo make install-conf
5. Install init files: sudo mkdir /etc/init.d/ && sudo mkdir /etc/rc.2 && sudo make install-init
6. Install Certification Authority certificates: The included documentation is unclear what to do if you intend to use imapproxy to connect to an IMAP server with TLS/SSL. First, imapproxy cannot connect to IMAP servers using port 993. Instead, imapproxy will only connect to servers using regular IMAP and invoking TLS though the starttls IMAP command (RFC 2595). imapproxy does not currently support a client connecting to it through TLS; it is intended to be run on the same host as the client. Second, you must install the appropriate Certification Authority (CA) certificates that will validate the TLS certificate offered by the server. I grappled with this for a while, even using a working imapproxy installation as a reference to no avail. In the end, I packaged all of the root CA certs from OS X’s keychain into a .pem (which I’ve made available here). It is not necessary to create your own CA or certs as implied in the README.ssl included with the source.
7. Edit the configuration file: sudo nano imapproxy.conf . I changed the server_hostname string to the IMAP server I want to connect to, the listen_port to allow other IMAP server connection attempts to succeed, the listen_address to 127.0.0.1 to only allow clients on the localhost to connect, the force_tls to yes to force TLS (although the IMAP server I’m connecting to uses LOGINDISABLED). Finally, I changed tls_ca_file to the file path of the CA certs. My working imapproxy configuration file is available here.
8. Start the proxy: /etc/init.d/imapproxy start

That should be it for getting it to work. You should configure your IMAP client to connect to 127.0.0.1 on whatever port you specified above.

That’s not the whole story, however. Mac OS X does not use init scripts but uses a much cooler launching mechanism called launchd. Launchd takes care of launching, maintaining, and closing daemons, meaning it eliminates a lot of hassle for the daemon programmer.

I’ve created a launchd plist that can be used with launchd to start imapproxy the right way in Mac OS X. If you use this, you do not have to use #5 or #8 above. Also, you must set foreground_mode to yes. Copy the plist to /Library/LaunchDaemons and use sudo launchctl [load|unload] /Library/LaunchDaemons/imapproxy.plist to start and stop the proxy. The proxy will also start whenever the machine is started (to change this, move the plist out of that directory).

There is more Apple information on launchd plists, launchctl, and writing daemons that use launchd.