5640 Reasons to Not use Windows

Well, it’s finally happened.  The last native Microsoft Windows machine at Chaos Central went down in flames this morning, to be reborn this evening as a Xubuntu machine.  Now, the demise of the system was not directly due to some minor mistake on behalf of Microsoft, but more to the general architecture that makes it necessary to constantly run virus and spyware checks on their systems.

The ultimate culprit here was the venerable ClamWin anti-virus software.  A recent virus signature update had an ambiguity in it that resulted in a number of false positives.  5640 of them on this particular system, to be exact, including, unfortunately, the ClamWin.EXE file itself, all of which got whisked away to the quarantine folder without any way to restore them and fix the links.

I had been using this system of late as the XenCenter control station for our Citrix XenServer, and–since it was there–as a VNC client for all of the virtual machines running on the XenServer.  And, of course, to run Firefox and other multi-media apps to get the audio on multimedia files, since the virtual machines have no audio connections.  I had Ubuntu 10.04 installed as Wubi on the machine, but Ubuntu’s X11 drivers were having some stability issues with the wide-screen monitor, so it seemed convenient to just boot to Windows.

The nerve center of Chaos Central, the old IBM NetVista as XenCenter and VNC client, just before the big Clam-ity that took out Windows once and for all.

Now that it is dead and gone, we still have the issue of running the few native Windows applications we have that won’t run under Wine:  XenCenter, Quicken 2010, TurboTax, and the Machine Quilters Business Manager immediately come to mind, but I’m sure there are a few others.  Oh, yes, I do need to run Internet Explorer to test new Cascading Style Sheet designs for my web clients.  So, we have properly-licensed copies of Windows XP OEM running under Oracle’s VirtualBox at Realizations Fabric Arts downstairs, and, fortunately, I had cloned the XenCenter desktop as a virtual instance itself, so the data and programs on it were not lost nor do they need restored.  From this exercise, I found it is necessary to have a separate XenCenter installation, which can be on another virtual machine, just not one on the same server you are trying to control.  Using the free version of Citrix XenServer, there are a few tools that are disabled, one of which is the ability to detach the console on a Windows machine.  Fortunately, one can share the Windows desktop remotely to a specific VNC client, so it is possible, by jumping through a few hoops, to get at the Windows desktop on a Citrix virtual machine.  Fortunately, we got to the virtual machines and upgraded the ClamWinAV packages to eliminate the problem before the bug trashed those systems, too.

So, why Xubuntu, other than just to try something different?  I first tried Fedora13, but it had some installation issues with the old Windows XP box (an IBM NetVista box we got as an off-lease refurb machine about five years ago).  It has lots of RAM, but still an old Celeron CPU.  Linux used to be very backward-compatible with older hardware, but some of the bleeding-edge distros, especially Fedora, have dumped drivers used on only a few “name brand” systems that are mostly in landfills by now. The install failure mode was a bit odd, but it wasn’t worth looking into, as there are lots of distros to choose from, and one or more of them usually works in these cases.  Xubuntu is a bit more light-weight than the regular Ubuntu edition, but has the multi-media support we need as the only audio-capable machine in-house. The machine also has only a CD reader and a primitive BIOS, so installing from a DVD or DVD image writ to memory stick was not an option, which eliminated most of the other Linux distros.  I like FreeBSD, and have used it for servers and routers, but it is a bit too labor-intensive to bring up as a graphical workstation to meet my timeframe on getting a desktop workstation back up quickly.

Concurrently with the Windows fatal meltdown, our Ubuntu laptop that is my main road warrior machine had a minor meltdown.  I had dismantled the compviz environment recently to work around some issues with VNC password windows not getting the focus, and one of the current updates shuffled dependencies around, such that the system went into a sort of zombie mode, with the windows jammed up under the top of the screen, minus their frames (no way to minimize or move the windows) and very sluggish behavior, due to one of the compviz components chewing up most of the CPU cycles in vain waiting for the missing pieces to answer back.  Restoring the deleted packages fixed that, but may have brought back the VNC login problem.  No doubt Vinagre does not have this problem, but we’re dealing with remote machines running VNC sessions on CentOS and SuSE piped through X11 tunneling under SSH, so we’ll just have to deal with it.  At least, with Linux, you can usually troubleshoot and fix things, where Windows woes turn into a reinstallation and rebuild from scratch situation.

And that’s just a typical day at Chaos Central.  Most of the day, we were off to Olympia, where we got in a bit of ‘Net time on the Ubuntu Netbook while getting an oil change on the vehicle we’re taking on road trip next week.

Veteran’s Day

On this Veteran’s Day 2010, we take some time off to reflect on our military heritage and those who have served their country. In my famly, military service has been a duty, but not a calling. Nevertheless, a number of us have served, some voluntarily, and some when asked.

Distant records are sketchy, but I do know that some of my ancestors, Huguenot refugees who came from France in the 17th century to seek freedom from religious persecution, settled in New Jersey, then fled to Canada to escape the troubles once more during the American Revolution, so saw no military service. Two generations later, the Larues, my great-great grandparents Samual and Jane, returned to the States, sometime in the mid-19th century, and raised my great-grandfather, Criness Larue, who saw service in the Union Army in the Civil War and was wounded.

criness larue, 1879
Criness Larue, Civil War veteran, at his wedding in 1879

One of my other great-great grandfathers, Dennis Tanner, saw military service in the 5th New York heavy artillery, and did not survive the experience, falling at the battle of Harpers Ferry. His daughter, Lucy, married Criness Larue in 1879, his first, her second. Lucy and Criness’ daughter, Lettie, was my paternal grandmother.

Dennis Tanner, 5th NY heavy artillery, 1861-1864, killed at Harpers Ferry, WV 10 December 1864

On my mother’s side of the family, the Pietz and Reis families emigrated from Prussia in the 1870s to escape the rampant militarism and universal conscription practiced by the newly-independent German Empire following the Franco-Prussian War. They settled in northern Minnesota, where my maternal grandmother Ella was courted by one William Strube, who did not meet approval by great-grandmother Pietz (Reis). Laura Pietz pressured her daughter to marry a more well-to-do Norwegian farmer. William, unlucky in love, enlisted in the Army during World War I. On his return after the war, he married the now-widowed Ella, whose first husband, Grant, my biological grandfather, had perished in the 1918 influenza epidemic.  William adopted Ella’s three children and, together, William and Ella had two more children, both of whom served in World War II.

William Strube, U.S. Army, 1918

Both my parents grew up fatherless, as my mother Hilda’s stepfather William succumbed to a kidney ailment in 1924, and my paternal grandparents had divorced in 1926. My father, Don, attended Dunwoody Institute (now Dunwoody College of Technology), earning a boiler license, electrician’s license, and becoming a member of the Refrigeration Service Engineer’s Society. In 1943, shortly after I was born, he was drafted into the U.S. Navy and soon found himself in a Construction Battalion in a forward supply base in the Phillippines, where he maintained the cold-storage refrigeration equipment for the duration of the war. Other than a few air raids on the field, he did not see combat.

Don’s youngest brother, Harry, served in the U.S. Army in England. Hilda’s siblings, William Strube’s natural children, brother Norman and sister Agnes, both served in the U.S. Army, Agnes as a nurse in France after the Normady invasion. Norman married Josephine, an Army nurse from Chicago. Aunt Jo recently took an honor flight to Washington, DC, with other World War II veterans, to visit the war memorial.  She was interviewed about her war experiences for a public television special about the trip.

Don, Milt, and Harry Parkins, 1941. Harry joined the National Guard after the war, retiring with the rank of Major.
Hilda, Larye, and Don Parkins, 1944 (U.S. Navy)
Cathy (Strube) Buxengard with her mother's WWII uniform displayed on a mannekin at a 2009 military ball

The Korean “Police Action” was between generations in our family. But, I was of draft age soon after the Berlin Wall was built. That and the threat of Castro’s Communist regime in Cuba escalated the Cold War and the struggle against the advance of Communism. When President Johnson and Secretary of Defense McNamara sent regular troops into South Vietnam, I was conscripted. I had just graduated from college, and was working for Univac Defense Sytems Division when my educational deferment expired. The draft board refused to grant an occupational deferment, especially since I was due to soon be deployed to Europe to install a Fleet Operations Control Center and draft-age men were already fleeing the country to avoid the draft.

I spent two years in the U.S. Army, the last year as a Physical Sciences Reseach Assistant, actually working as a Radio Frequency Interference Analyst, regulating radio spectrum usage at White Sands Missile Range, New Mexico. This was primarily an electrical engineering job, for which the Army had no training programs, but assigned personnel qualified by civilian training or experience. The assignment came just in time to rescind orders that would have sent me to the jungles of ‘Nam. An alert personnel clerk at Fort Gordon, Georgia culled many college graduates from the infantry ranks and placed them in such jobs.

H. Gale Hungate, Area Frequency Coordinator, WSMR, hands a Certificate of Appreciation to Specialist 4th Class L. Parkins on completion of his tour of duty. 1967

The Vietnam War dragged on for another five years, during which it was best not to mention having served, nor for a long time after the unpopular war was over. I went back to the military-industrial complex and continued my career as a Cold War mercenary for another 30 years.  I was involved in developing major naval combat systems, both tactical and strategic, and occasionally went to sea as a civilian technical consultant, a non-combatant, necessary to the crafting of complex systems, but reviled as a war profiteer, even though many of my uniformed collegues earned as much or more.  The difference being that, as a civilian, I would not be required to stand in harm’s way should the occasion arise, though I did once, during the Viet Nam conflict, carry identification to be used in the event of capture by opposing forces.  My status as a veteran did not stand in good stead in the company of active duty personnel, nor in the community at large.  This much we have lost in pursuing unpopular wars.  Only in Native American society today are warriors, past and present, revered, respected, and honored.

In due time, the next generation after me grew to manhood in relatively peaceful times. The oldest boy, stepson Matt Bock, joined the Army Reserve between his junior and senior years in high school and, after a year of deciding he wasn’t ready for college, went active duty. He was in Germany as a communications specialist when the Berlin Wall, erected a generation before, fell, and remained there through the First Gulf War, then called Desert Storm, that evicted Iraqi forces from the disputed independent state of Kuwait.

Matt’s brother, Mark, secured an ROTC scholarship to enable him to attend private university, and, after graduation, accepted a 4-year commission in the U.S. Army Tank Corps, spending most of his tour of duty in Colorado, with a brief deployment to Saudi Arabia during the uneasy peace between Desert Storm and Enduring Freedom, the ill-conceived Iraqi regime change that has, along with the drawn-out Afghani campaign, the longest war in American history.

So far, these 21st-century conflicts have endured without conscription, placing an awful burden on the diminished volunteer services, but leaving the next generation of our family, the fifth since fleeing Prussian conscription in the 19th century, and sixth since the casualty of the War Between the States, with a choice. Of the two girls and one boy currently of military age, and two more boys in high school, none have indicated a desire to serve.

We are proud to have served, and proud of those who served before us and who now serve in the defense of their country and common ideals. But, mindful of the sacrifices of those who did not return and those who, shattered in mind and body, cannot be made whole, we would rather that none of our future descendents need make the choice to go to war nor have that choice made for them.

Chaos Central version 2.0

As we start our second year in residence at Chaos Central, it is only fitting that we roll out version 2.0.  For most of the past year, we have run our respective businesses out of a three-generation household, sharing the house with our son and his family after our daughter-in-law, a local government professional, took a new job 20 miles away–and 80 miles from their former home.  Our son, a civil engineer who telecommutes part of the time to his job midway between the old and new locations, took over the main office; our two grandsons, ages 7 and 2, took over most of the living room and a substantial chunk of the longarm quilting studio, which became a Lego design studio.  Of course, the extra family filled two of the remaining bedrooms (leaving a guest room for the other grandparents); the kitchen ran in a three-section duty roster cycle, with separate meals prepared for children (unseasoned past and meat), parents (high-protein macrobiotics and spicy meals), and grandparents (vegetarian); and, the butler’s pantry/laundry/espresso bar ran pretty much continuously.

We arrived back from a business trip  to Montana at the end of October to an almost-empty house, our first night back home coinciding with the children’s first night in their new home, after a long search and even longer building cycle.  We celebrated by helping the grandsons assemble their beds and shuffle furniture the next morning while their parents retrieved more belongings from storage, then returned to Chaos Central to transform it into the fiber arts and software studio we had imagined.

First, without tubs of toys, the front room transformed into a welcoming reception area, which still needs a few lamps and occasional tables to round out the space.  The dining room got more spacious with the removal of two leaves from the table.

The reception area, with "adult" furniture, sans toy boxes and TV

We had started reclaiming the office earlier, anticipating the imminent move with the installation of our new XenServer. Since our return, the Unix Curmudgeon’s trusty Ubuntu Linux laptop has been set up on the conference table, with dual monitors. The XenServer console, a Windows XP machine (our one and only concession to the Redmond Menace), is essentially reduced to a VNC terminal for the many Linux/BSD images residing on the virtualization host.

The office reverts to a software development center
Getting ready access to the bookshelves and laser printers is great.

Of course, the real transformation is in the Nice Person’s fiber and fabric arts studio, now that she is rid of the Unix Curmudgeon’s temporary office mess in the midst of her looms. In fact, the fiber business has expanded to four rooms: the longarm quilting studio, the weaving/sewing room and office/library, a spinning and weaving room, and beading and weaving space in one of the guest rooms.

The quilting studio, now with cutting/ironing station replacing the grandchildren's Lego studio.
The weaving/sewing studio, with fabric stash and Oregon floor loom
The office/library area, with yarn stash and 8-harness table loom replacing the Unix Curmudgeon's former temporary office; the fabric arts office area is to the right.
The spinning/weaving studio, with Gilmore floor loom. This is also the "Music Room" and overflow guest space with inflatable mattress.
The 4-harness table loom in the "Bicycle Room" guest bedroom
A view of the "Bicycle Room" guest quarters. The quilt is a blooming 9-patch in Kaffe Fassett fabrics.
The original guest room, on the first floor, with a Thimbleberries sampler and the "cat quilt."
Of course, the downstairs guest room is known as the "Sewing Room," for the 1888 Domestic treadle machine.

So it goes. We’ve recovered our house and are transforming our workspaces for productivity. The lesson is this: family life and business don’t always mix well. Working from home when home consists of an active family life with small children is, by necessity, a stop-gap measure that involves some sacrifices. Prior to last year, we had been empty-nesters for over 15 years, and sharing space with college students is a lot different than sharing space with toddlers and grade-schoolers.

But, at the same time as we are setting up dedicated studio space, we are finding ourselves more mobile: the laptop computer is still the key to the software and systems consulting business; and the portable table-top looms, compact spinning wheel, sewing machine carry cases, and project portfolio boxes are essential to the fiber and fabric business.  Even without full-time multi-generational occupation, Chaos Central, true to its name, remains a flurry of seemingly disjointed, divergent activities on many fronts.

Life on the Road–Making Do

We’re on the road again–actually just back in the old Montana haunts, but without the amenities of home.  The Unix Curmudgeon is holding court with his laptop on a cardboard box on a filing cabinet, to align the screen with a second monitor provided by $CLIENT, along with a wireless mouse and keyboard also on loan.  So, this setup is not dissimilar to the temporary office at Chaos Central.

The Nice Person is making do with her netbook at the local public library and coffee shops.  We recently upgraded our eight-year-old copy of Quicken, for various reasons, most having to do with bit-rot and missing features not supported by Wine on Linux.  So, our financial records now reside in an XP virtual machine on the big Linux workstation back home.  We can connect with it remotely if we have to, but that’s never fun with slow wireless connections and limited screen sizes on the mobile devices.

This trip is a more or less extended contract work session, originally intended to keep level of coverage for on-site staff vacation replacement, but the current workload deferred the absences.  Nevertheless, there is enough excitement to keep busy, which is why we’re on retainer in the first place.  Being on-site for an extended period is much different than the focussed effort of per-incident billing that is the norm for this sort of consulting, but immersion in the day-to-day system activities also results in a big-picture view that justifies the extra expense.

Meanwhile, the Nice Person has planned activities as well, that are less focussed.  The inconvenience of not having access to the comforts of home require some workarounds.  Like the Curmudgeon’s makeshift workstation arrangement, she has been sewing in the empty ex-home, on a rickety occasional table, sitting on a rickety chair, but finds the bare carpet convenient for quilt-top layouts.  However, like the coffee-shop forays for Internet access, she relies on the local quilt shop classroom to do cutting and ironing.  Last week, she attended a quilt retreat with the old gang, and we’ve had a bit of time to visit with other folks we know, so it’s almost like a normal existence, if a little sparse.  Our mornings are spent sitting in the living room on lawn chairs, drinking instant coffee, but even that has some ambiance compared with spending mornings hiding in the fiber studio at Chaos Central waiting for the kitchen chaos to subside when the children get the grandchildren off to school.

Thanks to electronic billing and banking, the bills don’t pile up while we’re gone, but the fact remains that all of the places we call home need personal attention from time to time.  We left Chaos Central at the mercy of the ever-encroaching English Ivy, against which we have been waging a losing battle.  One weekend in Montana was spent removing walls and shelving in the garage to convert the craft workspaces back to potential parking area, in hopes of attracting buyers who expect a garage to be a garage, and another weekend in winterizing and continuing the on-going maintenance and construction in the off-the-grid cabin formerly known as the Y2K Bunker, 200km to the north.  The war against spotted knapweed around the cabin has been set back this year, as well.  We’re beginning to realize that, in the dozen years since we started building the cabin, our average length of stay there is 20 hours, at infrequent intervals, so it remains a work in progress.

So it goes: it’s not retirement, it’s a return to the road warrior days, before Unix, living out of a suitcase and indulging in portable hobbies to keep some semblance of stability and continuity to working everywhere and nowhere in particular.  We can see why a lot of folks encumber themselves with motor homes in later life, forsaking the garden, orchard, and porch of a permanent dwelling for the freedom to be where you need (or want) to be.  But, that’s not for us: not all of our activities are that portable, and we like our porch.  Besides, total mobility depends on the ability to shed some of those real-estate commitments.  Meanwhile, it’s getting close to time to head back to Chaos Central to collect the cat from the Kitty Hotel and see if the children and grandchildren (who moved in 10 months ago) have moved away yet…

Practice Makes Perfect

The “10,000-hour rule” was coined by psychologist Anders Ericsson in reference to violinists, but popularized by author Malcom Gladwell to be more inclusive.  The rule states, essentially, that mastery of a given field requires about 10,000 hours of dedicated practice.  For musicians, this is certainly true, given the time it takes to understand the nuances of one’s finely tuned instrument, plus commit difficult passages to muscle memory and to correctly interpret the composer’s auditory vision of the score.

But, what of other professions and activities?  What constitutes dedicated practice in other fields?  The 10,000-hour goal in the world of work is about five years of 8-hour workdays.  In most professions, five years is the entry-level experience for a “senior-level” position, what I would call “journeyman-level” in a skilled trade: someone who can handle routine tasks without supervision or guidance.  The next level of performance is measured at the eight or ten-year experience level, given that probably a third to half of the average work-day is given over to socialization and the business of doing business, during which we are not practicing the skills of our trade.

For the profession of system administration and similar technology pursuits, the 10,000-hour rule is even harder to judge, since mastery of the art is a moving target.  I personally have almost 30,000 hours of paid work as a systems administrator, of which we can apply about half, or 15,000 hours, to “practice,”  plus a few thousand hours of actual practice and study specific to the skill, prior to and outside of “on-the-job” time.  Any muscle memory part of the skill set is in keyboarding, which carries through, and the Unix philosophy set down by Thompson and Ritchie in the early 1970s remains to be thoroughly understood and practiced.  The analogy to music further maps the idea of mastering a composer’s body of work to mastering the various “flavors” of Unix: Solaris, BSD, SVR4, AIX, HP-UX, and, of course, the varied Linux distros.

This analogy breaks down when we consider that the body of work refuses to stay static: Unix is a constant sequence of variations in the form of upgrades, after which the original is never performed again.  Software and hardware are intertwined, where older editions of systems software can only be performed on obsolete and non-repairable hardware (though emulation can eliminate that obstacle), as if a particular work of music could only be performed on a single, fragile instrument.  So, mastery of systems administration is a dynamic process: virtuosity requires constantly learning new works (software) played on new instruments (hardware systems).  I don’t think 15,000 hours constitutes mastery of the art, divided as it is between several major versions, and with time split between straight system administration and programming, in an ever-changing environment.

Yet, mastery requires practice, meaning exercises in the fundamentals: in music, scales and fingering exercises; in systems administration, scripting, building kernels and applications from source, and testing.  These activities are the muscle memory of system administration, the automatic responses that facilitate solving difficult problems that require planning and reading the manual–the ability to apply resolution promptly and with skill.

Which comes to  the other side of expertise: in order to master a given skill requires physical stamina and flexibility, as well as a clear mind.  For the past 33 years or so, my outlet to balance the rather sedentary computing life has been bicycling.  Now, masters of the art like professional bike racers and world-class bike tourists accumulate 10,000 hours of practice within five to ten years.  As a bike commuter and accidental bike tourist, a mere 50,000 miles–my estimated lifetime accumulation at present–at perhaps an average speed of 14 miles per hour,  constitutes only about 3500 hours of practice, far short of mastery of the skill.  Worse yet, the past year has seen the end of bike commuting, since I now run my professional practice from home.  Now, I should be able to take my former commute time and recreational biking time and use it for practice, but the incentive just isn’t there.  Until one realizes that, like system administration or music, regular practice is essential not only to achieving mastery, but to maintaining a reasonable level of competence.

A bit over six years ago, I was inspired by a true master of the sport, Shirley Braxton, who, with her late husband Sam, had owned a bike shop in Missoula, Montana, and, in the 1970s, did much to start the bicycle touring industry by building bikes designed for loaded touring.  Shirley, then in her late 70s,  made a practice of capping the bicycling season with a “birthday ride,” of length in miles equal to her age in years.  For a few years, this was motivation enough to get out and train through the summer, building up to an early fall 60-odd-mile ride, even to the point of participating, as a training ride, in three MS Tours, a fund-raising ride to benefit Multiple Sclerosis–originally a 150-mile ride in two 75-mile stages, but, because of popular support from relatively new cyclists, has for a number of years offered 50-mile stages, which course we prudently chose.  As with any pursuit of mastery of a skill, the tools and instruments are also important to achieving the goal.  In our case [meaning, of course, the Nice Person and the Unix Curmudgeon], we ride a mountain-style tandem, which, like it’s single-seat relative, has a heavy frame and oversized tires, intended for trail riding rather than racing or touring, though we have toured with the tandem (see the other blog articles in our bicycling category). In any case, swift passage and high mileage are not the strong suits of such machines, though they generally come with very low gearing that compensates on hills.  Or so we tell ourselves.

So, with advancing age, both myself and my ride–a 1996 Specialized Hard Rock, entry-level commuter/mountain bike, with fat tires, steel frame, and no suspension–together we’ve tackled the “birthday ride” solo for the past three years, the Nice Person having come to her senses about the effects of inadequate training, leaving the Unix Curmudgeon to huff and puff his way alone through what became the longest rides of the seasons by double.  Without benefit of daily sprints across town to work, and with the last ride a month ago, setting out into the foothills of the Olympic Peninsula on a nearly 70-mile course was less a demonstration of ability and skill than a simple grueling test of endurance.  But, some of the lessons of nearly 35 years of all-weather commuting and touring held forth:  keep hydrated, keep fueled, put on rain gear when it starts raining, stow it when it stops to avoid overheating, don’t push too hard early on, and get off the bike for at least a few minutes every hour to eat, drink, and rest the legs a bit.  Oh, yes, the thought of aborting the mission did occur, once or twice, but we can report mission accomplished: 69 miles in 7 hours 52 minutes, an average speed of 8 and 3/4 miles per hour, including pit stops.  That’s just about the daily limit for a mountain bike, and one of the reasons we declined the 75-mile route on the MS Tours–there was an 8-hour time limit on that course, and it is important to finish.  Reasonable goal-setting is also a part of developing mastery of a skill.

Next year, the goal is to ride often and ride long, work on a more balanced fitness regimen, lose a bit of weight, and get a lighter, faster bike.  The rest of this year, the goal is to work more with server virtualization, hierarchical storage management, and keep up with the latest systems releases, on the work side.  Practice, practice, practice.  No matter how old you get, there is still more to learn, and roads to explore, perhaps at a more leisurely pace.

Musings on Unix, Bicycling, Quilting, Weaving, Old Houses, and other diversions

%d bloggers like this: