Skip to main content

Tethered or Untethered?

I don't want to be tethered.

From The Free Dictionary:
A rope, chain, or similar restraint for holding an animal in place, allowing a short radius in which it can move about.
I don't think I am an animal, at least in the sense that animals are somehow distinguished from humans.
How about:
A similar ropelike restraint used as a safety measure, especially for young children and astronauts.

Nope - I'm not a young child, nor an astronaut. Maybe I wanted to be an astronaut when I was a young child, but that doesn't count.


The extent or limit of one's resources, abilities, or endurance: drought-stricken farmers at the end of their tether.

I might be at the end of my tether. But only because I'm tethered when I want to be untethered.

When we first connected two computers together to form a network, we created a connection, or a tether, that mechanically bound the computers to each other. That binding lasted until early wireless technology permitted a computer to be on a network without being wired to that network. Now we freely roam about on wireless networks, untethered. Sort of. We still have to be near a wireless network access point, but that's not to hard do do now days.

So we are untethered, right? Not quite -we still need our power cords, wall warts, power bricks and international adapter plugs. But to be tethered to a wall only by power requirements is a huge advancement the overall state of personal freedom. We can go for a couple hours at time freely moving about the home, workplace or nerd conference, and enjoy the ability to move about unhindered by a 'rope, chain or similar restraint'.

Until the energy runs out. Then we frantically re-attach ourselves to our tethers, this time the -/+ 12vdc ones. And as the day goes on, and we burn our battery reserves, we find ourselves budgeting our wall-connect time, scrambling for conference tables near the wall jack, pulling extension cords out of oversized briefcases (or undersized steamer trunks on wheels) in a desperate attempt to stay attached to the wireless network until the last BOF of the day. Yep - we frantically scramble to wire ourselves to a wall so that we can stay connected to a wireless network.

Of course as the day goes on, we find that the ratio wall-tethered to untethered time isn't quite enough to keep us alive all day, and we inevitably enter the downhill spiral of ever shorter periods of untethered freedom followed by ever longer attachments to wall plugs, until we finally can leave our leash and our oversized briefcases (or undersized steamer trunks on wheels) in the hotel room and enjoy the conference.

Somewhere along the line we've decided to trade power or performance for battery life, almost as though we are afraid to be untethered for more than 2 or 4 hours. The thought of being completely disconnected, free to move more that 3 meters from a wall for more than 2 hours, must scare us. Or else we'd have figured out a solution by now.

There simply are no contemporary laptop computers that have reasonable battery life, where reasonable is defined as somewhere close to a normal day. The best we've come up with is 2 hours of freedom for $1000, or 4 hours of freedom for $2000. Or in the case of my home notebook, one hour of freedom for $500.



  1. Just recently discovered your blog. Love it. In my opinion, one of the best sysadmin blogs I have ever read. Thank you.

  2. @john -

    Thank you.

    The real challenge is in keeping it up. The people that have been doing this for years have my respect.


Post a Comment

Popular posts from this blog

Cargo Cult System Administration

Cargo Cult: …imitate the superficial exterior of a process or system without having any understanding of the underlying substance --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.
The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:
Failing to understand the difference between necessary and sufficient. A daily backup …

Ad-Hoc Versus Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to…

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. These …