The best April Fools joke I've seen here
My department has always done a lot of different things. Many years agowe were called 'Computing Services' ('University of Toronto ComputingServices' if you were being formal), and one of those things was a bunchof modems on a Sun 4. Of course, we had a greeting banner:
U of T Computing Services.
login:
(roughly what you saw if you dialed in.)
One April 1st, a co-worker changed this to ' U of T Confusing Services '.
The
A Firefox CSS irritation
I'm not going to fault Firefox for not supporting the CSS 2.1 ' word-wrap: pre-wrap ',no matter how convenient it would be for me if it did.Especially since CSS 2.1 is not yet a standard, merely a late stageworking draft. But I am annoyed that Firefox doesn't support the CSS2' display: compact ', since I could have used it just now.
' display: compact ' is classically used (in that it is right
The perfection trap: a lesson drawn from Worse is Better
I've mentioned Richard Gabriel's famous The Rise of "Worse is Better" before (back here ), but only recently did oneof its important lessons coalesce in my thoughts.
"Worse is Better" contrasts what Gabriel calls the MIT approach , with the cornerstoneof 'the right thing', against the New Jersey approach , with a 'worseis better' minimalism (this is a simplified summary). Gabriel arguedthat despite its flaws, the New Jersey approach had significantly bettersurvival characteristics than the
The difficulty of punishing people at universities
One of the quiet little secrets of university computing is just howdifficult it is to actually punish people for doing bad stuff withcomputing resources. Really bad stuff, things that are criminal orhave serious civil liabilities, can be punished. But mere violations ofpolicies or bad network behavior (including spamming) can run into aseries of problems.
Tenured professors might as well be the left hand of God, of course,especially if they get grant money . But evenstudents (grad and undergrad both) are heavily protected
What disk IO stats you get from the Linux kernel
To follow up my previous entry on iostat problems ,here's a rundown of the information you actually get from the Linuxkernel.
First off, you only get this from 2.6 kernels, or 2.4 kernels with theRed Hat disk stats patch (such as Red Hat Enterprise 3). In 2.6 thisinformation appears in /proc/diskstats ; in Red Hat's 2.4, it appearsin /proc/partitions with slightly more fields.
/proc/diskstats fields for
Easier Solaris patch management with pca
Every so often having comments on here really pays off. A commenteron my previous entry gave me a pointer to pca (Patch Check Advanced), anactual sane patch management program for Solaris machines; if you wantmore reasons to take a look, see my longer comments .
One of the nice things about pca is that it led me to the patchdiag.xref file, which is a big cross index of all of the Solaris patches, and to patches.sun.com in general. Patchdiag.xrefis
Using threading to implement a 'busy' cursor (a tale from long ago)
A very long time ago, I spent a year being an Amiga programmer as partof a small team writing an application. We wanted it to have a busymouse cursor (the general hourglass 'this is going to take a while'cursor good apps put up during long operations), but what with one thingand another, we wound up with two problems:
- we weren't actually sure what user actions would take a longtime.
- we got to 'implement a busy cursor' rather late in the whole
Hotmail spam stats revised
It turns out I made a mistake in my Hotmail stats for this week that missed some Hotmail rejections thatwere for @sympatico.ca addresses. There were actually 11 messagesrefused due to their IP origin, from six different IP addresses:
| Count | IP | In | (Size) | Listed since | Owned by |
| 4 | 62.166.232.22 | SBL15419 | March 6th | Versatel (Netherlands) | |
| 3 | 81.199.172.231 | SBL |
A helpful Apache safety tip
This is a two part safety tip:
- most things that roll Apache logfiles
SIGHUPApache to get it toclose and reopen the logfiles - when Apache is
SIGHUP'd, it closes its current set of sockets andtries to listen on the set that its configuration file says itshould use.
So, if you have changed Apache's configuration of what it should listenon, and something else is currently camped on one of those places,something that is scheduled to be killed off during an impendingreboot, and your logfiles
Weekly spam summary on March 25th, 2006
The basic volume numbers for this week are that we:
- got 19,744 messages from 236 different IP addresses.
- handled 19,083 sessions from 955 different IP addresses.
- received 139,156 connections from at least 43,459 different IPaddresses.
- hit a highwater of 31 connections being checked at once.
We got more emails this week than usual mostly because of a small mailloop explosion during the week that added several thousand