Spotted this on my rounds this evening…

Spotted this on my rounds this evening…
In the early days of my participation in the Texas Renaissance Festival, around 1988 I suppose, I met a man named Bill Sanders. I can recall walking up the slight slope which passed what once was the battle mound coming out of Sherwood Forest up to where the Wharfside Music Gazebo now stands.
At the crest of this small hill, standing alone and gazing at an astrolabe, was a curious looking man dressed in black leggings and a black doublet with red piping. His long black hair shooting wildly out from under the floppiest of hats, his wiry beard formed a fuzzy half-moon shape that reached from one ear to another.
I remember I was walking with my band-mate and friend, Joe Linbeck, and he knew this guy so we stopped to chat. That was when I met Bill Sanders.
Bill was at the festival and playing the role of Galileo. All the time we spoke with him he remained in character and was quite amusing. Joe and I wandered off to do whatever it was we on our way to do, but the memory of Bill lingered.
Back then we used to camp out at the festival and hang out with the other actors and musicians. Bill kept a pretty elaborate camp site and it was a gathering place for Rennies in the evenings. That year and the next my band-mates and I stuck up a pretty good friendship with Bill and we spent many evenings drinking and listening to Bill tell stories. You see, Bill was a history major (well out of college) and had a penchant for very esoteric historical events and had a way of telling stories that was quite amusing. Bill would cast those who listened to him tell his tale into the roles of those he was recounting the tale about. It was always engaging and always monstrously funny.
One year I recall I was wandering around the festival site late at night when my fiddle player Greg and Bill loomed up out of the darkness near the Globe Stage.
Greg was an expectant father at the time. His wife Deborah was pregnant with his unborn daughter Joanne. Bill was a father of two preadolescent girls and had spent some time “counseling” Greg on what to expect as a father. To this end he had told Greg the story of Sawny Bean, the cannibal of Scotland, as a cautionary tale of family values.
Let me give you a brief synopsis of Sawny Bean. The legend goes that a man named Sawny Bean lived in Scotland in the 12th or 13th century. Allegedly he took a wife and took up residence in some caves on the Road to Edinburgh and there he raised a family of over 40 inbred cannibals that preyed on the travelers to and from the city for over 20 years before they were captured and executed.
Bill postulated that the downfall of the Bean Clan most certainly resulted in a breakdown of family values. Sawny would have had rules about capturing the travelers and bringing them back to the caves to kill and eat. He might have warned against lighting any cooking fires and admonished his offspring to leave no survivors and no trace of their existence.
These simple rules allowed the clan to go undiscovered for over 20 years. It was only when some of the older children were on a hunt and decided to cook their prey and have sport with the women that a hapless traveler escaped and fled in a terrified panic back to Edinburgh with is tales of horror and cannibals.
You could just imagine those those kids saying “T’hell with dad and his rules!!!” followed by that adolscent “uh-oh” when the traveller escaped and they returned, sheepishly, to the caves to tell dad of their error.
Prior to this the people believed the road to be haunted to plagued by monsters. Now they knew what they were up against and it was a simple matter of tracking them down and capturing them, which they did in short order.
This story captured my imagination and Bill and I would spend countless hours pouring over the details and speculating about those events late into the evening and well into the wee hours of the following morning.
One night at the Globe Stage Bill and I were sitting and talking when Greg Taylor wandered by. Greg Taylor now plays the role of King Henry the VIII at the festival but back then he had a more humble calling. He was Gipepetto the Pickle Boy (or something similar), hawking pickles to the patrons. Neither Bill nor I really knew him but he seemed a nice enough fellow. In later years Greg Taylor confided that he was not really sure WHAT he had gotten himself into when decided to stop and “break bread” with Bill and Jay the Cannibals as we came to be known.
As we conversed Bill and I told him the story of Sawny Bean. As we told the story more people wandering by and stopped to listen.
In true Bill form he began to cast the audience into the roles of the characters in the story. I was Sawny Bean, Greg became the father of his bride that was killed before Sawny fled to the caves to start his family. The various passers by became the travelers on the road to Edinburgh who were set upon and devoured at which point they became members of the ever growing clan and so forth. It went on this way until everyone was a part of the story.
In the end everyone became the cheering town-folk as I, in the role of Sawny Bean, was executed.
There must have been 15 or so people who witnessed that. Bill and I discussed it after everyone had moved on and we thought it might be a good idea to try and tell this story in this manner on the Saturday of Halloween weekend.
We picked the stage that is now The Odeon as the site for our tale and invited anyone who would listen to meet us there at 9:00 pm for a Halloween story. There was a jack-o-lantern carving contest being judged at 8:00 and we figured when that was over people would trickle over to our stage and we would have some fun.
Bill and I staked out the stage with a few others, including Greg Taylor, and prepared ourselves.
As it approached 9:00 pm there was really nobody there and we began to think that our idea was a bust and were getting ready to move on when someone said “LOOK!”
We all turned to see what it was and there, in the distance, was a line of lit jack-o-lanterns being held aloft as a parade of people wound their way through the site headed right for our stage.
Each of the jack-o-lanterns was placed at the foot of the stage like a stage light and people began filling the benches. It must have been a hundred people or more.
We told the story and by the end most of the people were on the stage, cast in one role or another. It was magnificent.
The next year Bill and I worked together in the performance company and we told that story, in that way, to the patrons. In fact, that is when I met Cynthia who was a cannibal groupie back in the day.
To this day they still tell the tale of Sawny Bean on Halloween weekend at the festival. Bill Sanders passed away a few years ago and I haven’t attended the event in many, many years myself, but it makes me happy to know the tradition lives on.
One of the odder aspects of doing radio is the fact that prisoners in Huntsville tend to listen to the station.
In this fast paced, connected Internet world we live in it’s all instant messaging, cell phones and e-mail. Of course the inmates at the local correctional facility don’t have access to such amenities. When someone there wants to make contact they have to do it the old fashioned way and send a hand-written letter.
I tend to get about two or three letters a year from someone in the Wynne Unit. You can always tell it’s prisoner mail when you see it. The hand-written address on the envelope is dead giveaway. When you open the envelope to remove the letter a small piece of paper usually falls out that says
GENERAL INMATE CORRESPONDENCE – TEXAS DEPARTMENT OF CRIMINAL JUSTICE – INSTITUTIONAL DIVISION
It’s like one of those ‘Inspected by #42’ tags that you find in the pocket of a new pair of pants.
Most of the time the letter tends to be a question about what to study to get a computer job when the inmate is released or some other question about something we talked about weeks before.
Last night there was a letter in my station mailbox and it was immediately obvious it was another prison letter. I opened it up and read it. It was an unusual letter in that it asked nothing of me. No question to respond to or anything. It was just one prisoner’s observations on the show.
This is how it started off:
Jay and everyone else,
Greetings. Yes I’m writing from prison but before you start thinking I’m some tin-foil hat wearing weirdo stalker type person, let me assure you I have never even owned a tin-foil hat! Kudos on the show, I’ve even learned a thing or two but usually, though, I just tune in for all the jackassery so double kudos on that!
—
The rest of the letter went on to describe, quite humorously, some of his observations of the program. I read the whole thing on the air last night. I hope he got to hear it.
It made me think how much I miss hand-written letters. There’s something about holding a piece of paper in your hand and reading the contents when it’s something crafted just for you in such a manner.
Oh, and it had the word jackassery in it! That is, certainly, an underutilized term that I think should be used much more. As you prowl the Interweb today you should drop it on your friends in casual comments and conversation.
For the pajama party Cynthia made custom PJ’s for herself and for me that came out REALLY well.
The ratio of pajama-clad to pajama-free was respectable.
I think everyone ended up having a really good time. Thanks to everyone who came out!
Last night’s show was, well…interesting to say the least.
At one point I was describing Groovehouse‘s eagerness to answer and screen calls as we were inviting listeners to call in. I used the idiom “chafing at the bit” as in “Groovehouse is chafing at the bit to take your call.”
At this point I noticed someone on IRC and Phliktid having a good laugh I asked them to share what was so funny.
Apparently someone in IRC found great humor in my application of the word “chafing” and pointed out that it should be “chomping” or possibly “champing”, suggesting that “chafing” was incorrect and intimating that the connotations of “chafing” was strictly an inside the pants situation.
Basically he called me out on a mixed metaphor. I was horrified. Could I really have been using an incorrect figure of speech so egregiously all my life? That’s unpossible!
I struggled vainly to explain that it could totally be “chafing” when one considers that a horse straining against the bit of the bridle might chafe the inside of the horse’s mouth but he would have none of it.
For the sake of good radio I conceded my lifelong error and moved on. Until this morning when I did some research. As it turns out “chafing at the bit” is completely interchangeable with “chomping/champing at the bit” and is a widely accepted version of the idiom.
IN YOUR FACE, SPACE COYOTE!
Another incident involved the idiom “Curiosity killed the cat” used by a caller to describe his efforts to diagnose his own problem and perhaps going a bit too far and ending up doing more damage.
When the caller said that, I responded with a quick quip along the lines of “we like dead cats.” at which point one of our guests looked like he’d been hit by a truck. Oh yea, he’s a huge cat person. I should not have been surprised.
It certainly was not my intention to offend any cat lovers (although they are such easy targets). What I meant was that if curiosity kills cats then those who appreciate or participate in curious behavior (something that describes most nerds) must like dead cats.
Not literally! I was being idiomatic!
It’s not like we had a real bridle on Groovehouse chomping, chafing or otherwise. Of course no-one seemed to take issue with the idea when the idiom was used. No one rallyed to Groove’s cause when it might be suggested that, even if only idiomatically, he might be strapped into some type of riding harness. But use the word “dead” and the word “cat” in a sentence and watch out!
Anyway, I stand by my free lance idiom “I like dead cats” to describe my curiosity and offer it up unto the every-growing lexicon of language. In fact, upon further reflection and refinement of thought I would add “I’m killing a cat” and “I’m committing cat suicide” as ways to describe indulging in one’s curiosity.
For the record, I do like cats and I am in no way an advocate of killing them.
.
After my post about how to deal with IT people when seeking assistance one of my readers provided me with the following story from The Register.
—
Oklahoma city threatens to call FBI over ‘renegade’ Linux maker
Follow the link and scroll to the bottom to read the related stories.
The heartland turned vicious this week when an Oklahoma town threatened to call in the FBI because its web site was hacked by Linux maker Cent OS. Problem is CentOS didn’t hack Tuttle’s web site at all. The city’s hosting provider had simply botched a web server.
This tale kicked off yesterday when Tuttle’s city manager Jerry Taylor fired off an angry message to the CentOS staff. Taylor had popped onto the city’s web site and found the standard Apache server configuration boilerplate that appears with a new web server installation. Taylor seemed to confuse this with a potential hack attack on the bustling town’s IT infrastructure.
“Who gave you permission to invade my website and block me and anyone else from accessing it???,” Taylor wrote to CentOS. “Please remove your software immediately before I report it to government officials!! I am the City Manager of Tuttle, Oklahoma.”
Few people would initiate a tech support query like this, but these are dangerous times, and Taylor suspected the worst. (Er, but only the world’s most boring hacker would break into a site and then throw up a boilerplate about how to fix the hack.)
CentOS developer Johnny Hughes jumped on the case and tried to explain the situation to Taylor.
“I feel sorry for your city,” he replied in an e-mail. “CentOS is an operating system. It is probably installed on the computer that runs your website. . . . Please contact someone who does IT for you and show them the page so that they can configure your apache webserver correctly.”
That response didn’t go over so well.
“Get this web site off my home page!!!!! It is blocking access to my website!!!!~!,” Taylor responded, clearly excited about the situation and sensing that Bin Laden was near.
Again, CentOS jumped in to try and explain some of the technical details behind the problem. It pointed Taylor to this page, saying it was the standard page for a web server and noted that it provides instructions on how to fix the problem. The CentOS staffer suggested that Taylor contact his service provider or have an administrator look into the issue.
That response didn’t go over so well.
“Unless this software is removed I will file a complaint with the FBI,” Taylor replied.
Later he added,
“I have four computers located at City Hall. All of these computers display the same CentOS page when attempting to bring up Tuttle-ok.gov. Now if your software is not causing this problem, how does it happen??? No one outside this building has complained about this problem. This is a block of public access to a city’s website. Remove your software within the next 12 hours or an official complaint to the FBI is being filed!”
And later,
“I am computer literate! I have 22 years in computer systems engineering and operation. Now, can you tell me how to remove ‘your software’ that you acknowledge you provided free of charge? I consider this ‘hacking.'”
After a few more exciting exchanges, CentOS managed to track down the problem for Taylor. It turns out that hosting provider Vidia Communications is running CentOS on some of its servers and had not configured the Tuttle web site properly. CentOS informed Taylor of the situation, and, a day later, Taylor had calmed down.
“The problem has been resolved by VIDIA who used to host the City website,” he wrote. “They still provide cable service but do not host the website. The explanation was that they had a crash and during the rebuild they reinstalled the software that affected our website.”
“I am sorry that we had to go through the process and accusations to get the problem resolved. It could have been resolved a lot quicker if the initial correspondence with you provided the helpful information that was transmitted in the last messages. My initial contact with VIDIA disallowed any knowledge of creating the problem.”
Er, so despite the fact that CentOS went out of its way to figure out the problem for Tuttle, Taylor still places the blame on CentOS for not fixing the problem – that it didn’t create – sooner. In addition, Taylor didn’t really start off the whole process on the best foot despite Tuttle being a town “Where People Grow – Friendly!” Grow friendly, threaten to bring in the FBI at the drop of a hat – what’s the difference?
There’s a lot of focus these days on customer service. And while it’s true that the service professional is responsible for his role in any customer service interaction, there are things that the customer can do to help facilitate a positive experience.
With that in mind, I offer these tips for dealing with your IT dept.
1. REBOOT YOUR COMPUTER
If you have not rebooted your PC to see if it clears up the problem you have done nothing. Many problems can be cleared up with a simple restart of your computer. If it’s locked up, force it to turn off by pulling the power if necessary.
When you call the helpdesk one of the first questions you are likely to be asked is “Did you reboot?” If you answer yes then you move on to phase 2 of the troubleshooting process. If you answer “No” you may be sent away to do so and have to get back into the queue for support.
Also keep in mind that just because you don’t see how a reboot could solve the problem does not mean it’s not a good thing to try. When it comes to asking for help with your computer, your understanding of the troubleshooting process is not essential to getting your problem resolved. I know it sounds harsh, but it’s true. When you call the helpdesk and you indicate you have already tried rebooting your computer the technician is likely to respond favorably to you and the rest of the troubleshooting process is likely to be way more pleasant.
It’s also quite likely that the reboot will make the call the to the helpdesk completely unnecessary and then EVERYBODY wins.
2. DON’T LIE
Your IT professional may ask you questions in the diagnosis process.
For example, the IT person may ask “Did you change anything?” to which most people reply “No, I didn’t change anything.”
Installing software programs counts as change.
Installing a security patch counts as change.
Adding or removing hardware components counts as change.
For the more painfully literal IT people the fact that you observed your computer running counts as change if you apply the Schrödinger’s Cat mental exercise. I pity you if you are cursed with such a technician.
Another common user lie is “I tried everything.” Obviously you DIDN’T try everything, or you wouldn’t be seeking help and you would have solved the problem yourself.
Speaking of trying things, if you are able to remember what you tried this can help the technician figure out how much worse you have made the original problem and guide them through the process undoing the additional damage caused by attempting to fix the problem yourself.
3. ASK GOOD QUESTIONS
Let’s say you arrive at work, turn on your computer and are unable to get to e-mail, you’re stock reports (which you shouldn’t be doing on company time, tsk tsk!) or communicate with your friends via AIM, Yahoo or whatever (again, TSK TSK!)
This first instinct of most users is to contact the helpdesk and ask “Is the Internet down?” to which the technician will usually respond to by saying “No.” This is because the Internet is not likely going to be completely down but since you asked, they answered. A good technician knows what you are really asking but is often so painfully literal that they will answer the question asked rather than try to determine what you really need.
A better way to approach this problem would be to say something along the lines of “I can’t seem to connect to the Internet, is there a network problem?” to which the answer may still be “No” but this will facilitate the process of determining why YOU cannot connect to the Internet.
4. DON’T OFFER USELESS INFORMATION
A common comment technicians hear is the phrase “It worked yesterday” or “It was working fine up until I got back from lunch.”
Well, duh. That’s what we in the business call BROKEN. The fact that something functioned before is not a guarantee it will work in the future. We know it worked fine before, that’s why we have not heard from you until now.
Just state the problem concisely. “My computer will not start” or “I’m being bombarded by porn pop-ups.”
We know your computer started yesterday and that you were pop-up free up until you cruised that non-work related web site during your lunch hour.
It’s not important and will not get your problem solved any faster.
You should also try to minimize guessing what you think the problem might be once the diagnosis has begun. Let the technician do his work.
Also, while technicians appreciate users being contrite and self effacing, you could exacerbate your problem if you subject your technician to the phrase “I’m computer illiterate” or “I know just enough to be dangerous.” It’s like those morons in the Renaissance Festival parade who go by saying “Smile and wave” not realizing that the poor patron standing there is going to have to hear that bit of cleverness from the next 50 parade participants marching by.
Say something meaningful like “I appreciate you taking the time to help me” and “Thanks.”
5. RESPECT YOU TECH’S PERSONAL TIME
In the course of the day you might see one of your IT people walking about. They are usually not just wandering aimlessly looking for someone to ask them a question. Chances are they are on their way to work on another problem or they are on a break. They might even be done for the day.
When you see one of your IT people walking by and you stop them and say “Quick question” you need to know that all questions are quick.
“What is the airspeed of an unladen swallow?” is a quick question. What takes time is determining whether you mean an African Swallow or a European Swallow and details such as wind speed, air pressure, elevation and so forth. There simply is not enough time to answer your question before the elevator doors open or before it’s time to flush and wash up.
You should also keep in mind that if you flag down an IT person on the floor and ask them for something that can’t be done immediately they are going to forget in the time it takes them to make their way back to their desk. This is because they are probably going to be stopped a dozen more times and asked a “quick question” before they make it. If you need something from IT follow the procedure and submit a ticket or send an e-mail.
Besides, the problem you are having almost certainly existed before you saw the tech walk by and the fact that you have not contacted the helpdesk already would tend to indicate that the matter is not urgent.
—
These simple suggestions can go a long way toward endearing yourself to your IT department and can mean the difference between good tech support and excellent tech support.
Billed as the Hottest Littlest Kiss Tribute Band in the World..
Pete Gordon at the Continental Club said he got a call about them coming to Houston. I want to encourage the immediate booking of the little guys!
Detroit Rock City, Baby!