Like Lear on the Moors

Blow, winds, and crack your cheeks! rage! blow!

– William Shakespeare, King Lear


  

Before wind (left); after (right)

Had access to a digital camera this weekend, and so I made the most of it by taking pics of this and that.

Glad I made the effort because the winds we had last night left the magnolia tree in the front yard looking like fall had come. (See today’s photo, right. Same tree, roughly same shot, less than 24 hours later…)

White bracts (the so-called blossom petals) strewn all over the yard (in back, as well) and the branches almost naked, just a blossom here and there and the small green leaves starting to push out.

The Power of Shower

Why is it that a simple shower often opens the floodgates for mental acuity?

I can’t tell you how many times I’ve been in the shower and – out of nowhere – a solution to an algorithm I’ve been working on pops in.

Weird.

This moring was the same – last night I had tried to think of how a TV series (Monk) had ended it’s season; I knew there was some twist, it wasn’t a normal show.

But I couldn’t grasp it.

In the shower – after not thinking about it for approximately 12 hours – bing! – I remembered the ending (he flies to NYC to track down his wife’s killer).

Why did it pop in like that? This happens all the time. Maybe I should set up an office in there…

I’m Missing the Point

Like a lot of techies and/or Penguin-heads out there, I’ve been following the whole SCO-vs.- [well, everyone] battle that has pitted the small Utah-based Unix company against…well, the entire, global Linux community and beyond.

For those not familiar with the whole mess, here is an encapsulated summary:

SCO says it owns the rights to Unix; SCO says this same Unix code is in Linux, so SCO is busy suing a lot of Linux vendors/users (IBM, Daimler-Chrysler, Autozone) and being sued by others (RedHat, Novell) for same actions.

Yes, that is a greatly over-simplified version of the whole mess. But necessary for what follows.

There was a very good story on Salon.com today (subscription or “view ad get daily pass” required) about the SCO frontal – and the OSS backlash – titled Making the world safe for free software.

In the article, a short summary (far better than mine) outlines the whole issue of SCO vs. [everyone], and what is happening – pre-legal outcome[s] – to combat this issue. In general, it addresses how Linux – or any such non-company product – can survive our litigious times.

The focus of the article is on Open Source Risk Management (OSRM), a company that is trying to act as an independent – yet OSS-friendly – insurance agency for companies using Linux. Notable among OSRM’s hires is Pamela Jones, the Head WebMistress of Groklaw, the simple blog turned open-source legal defense for Linux. Groklaw – the Anti-FUD.

It’s an interesting article and OSRM has an interesting tack on the whole indemnification issue, but – to me – this should be only a first step. Maybe it is; however, neither the article (nor anything else I’ve written) seem to indicate otherwise.

Bear with me, as I’m not a lawyer and just not that bright (obviously…), but here are some of the issues/contradictions I see, as well as comments on the current condition:

  • SCO will fail in its lawsuits: However, the whole lawsuit thing was a good wake-up call for the OSS industry/users. This stuff (nuisance lawsuits) – as Pamela Jones notes in the Salon article – are not ever going to go away.
  • Copyright laws don’t work for software: Read (Prof.) Lawrence Lessig’s blog at any point for more on this, but there are too many issues with U.S. copyright and software to easily reconcile. If I’m in possession of stolen hard goods (TV, stereo), it can be seized, but – unless I knew it was stolen – I can’t be prosecuted. However, I’m running Linux – legally, I can be prosecuted for buying Linux from a valid company and using it according to the terms set by company even if I have no clue about contested code. That seems…odd…
  • Why Insurance?: The whole OSRM concept (as I’ve read it) seem to be to scour the code (what code? Not clear) and then indemify companies that use such. OK, I get it, but this feeds nuisance lawsuits in two ways:

    • It gives the potential plaintiffs “deeper pockets” (insurance dough) for nuisance lawsuits to target.
    • It puts the burden (cost) on the end user (say, me, a Linux user) rather than the provider (RedHat, SuSE etc.).

  • Why not an Underwriter’s Laboratory (UL Listed) concept?: This is the logical extension of what OSRM is doing, but they don’t seem interested in doing such. How would it work?

    • Linux vendor (RedHat, SuSE etc.) grabs a certain Linux tarball, attaches some of it’s own stuff (maybe) and submits it for approval. Pays for this review. (Also an incentive for competing companies to at least agree upon a base kernel so the cost can be shared; added libraries or proprietary code is extra).
    • OSRM does the code review; pronounces it clean if OK; sends it back with “issues” if such are found.
    • If issues are found in OSRM-approved code in the future, that’s OSRM’s problem – upon approval, they give indemnification.
    • NOTE: The above does not address the issue of folks who grab the raw Linux code and compile.

I’m sure I’m missing something, but why not some sort of move where a third-party (OSRM, for example) can give blanket indemnification? Instead of each RedHat client (for example) having to apply for this insurance Yes, it could be a bundled cost, but doesn’t that point to the need for something “UL-like” as I’ve pointed out?

People who run Linux that is not UL-listed, well, same as building your own power strip.

Your house may burn down.

If it does, you don’t have a recourse.

Which is fine – keeps choice open, but protects those (yes, at some cost) who want protection.

Database Days (Daze?)

Over the last couple of days, I’ve turned my Inner Geek into DBA geek in a manner of speaking.

As a Web developer, I’ve of course been messing with databases for years in different capacities, but over the last couple of days I concentrated on two database-related tasks in an effort to better myself/my Web skills.

And it’s fun!

The items:

  • Replication (in this case, with MySQL)
  • Perl DBI

Without any further ado…

Replication (in this case, with MySQL)

Yes, I have long understood the whole concept of replication. I’ve worked with replicated, clustered, fault-tolerant DBs for years.

It’s just that I never really had a hand in actually setting up/maintaining any DB other than a single, stand-alone instance until now.

Yesterday, in a (for the most part) completely painless process, I configured replication from the MySQL instance on my main Linux box (master) to a MySQL instance on my main Windows box (I use SQL Server for my Windows apps, for the most part).

I was inspired when I read – on his blog – that Jeremy Zawodny’s MySQL book has been released.

Zawondy is a MySQL guru who works for Yahoo!, and he has much knowledge about the subject (and a good sense of humor – he’s worth reading for non-tech matters, as well).

One chapter of the book was available on the O’Reilly site (the publishers), the chapter on replication. (Note: Link to download page; chapter is a PDF file.)

So I downloaded it and thought, what the hell, let’s set up replication here!

And – as mentioned above – it was rather trivial to set up. For all I bitch and moan about MySQL (legitimately, I think), it still has a lot going for it. And I use it more every day.

One thing JZ’s tutorial left out was the issue of how to set up replication with Windows – the examples were all Linux-centric (which is fine, as MySQL is primarily a *NIX product).

However, since I rarely use the Windows MySQL, I had to dig around to find things. Such as the base configuration file.

On Linux: /ect/my.cnf

On Windows: c:/winnt/my.ini (may differ with different installations; but the file is “my.ini”)

Once I found that file, I made the changes, restarted servers and … damn… it just worked.

I’m sure I did some things stupidly, but that’s part of the learning curve – when something breaks, you figure out why and that’s how you get better.

But – so far – nothing’s broken. Excellent.

Perl DBI

I’ve just never gotten around to messing with this (I bought a book about it over two years ago…), simply because I’ve primarily done Web programming, and the scripting languages – ASP, ColdFusion, JSP, PHP – have been more than adequate for most tasks.

Now that I’m working more on learning back-end tools – CRON, parsing, data loads, shell scripts and so on – it seemed to make sense to (begin to) learn the Perl DBI so I could run simple Perl scripts to do a whole bunch of stuff that would be more convoluted with Web scripting languages.

So I wrote my first Perl script that uses the DBI – a CRON job that runs each night and updates a given database/table in my MySQL database server.

It’s a trivial example, but something that mimics a file I had written in PHP and does the same in less lines.

That’s good!

The Coin Toss on Privacy

In case you’ve been asleep for the last couple of weeks, there is small firestorm raging over Google’s introduction of it’s e-mail service, GMail.

Some links of note outlining the firestorm are via Dan Gillmor, news.com (see related stories there, as well) and CNN.

The question (I’m addressing here) is: Is this a valid firestorm or a tempest in a tea pot?

What Google is offering with GMail is intrinsically the same as the e-mail services offered by other large Internet players, such as Excite.com, Yahoo.com and Hotmail.com. However, since Google is a late-comer to the free e-mail party, it has to differentiate itself.

Some of the differentiations are what is what is raising the ruckus – in one case, a California (of course) legislator is attempting to block the official launch of GMail (now in Beta):

A California state senator on Monday said she was drafting legislation to block Google Inc.’s free e-mail service “Gmail” because it would place advertising in personal messages after searching them for key words.

“We think it’s an absolute invasion of privacy. It’s like having a massive billboard in the middle of your home,” Sen. Liz Figueroa, a Democrat from Fremont, California, said in a telephone interview.

“We are asking them to rethink the whole product,” she said.

– Reuters via CNN, Tuesday, April 13, 2004

Hmm…sounds serious…

Is it?

There is always the other side of the coin (obverse vs. reverse); let’s look at some of the issues GMail (may) introduce and draw some conclusions. I’m from Illinois – the Land of Lincoln – so let’s use the obverse (head) and reverse (tails) sides of a penny to set the Issue|Issue Deconstructed:

Heads: The service Google is offering is – essentially – the same as other site’s offerings: Free e-mail, X Meg storage, contact list, browser-based blah blah….

Tails:Yeah, everyone pretty much agrees that the basic concept does not significantly differ from others; it’s the other stuff. But that’s not the point of…this point.

Heads: GMail will scan your e-mail and place paid ads that correspond to the content of your message. (This is the one that gets everyone’s undies in a bunch)

Tails:This is the nasty part for most folks, and it’s not even touching the ad-clutter (making $$ off my messages??) nonsense.

To a degree, this is a valid issue. It comes down to privacy, but does this argument hold up?

Example: I have a wife and a mistress (example, dammit!!); I use GMail for the Mistress. When I’m getting a (hot and heavy) message from the Mistress, there are ads for “Is Your Spouse Cheating On You?” software, sex toy shops or whatever. Disquieting, to say the least, I would guess.

But is Google reading your e-mail? Sure, because I got an ad for the hotel I told the mistress I was going to take her to…

OK. Define “read” – yes, Google read your e-mail; so does anti-virus software (offered by other similar providers, such as Yahoo and Excite). In the latter case, plain-text RegEx matching toasts an entry based on keywords (supplied by user); in the former it toats an entry or displays it with keyword-based ads.

OK. The one (virus) you don’t see; the other (ads) you see. Both are based on ASCII-text keyword algorithms.

Heads: Google’s current privacy terms for GMail sound fairly draconian – they may or may not delete stuff and so on. Sounds fairly invasive, to put it nicely. (I’m not going to link, as I expect the terms to change dramatically in the short term)

Tails:I think Google is catching flack for its honesty. Honest. I have test accounts on Yahoo, Excite and Hotmail and – while I should – I have never read the goddam terms. Yes, I should. My guess is that these three (and others) don’t explicitly mention what happens to that “myMistress” folder when you delete it. Is it really gone? Can the FBI, John Ashcroft, my mistress’ husband get it recovered? Does “delete” mean “gone forever”? (Duh – of course not. Google just admits this.)

OK, here is my bottom lines on all of this fuss:

  • I think Google vastly underestimated the issue of privacy and – more importantly – the scrutity they get for any move they make.
  • GMail is free – at least as currently planned. Don’t like Google’s terms? Don’t use GMail. That part is very simple.
  • OK, your mistress has set up a perceived dangerous GMail account. Your incoming e-mail (to her) is scanned and ads displayed on the strength of your dirty talk. That’s not the issue: The issue is is the message somehow stored? Somehow accessible by humans, not just software scripts?

The last part is huge, and has two parts:

  • Is the info stored?
  • If stored, can this info be stored with associations to [me/you/mistress/Bin-Laden…]?

That’s the crux of the issue: This is “my” e-mail, is there the possibility that someone else (i.e. Google) can get their hands on “my” e-mail?

And the bigger – perhaps biggest question: Does this “someone else” have any plans to draw conclusions about me by reading my e-mail?

Good questions…

Random Musings

WATCHING:
21 Grams

I was expecting a drug movie – the 21 grams was the clue – but this movie, while having some drug use, is not about drugs.

It’s about the intersection of three people (and – peripherally – the people associated with those three) whose lives accidently intersect, told in a series of out-of-sequence vignettes (some brief, some extended).

Not a feel-good movie; not a great movie, but very, very good. Sean Penn again demonstrates that he’s one of the finest actors out there.

All movies

Some random musings on some non-related issues:

Microsoft Circles the Wagons

This issue is worthy of a full entry, but for now I’ll just make this point: With the spate of recent settling of scores (Sun Microsystems, InterTrust), MS appears to be circling the wagons by throwing money at companies with two objectives in mind: 1) Shut down expensive and distracting litigation, 2) Set the stage for the next version of Microsoft (the company), where it exercises it patent and DRM portfolio, and concentrates less on the actual software. It increasingly becomes a licensing company.

I’m sure I could be wrong about all this – and it wouldn’t be the first time – but MS has blown through a few billion recently to settle scores. That’s a lot of money, even for a company with ~$40 billion in the piggy bank. These are strategic moves.

The Constitution Terminator

There’s been a lot of ink (digital and otherwise) tossed at the issue of Supreme Court Justice Antonin Scalia’s erasure of recordings of a recent speech. (Note: A federal marshall did this; not Scalia.)

Lost in this issue is, to me, a discussion as to why Scalia doesn’t want his public speeches recorded.

First of all, if it is a public speech, doesn’t that pretty much grant anyone the right to record? Private talks or off-the-record talks with reporters I can see as his call to define, but speeches?

Second, if he’s so against recording his speeches, why give them?

And what’s lost if they are recorded? There were quotations of his speech given in stories about this who situation, so – apparently – quoting him is OK…as long as it’s by hand (is recording his speeches with shorthand allowed? Apparently.

Supreme Court spokesman Ed Turner said that Scalia was unavailable for comment. “The justice generally prefers not to have audio or video recordings of his remarks,” Turner said.

Washington Post, 4/9/2004

I don’t know, this is just a little bizarre to me.

Lily Day

Well, it’s Easter, and when I went into the grocerty store yesterday, the store was packed.

And it seemed like everyone was buying Easter lilies.

Madness!

The picture at right is actually an Easter lily from years ago – after Easter, it was going to be tossed. So I sav ed the plant and shot a few sheets with my 4×5 view camera. They turned out nicely; the full-sized image is a (scan of the) contact print from the negative.

Ah, I miss the darkroom some days…

I Parse, Therefore I Am

No matter what the shape/type/scope of a database driven application, at some point days of building parsers is involved.

These parsers can be final parsers, which will load (either one-time or CRON jobs) real data into the database, or they can be ad-hoc down-and-dirty scripts that load test data.

For either of these uses, Perl is your friend.

Can’t beat it…

The Economic Walden

READING:
Nickel and Dimed: On (Not) Getting By in America
Barbara Ehrenreich

Ehrenreich’s Thoreau-like adventure, with the world of manual, minimum-wage jobs as her Walden.

The basic conclusion of the book is simple: A job and hard work does not translate to a ticket out of poverty.

All books

In 1998, Ehrenreich, like Thoreau before her, set off to see if she could survive on her own; she reported her findings in Nickel and Dimed: On (Not) Getting By in America, which I started and finished today.

While Thoreau set off for this cabin in the woods surrounding Walden Pond, Ehrenreich set off for a more contemporary, yet just as isolated area: Leaving (to a degree) her safety net of family, Internet access, home and current occupation (writer), she sought full-time work for poverty-level wages.

Working as a waitress in family-style restaurants (think Denny’s), as a maid as part of a home-cleaning crew and as a menial associate at the world’s largest retailer – Wal-Mart – Ehrenreich came to the conclusion that having a full-time job was not the ticket out of poverty:

Something is wrong, very wrong, when a single person in good health, a person who in addition possesses a working car, can barely support herself by the sweat of her brow

  – Evaluation chapter

She worked in three different cities – sometimes working two jobs at once – and yet she still comes to the conclusion that she could not have endured much longer than the month she allotted for each city/job if she had had any sort of non-basic (food/clothing/shelter) costs: These non-basic costs would include any medical care, fixing her car and so on.

It’s a disquieting message that Ehrenreich went into this project expecting, yet her proof-by-experience is damning.

While I don’t necessarily agree with all her conclusions/accusations – she paints all management as Dilbetian pointy-haired bosses, and still wonders why the menial workers (of which she became one) don’t demand more for their labors – her book draws some interesting conclusions, many of which she never specifically states:

  • She is an educated, healthy, unencumbered woman. What of others with families or ailments. If she can barely get by, what does this mean for others who shoulder extra burdens? From what Ehrenreich writes, she was a rarity among those she worked with in many ways: Car, ability to put a deposit on an apartment, no children and associated costs/constraints. Again, if she can barely – just barely – make it, what of others?
  • She worked with a lot of co-workers – full-time workers – who were either homeless or depended on a second income (spouse, friend, roommate) to cut housing costs.
  • Affordable housing just is not keeping pace with the demand. If one considers geographically accessible housing (low income workers frequently have no car), and the number of affordable units dwindle to near-zero.
  • Food costs are higher for the less wealthy simply due to conditions – for example, Ehrenreich once received a box of food from a food pantry, and one item in the collection was a canned ham. Without a refrigerator – and in her case, living alone – the extra meals this large hunk of meat could provide were only marginally useful to her: Without a refrigerator, she’d have to eat it all in one sitting. (She ended up donating this box of food to another pantry). While I’ve read similar reports – the poor have to eat fast food/buy from convenience stores due to time constraints, but the costs are higher – it hits home with an example such as this.
  • I hadn’t realized that a lot of companies hold workers’ first weeks check as a security deposit of sorts, giving the money back at some future (termination, after X months) date. For someone living check to check, this is another incentive to not leave a job – one can’t afford to miss a check in this manner.

This book was written in 1998, when the economy was booming. Especially in Minnesota, where Ehrenreich’s last job was located, the boom fueled a demand for workers, yet conditions were still appalling and wages seemingly artificially low. Today, whatever leverage workers had due to a demand for manual/service-sector labor is obviously missing. It’ll be interesting to see if she revisited this issue recently to see – in a statistical manner, at least – how things have been changed by the job market forces.

Ehrenreich (almost) closes with the following message:

When someone works for less than than she can live on – when, for example, she goes hungry so that you can eat more cheaply and conveniently – then she has made a great sacrifice for you, she has made you a gift of some part of her abilities, her health, and her life. The “working poor,” as they are approvingly termed, are in fact the major philanthropists of our society. They neglect their own children so that the children of others will be cared for; they live in substandard housing so that other homes will be shiny and perfect; they endure privation so that inflation will be low and stock prices high. To be a member of the working poor is to be an anonymous donor, a nameless benefactor, to everyone else.

  – Evaluation chapter.

Ehrenreich then finishes up the book with a short paragraph saying she expects the workers like she worked with to someday tire of taking all the crap and demand a living wage.

Unfortunately, this is not a reality I see happening. For example, one of the points Ehrenreich makes in her book is that job listings don’t necessarily reflect need: Some companies keep a listing going forever, as turnover is fairly constant and the applications are frequently needed. It’s cost-effective to keep the ads running regardless of current needs.

In other words, the lowly workers don’t have any leverage. Yes, they may deserve more money/respect and so on, but – if you’re unhappy with your job – there is always someone else to fill it. It hurts the worker more than the company, or the company would not tolerate this consistent turnover.