Road Trip 2016

When we set out on Expedition 2016 in March, we thought that the planned 4-month, 5000km bicycle adventure would be the ultimate trip for 2016, after which we would settle down and be “normal” retirees, puttering around the house, painting woodwork and shoveling out 50 years of hoarding journals, books, and hobby news.

Well, the grand expedition turned out to be only two months, most of it in a rental car rather than on the bicycle, (600km of cycling taxed our limitations).  We did see most of the planned sites in the U.S., plus a few more, the result of turning west at the Delaware Water Gap instead of continuing into New England and Eastern Canada.  We’ll save those for next year, with a different venue.

So, after arriving home in mid-May, we quickly planned more trips: a camping trip to the beach with cycling; participation in the 30th anniversary NorthWest Tandem Rally in  Klamath Falls, OR, and contemplating signing up again for a Pedal Across Wisconsin bicycle tour, this time of Door County.  We had made a down payment in 2014 for their North Woods tour, but had to cancel because of a training issue that turned out to be cardiac artery disease.  But, after thinking it over, we did something different: we are seasoned self-supported tourists and had, in 2015, gone on a successful car-bike tour of selected trails, which seems to be the preferred mode of touring for us elderly folks.  We also wanted to encourage non-local grandchildren to visit us for a change, so we hatched the plan for Road Trip 2016.

Fuel stop at a one-pump farm co-op in Rudyard, Montana, on the way home.
Fuel stop at a one-pump farm co-op in Rudyard, Montana, on the way home.

First, we made reservations at an available resort 80 km south of Sturgeon Bay, the gateway to Door County, for a week before the PAWs commercial tour (so as to not be inundated on the road with their clients and competing for attractions with 50-75 other riders).  We then convinced our grandson in Madison, Wisconsin that he needed to visit the west coast,  The plan was that he would fly out to Seattle, spend a week or so, then we would drive back to Wisconsin, stopping at tourist attractions along the way.

2016-08-19-16-50-46The plan got underway, with a trip to the Pacific Ocean beach, near where we had camped earlier, so we were familiar with the territory and things to do and see; a visit with his cousins in Olympia, and culminating with a tour of Seattle Center and the iconic Space Needle.  Then, off across the country, oblivious to the fact that we hadn’t done a major road trip with teenagers for over 35 years.

cjroadtrip2016The first few days went well, with stops at Multnomah Falls, a natural ice cave and the Craters of the Moon volcanic monument in Idaho, the Museum of the Rockies (Dinosaurs!) in Bozeman, and Custer Battlefield.  We stayed mostly at motels with indoor pools, giving the young man a few hours to work off the ennui generated from being trapped in the cramped back seat while endless bleakness crawled by and cellular data waxed and waned and then disappeared altogether in the desolation that is northeastern Wyoming.  About then, his computer crashed, a broken display cable.  The adventure became akin to traveling to the space station in a cramped Soyuz capsule following launch in a less-efficient orbital transfer path.  He curled up in the small space and we didn’t hear much the rest of the trip.

2016-08-27-16-27-21A stop at Crazy Horse Monument was of interest–a massive sculpture started in his grandparents’ childhood and which will likely not be finished before he is a very old man.  Mount Rushmore, with four presidents squeezed into a smaller mountaintop, was less impressive, even after dragging his grandparents up the hundreds of stairs to the viewpoint below the faces.

Corn Palace, Mitchell, SD: 2016 theme: Rock & Roll Hall of Fame
Corn Palace, Mitchell, SD: 2016 theme: Rock & Roll Hall of Fame

We retaliated by taking a tour of the Corn Palace, where this year’s theme, massive portraits of rock and roll legends from our youth, was realized in mosaics of ears of corn, covering the exterior of the huge auditorium.  We followed up by a walk-through at closing time of Arnold’s Park, a century-old amusement park in northern Iowa where I spent my teen-aged years watching people with money spending theirs on a good time, like riding the rickety wooden roller coaster, which horrified the grandchild raised in a more safety-conscious age.  The roller coaster was still running, held up by new, as yet unpainted, spindly sticks here and there.  Like 60 years ago, we just watched, then moved on.

Across Iowa, we stopped (more of a “drive-by howdy” than a stop) at our daughter’s tiny goat farm on the outskirts of “Brick City,” to be nibbled by the goats and pat the heads of Drake and Moose, the huge house dogs.  Apprehensive at first, our young charge soon felt at home with his newly-found relatives (but not necessarily with the goats). We soon moved on, back to the more familiar Wisconsin and home.

Viewpoint at Inspiration Point in the Arcadia Dunes area on the eastern shore of Lake Michigan.

Shed of our grand-parental responsibilities, we headed for Milwaukee, then followed the lake shore through Chicago and the Indiana dunes,  up the eastern shore through Michigan, along scenic roads we hadn’t ridden on our 2013 bicycle tour.

Mackinac Island 2016 from Larye Parkins on Vimeo.

A return trip to Mackinac Island: this time,we rode the perimeter of the island, in both directions, and explored some of the interior roads. The afternoon crowds brought many amateur bicyclists, creating a bit of a hazard to navigation.

At Mackinaw City, we unlimbered our bug-encrusted bike from the top of the car and spent most of a day touring Mackinac Island, a bit more leisurely and thoroughly than we had time for in ’13.  With a bit more time to sight-see this year, we wandered over to the Painted Cliffs along the south shore of Lake Superior, working our way back east to Sault Ste. Marie.

Castle Rock, on Lake Superior's Painted Cliffs
Castle Rock, on Lake Superior’s Painted Cliffs

In the morning, we watched an ore boat work its way through the locks–through the fence, as the facility didn’t open to visitors until late morning, by which time we were headed south, covering in a few hours what had taken us six days on the bicycle, to spend a week exploring the Wisconsin shore of Lake Michigan.  On the way, we took a side trip from Sault Ste. Marie to Whitefish Point, where the museum features the story of the Edmund Fitzgerald, ore-carrier that sank with all hands in a November 1975 storm.

Mariners Trail from Larye Parkins on Vimeo.

The first day on the Wisconsin coast, we took the bicycle down the Mariner’s Trail from Two Rivers to Manitowoc, realizing as we came upon the USS Cobia (SS-245), docked in the river next to the Wisconsin Maritime Museum, that this is where 28 Gato-class submarines were built in WWII.  Later in the week, we returned by car to tour the well-preserved submarine and the museum.  The next day, we did a recon of Door County,  Sturgeon Bay to Egg Harbor seemed a good bike route, but the northern end of the peninsula is quite hilly. On the way back, we got buffeted by heavy rain, so were glad we hadn’t chosen to ride this day.

Spaceship 1, the first non-government spacecraft to reach 100km altitude, and which won the X-Prize, 2004.
Spaceship 1, the first non-government spacecraft to reach 100km altitude, and which won the X-Prize, 2004.

Back at the resort, we planned our week around the weather forecast, which was punctuated with thunderstorm activity through the week.  A tour of the submarine and museum in Manitowoc was on the agenda, for a not-so-stormy day, as the submarine tours are cancelled on wet days.  We also took a rainy-day excursion over to Oshkosh to visit the Experimental Aircraft Association museum, which we hadn’t been to in fifteen years or so.  In midweek, the weather cleared over Door County, so we took the noon ferry to Washington Island for a bicycle ride around the island, lunch and the Island Cafe and gelato at the dairy and lavender farm.

Washington Island from Larye Parkins on Vimeo.

A brief (2-minute) tour of Washington Island, Door County, Wisconsin. The island is a quiet, gently rolling oasis a 30-minute ferry ride from the end of WI 42.

Finally, it was time to head for home, with an impromptu stop in Jefferson, Wisconsin for the regional fiber festival, where Judy bought yet another weaving shuttle from the Woolgathers, who made her portable box loom.  We stopped in Middleton to visit our son for a couple of days: the car requested an oil change, so we took advantage of the shop time to ride another trail, this one north along U.S. 12., conveniently near the auto dealer.  Another rainy day, we took a tour of Olbrich Botanical Gardens, between Madison and Monona.

The Thai Pavilion at Olbrich Botanical Gardens, Madison, WI
The Thai Pavilion at Olbrich Botanical Gardens, Madison, WI

As we made our way west, we drove up the Mississippi on the Wisconsin side, to La Crosse, and to Rushford, Minnesota, on the Root River Trail, for an evening bike ride on trail section we missed last year.  The next day, we drove across southern Minnesota, sticking to the county roads that follow the route of the old U.S. 16, avoiding I-90, which didn’t exist when I grew up in the area.  After arriving in the midst of a heavy thunderstorm, we met my aunt and cousin for dinner at the local V.F.W. post.

Return to Root River from Larye Parkins on Vimeo.

A return to the Root River Trail in southeastern Minnesota, to ride the Rushford-Peterson segment. This is an evening ride, with the sun low up the valley. At 30 sec, two deer bolt up the trail and into the brush on the right.

Early the next morning, we took the old U.S. 71 north, a route I traveled many times in my youth to visit relatives in central Minnesota. But, this time, our destination was to Judy’s cousin in Devils Lake, North Dakota, so we headed west on I-94, north on I-29, and finally west on U.S. 2,  After our visit, we continued west on U.S. 2 into Montana, leaving the Hi-Line at Browning for a quick tour through Glacier National Park, crossing east to west for the first time, and crossing the park completely for the first time since our bicycle tour in 1988.

Mission Valley, Montana
Mission Valley, Montana

We spent a few days visiting our nephew Rick in Polson–strange to be next door to the  land we had owned for more than 20 years: the tiny cabin we had built now belongs to a young couple who will be building a home in which to raise their family, with the cabin as a base and future guest quarters, as we had once hoped to do.

Lewiston, ID - Clarkston, WA, at the confluence of the Clearwater and Snake Rivers.
Lewiston, ID – Clarkston, WA, at the confluence of the Clearwater and Snake Rivers, with the old Spiral Highway up Lewiston Hill in the foreground..

A trip up the Bitterroot to see some of our many friends was the last diversion on our long road trip.  Turning westward, we chose to take U.S. 12 across Idaho, a pleasant, slow route with low traffic on a two-lane road.  We stopped in Kamiah, halfway across, a small (~1200 pop.) timber town on the Nez Perce reservation, where there was no cell phone service, making for a quiet, reflective evening, after dinner at a nearby tavern/restaurant/bowling alley.  Our route turned north at Lewiston, ID, then west at Colfax, WA.,  for a pleasant, low-traffic drive to relax us before enduring the rainy Snoqualmie Pass on I-90 and the creeping parking lots of WA 18 and I-5.  We exited the freeway on the outskirts of Olympia, preferring the city traffic to gridlock on the Interstate.

2016-09-23-17-42-23We made it through the city early enough to pick up Delia from Just Cats Hotel, so the family arrived home together after exactly a month away, all glad to be home.  Now we have two weeks to prepare for our next outing, to the apple country on Lake Chelan.

Road Trip 2016 Route — to explore in detail and see photos at the waypoints, click on

Warm Showers 2016, Part 2

This summer, the 40th Anniversary of the Adventure Cycling Association (nee BikeCentennial), has brought a surge of bicycle tourists.  No sooner had we clicked “Publish” on Part 1 of our guest gallery post that we got another round of requests.

Conor and Erin, former Peace Corps volunteers using a bike tour to settle into life back in the U.S. after 2-1/2 years in Tanzania.
Daniela and Christian, from Karlsruhe, Germany.

We had made plans to have our 14-year-old grandson visit us from Wisconsin in mid-August, after which we would drive him home and spend some time bicycling trails and back roads around Wisconsin and Michigan, for a second, gentler tour this year.

So, as of August 1, we put ourselves on the “not available for hosting” list with Warm Showers, having already accepted an advance request for the first week in August.  Another family from Germany, this time with two small adventurers in tow, 15 and 18 months old.  We’ve hosted babies and toddlers every couple of years or so, and the occasional dog who would rather ride bicycles than chase them.  The youngsters readily take to the traveling life, with the bicycle just another piece of furniture in their open-air home.

Stefanie and Ingitha, with their two toddlers in tow (behind Ingitha); Stefanie tows the supply trailer.
Stefanie and Ingitha, with their two toddlers in tow (behind Ingitha); Stefanie tows the supply trailer.
We keep a supply of toys left over from when our grandsons lived with us, to entertain our younger bicycle tourist guests.

Even though we were on the “not available” list, we got one more request, via a referral by an earlier guest. In the age of the Internet, the best way to plan a bicycle tour is to search for the stories of others who have gone before, in blogs, the “Crazy Guy on a Bike” journal, Facebook, Instagram, etc. Angela, corresponding with Nico, whom she had never met, got our name and contact information and called, having arrived in Shelton late in the day with no plans. Angela had met Mira, a Czech cyclist, earlier in the day. Of course, we took them in. Mira had a meeting set up in San Francisco, so forged on ahead after they reached Astoria, but we continue to track Angela on her journey as she overcomes hardships and meets new friends on the road, as we have many other guests over the past five years, now numbering over 150. And, now and then, we succumb to that urge for the open road and adventure at 10-15km/hr and set off on our own quest.

Angela, from Canada and Mira, from the Czech Republic, riding together for a few days on their separate tours.
Angela, from Canada and Mira, from the Czech Republic, riding together for a few days on their separate tours.  Angela was three days into her first long-distance tour, and Mira was finishing the last stage of a tour of the Americas that took him from Argentina to Los Angeles and Alaska to Washington, headed for San Francisco.

As I write this, we are in Wisconsin, having dropped off our grandson near Madison and circled Lake Michigan by car, taking time to ride when we can: a return to Mackinac Island in Lake Huron, riding a shoreline trail on the west shore of Lake Michigan, and riding around Washington Island, at the northern tip of Door County, Wisconsin, covering a bit less than 100km on the bike and over 5000km in the car.  The weather has been variable, with late summer thunderstorms dictating when and where we ride, making us glad we have the car to transport us between scenic trails, and to check out road and terrain conditions before we commit to a ride.

Beware the Wiley Hacker: a Cautionary Tale

Not an approved method of securing your network...
Not an approved method of securing your network…

A while back, we wrote about rebuilding a crashed Raspberry Pi system.  In the course of reinstalling the system (on a new chip–the old SD card that contains the operating system had “worn out”), we had made a fatal slip.  This system happens to be our gateway system, i.e., connected directly to the Internet to provide us access to our files and some web services while out of the office.  Unfortunately, this also provides the opportunity for the world-wide hacker community to try to break in.

Normally, we have safeguards in place, like restricting which network ports are open to the outside and which machines and accounts are allowed login access.  However, in our haste to get the new system up and running as quickly as possible, we connected the device to the Internet to download upgrades before the configuration was complete, meaning the system was exposed without full protection for several hours to several days.

Screenshot-larye@raspberrypi2: -var-log
One hour’s worth of break-in attempts by hackers. Note that attempts to access system accounts (root, pi) are denied because we don’t allow external logins for these accounts.  The accounts that are allowed are restricted to public-key authentication (basically, a 1700-character random password).  Attempts on this one-hour snapshot come from four different sources: Porto, Portugal; Shanghai and Baoding in China; and Tokyo, Japan (possibly hacked machine, as the name is spoofed).

Now, our security logs record, on a normal day, hundreds of break-in attempts (see screenshot above).  We aren’t the Democratic National Committee or Sony, just a small one-man semi-retired consulting business.  But, the hackers use automation: they don’t just seek out high-value targets, they scan the entire Internet, looking for any machine that isn’t fully protected.  If they can’t steal data or personal information, they will use your machine to hack other machines.  If you use Microsoft Windows, you are undoubtedly familiar with all sorts of malware, as there are many tens of thousands of viruses, trojan horses, adware, ransomware, and other malevolent software that invades, corrupts, and otherwise takes over or cripples your machine.  Unix systems are less susceptible to these common attacks, but, if an account can be compromised, or a bug in the login process exploited, eventually a persistent attacker can gain system privileges and install a ‘rootkit,’ a software package that replaces the common monitoring and logging software, redirecting calls through the rootkit, which hides its existence and activities from the reporting tools, even the directory listing utilities.

Once an attacker takes over a Unix or Linux machine, there is no limit to the damage they can do on the Internet, as Unix/Linux is the basis of most of the servers on the Internet, and can become as a SPAM server, web-spoofer, or hacker-bot itself.  (Microsoft Windows Server has the rest, nearly half, and they are even easier to break into.)  I began to suspect this might have happened when normal system functions failed to terminate or run correctly.  We have a lot of custom software built on this machine, which runs on a scheduler.  The machine got slower and slower, and it was apparent that the jobs run by the scheduler were never exiting, filling up the process table with jobs that weren’t doing anything, except taking up space, which is always at a premium.  Clearing out all the jobs, restarting the machine, and starting the processes manually worked–until about 2:00pm.  Very suspicious: a rootkit, once installed, can repair or re-install itself even if the administrator restores many of the co-opted command files by normal upgrades or by a conscious attempt to recover from the intrusion.

The main problem seemed to be with /bin/sh, the system shell, which is actually /bin/dash, a shared object.  Cron, the scheduler, uses dash to run the jobs, where the normal user login shell uses /bin/bash, a non-linkable executable shell with similar functionality.  A rootkit is generally constructed as a filter, wrapped around the co-opted commands, so it would be easier to link to the *real* /bin/dash in an undetectable manner from the filter program than it would to wrap /bin/bash.  In this case,  assuming an intrusion was the cause, something went wrong, rendering dash non-functional.  Perhaps the intrusion was not compiled for the ARM  processor used by Pi, though most of a rootkit would be scripted to be portable among different CPU architectures and Unix/Linux versions.

An analogy to the problem would be like finding out who let the horses out: it is easy to identify wolf or horse-thief tracks outside the barn when the door is barred, but, if you left it open and the horses have bolted, it is more difficult to find out what happened–the traces are covered. I did install some intrusion-detection software, but running it after the tracks are covered over is usual a futile effort.  However, there were enough questionable traces to warrant taking corrective action.  Besides, even if the problem had been caused by some inadvertent misconfiguration on my part (unlikely, considering the fact that the machine could be made to run for several hours before the problem reasserted itself), the solution was clear:  reinstall everything.

The first step is to backup the data, including configurations.  Now, this is not just an ordinary computer:  Raspbian, the Debian-based operating system distribution designed for the Raspberry Pi computer, comes with a simple desktop intended to introduce new users to Linux.  But, this machine doesn’t use the desktop and is not even connect to a monitor most of the time: it is an internet gateway, web server, and custom webcam driver, so has a lot of “extras,” both loaded from software repositories and written especially for this installation.  Backups are important, since much of the software only exists on this machine.  And, since we only have one camera, fail-over isn’t possible without physically moving the camera from one machine to another, not a trivial exercise, as the connection is on the motherboard rather than an external connector.

Now comes the glitch: Since the introduction of the Raspbian operating system, it has been based on Debian 7; but, since Debian 8 was recently released, a new version of Raspbian is also available.  So, the machine was rebuilt with Raspbian “Jessie”, replacing Raspbian “Wheezy” (the releases named after Toy Story characters rather than just the numbers–as with Apple OS/X, Debian releases tend to have names in addition to release numbers).  Installation on Raspberry Pi is not like other computers.  Since there is no external boot device, the operating system “live” image is loaded onto the SD card that serves as the boot device and operating system storage.  Initial configuration is best done without a network connection, since the startup password is preset and well-known.

So, avoiding that mistake (booting on a network with the default passwords, the single most preventable source of hacker intrusions), we booted with the network cable disconnected and a monitor and keyboard attached, changed the password and expanded the system to fill the SD card, set up the other user accounts, then shut down the system, removed the SD card, and mounted it on the backup server to finish transferring vital data, like the security keys and system security configurations.  In larger systems with a permanent internal boot drive, such “hacker-proof” installation is done on an isolated network, but, since the boot drive on a Pi is removable, it is easy enough to edit the configuration files on another system.

So, with the system fairly well hardened by securing the system accounts and user accounts, it was rebooted attached to the network and the system upgrades and extra software packages (like the web server) installed.  So far, so good.  But, since we upgraded the operating system, the server packages were also upgraded, most notably moving from the webserver, Apache, version 2.2 to version 2.4.  Apache has been the predominant web server software on the Internet for 20 years, so it is in a constant state of upgrade, for security and feature enhancements.  Between version 2.2 and 2.4, many changes to the structure of the configuration files  were made, so that not only did the site configuration need to be restored manually, but there was a fairly steep learning curve to identify the proper sequence and methodology by which to apply the changes.

Then, of course, were the additional Python modules needed to be installed to support the custom software, which involved downloading and compiling the latest versions of those, since Python 2 also upgraded from version 2.7.3 to 2.7.9 (we haven’t yet ported the applications to Python 3, which moved from version 3.2.3 to 3.4.2 between Debian 7 and Debian 8).  Finally, there were other tweaks, like comparing system configuration files to update group memberships for access to the camera hardware, loading the camera drivers, and setting file ownership and permissions for data and program files.

We could have saved most of this by sticking with Raspbian Wheezy, but eventually, support for older systems goes away, and the newer systems are usually more robust and faster: open source software evolves rapidly, with new minor releases every six months and new major releases every two years for most distributions, and an average life span of five years for maintenance of major releases and a year for minor releases.  As we said before, Linux is free, if your time is worth nothing.  The price of keeping current is constant maintenance.  Patch releases occur as they are available, with maintenance upgrades almost daily.

Finally, after a week of tweaking and fiddling, the webcam service is back up and running.  And, the security logs show break-in attempts every few minutes, from multiple sites all over the world (one from Portugal recently, others from unassigned addresses–ones with assigned addresses undoubtedly come from computers that have been compromised and used as hacking robots, as hackers don’t want to be traced back to their own computers, ever).

So, the moral of this post is:  don’t ever expose a stock, unmodified computer system directly on the Internet (which is difficult to do, when all upgrades, new software, etc is available only through download from the Internet–which should be accomplished only from behind a proven firewall).  But, you can set passwords and change system accounts before joining a network.  And, if your computer is hacked, take it to a professional, and don’t grumble about the cost or time it takes to restore it.  Pay for malware scanning software and keep your subscription up to date, as well as scheduling upgrades on a regular bases.  And, if you are a professional, don’t take shortcuts (i.e., install and configure off-net or behind a firewall), keep good backups, install intrusion-detection software early, and check for security upgrades daily.  Change the default passwords immediately, and create a new, weirdly named administrative user, and deny external logins for all administrative users.  Use two-factor authentication and public-key encryption on all authorized user accounts.  They are out there, and they are coming for your computer, even if you don’t have data worth stealing: they can use your computer to spread SPAM or steal data from someone else.

Warm Showers 2016, Part 1

Despite our absence on our own shortened “Beyond 70” tour mid-March through mid-May, 2016 brought a steady stream of Warm Showers guests. We had to turn down a few while we participated in the NorthWest Tandem Rally in Klamath Falls, Oregon over the July 4th week, and plan to take a short break at the end of July to get in some more cycling and camping before heading east at the end of August for an early September tour of Door County, Wisconsin. This entry covers the 39 guests we have had through 22 July (including Toph, the dog).

Cara came through in early March, headed south. With El Nino, the bicycle touring season in the Pacific Northwest is nearly year-around.
Carina and Mat, from the U.K., arrived in mid-May, traveling from south to north on the Pacific Coast.
Nico, from Iowa, traveling down the Pacific Coast at a more leisurely pace than most. As of this writing, he was in Los Angeles.
Mark and Seth also traveled down the Pacific Coast.
Simon, from Switzerland, was a “drop-in,” guided to our house from downtown by our neighbor after finding there were no campgrounds nearby. He was already a Warm Showers member, but hadn’t made firm plans for daily distance, counting on finding campgrounds near the end of the day. Simon was touring south on the Pacific Coast route.
Justin was riding north to British Columbia and points east, to the Great Divide Mountain Bike Route, having cycled from his home in mid-Texas to California and up the Sierra Crest route.
Betty and Robert, AirBnB hosts and new Warm Showers members from Vancouver, BC, were touring to San Francisco.
Lisa, headed north from Portland to tour the Canadian Rockies, crossing paths with Tony and his dog Toph, below.

During the busy part of the summer, we often get multiple requests for the same night. Sometimes the travelers are headed the same direction and may meet on the road, but sometimes they are headed in opposite directions, as were Lisa and Tony. Tony had rescheduled because of the medical emergency with Toph. We have plenty of room, with three guest rooms, large open porch, and large format leather furniture in the living room, having hosted seven once.

Tony, from southern California, was traveling the Pacific Coast route with his small dog, Toph. Our cat insists that dogs camp outside, so Tony and Toph pitched their tent on the porch.
Toph cut her feet on shells on a beach a few days before and the cuts got infected, so she got the dreaded cone the day before she and Tony arrived.
Brian and Heather, finishing a loop around the Olympic Peninsula.

Shelton is a nexus for several popular routes: The most used is the Pacific Coast Route, with riders chosing the ACA route between Bremerton and Elma, or riding down U.S. 101 from either Port Townsend or Port Angeles. Some choose to take a short cut to Centralia via Olympia (or around Olympia on Delphi Road, skirting the Capitol Forest), and some head west from Elma for a more direct route via U.S. 101 and the 6800-meter-long Megler-Astoria Bridge across the Columbia River. Some extend to the Washington coast at Westport. The Olympic Peninsula Loop is also popular, but most riders continue south along the coast from Aberdeen, so bypass us entirely. Some riders starting or ending in Seattle also choose to follow the route of the Seattle-To-Portland ride, east of Puget Sound, and also bypass Shelton. This year, we’ve gotten riders who have ridden the Sierra Crest Trail through California and Oregon and continue on the Pacific Coast Route to Vancouver. We also have gotten, from time to time, Trans-Am riders who head up the coast from Newport, Oregon to Seattle to fly home.

And, there are some riders who are in the middle of a Grand Tour, either from Alaska or the Yukon Territory to South America or a loop tour of the U.S., via the Southern Tier, Pacific Coast or Sierra Crest, and Northern Tier. And, of course, riders to and from Portland, Oregon, the undisputed bicycle capital of the West Coast. Not everyone stops in Shelton: we see a lot of riders throughout the day, passing through, and some who stop at motels, the other Warm Showers host on the north side of town, or Couch Surfing hosts.

Glenn and Bobbie had ridden across the Southern Tier from Florida to California and up the Sierra Crest Route, headed for the San Juan islands.

Another night with two groups: Veteran tourists Glenn and Bobbie, finishing their tour at Anacortes, while Jason and Amy, below, first-time tourists, were just starting a cross-country tour. Conversation is interesting when comparing notes. From our own experience touring the Canadian Rockies 28 years ago, much of the fun is meeting and sharing stories with other tourists on the road.

Jason and Amy were headed north from Portland to Anacortes to join friends on the Northern Tier route to the East Coast.
Ana, a graduate student at UBC in Vancouver, BC, was taking a summer break from her studies to ride the northern half of the Pacific Coast route.
Mark finished the Trans-Am route from Virginia to Oregon and intended to take a break from cycling to hike in Colorado before heading back east on the Northern Tier route. He stayed a couple of days to recover from a bout of food poisoning, a risk when food stops are sometimes limited to convenience stores.

After Mark headed north toward Seattle, we clamped our Bike Friday tandem on top of the car and headed down the Oregon Coast, following the route of many of our guests. We spent the night at an AirB&B near Seal Rock, a nice couple who recommended a gastrobpub nearby and fed us a nice breakfast. We then drove to Eugene to augment our Bike Friday accessories and ride the wonderful trails, staying at an AirB&B downtown across from a brewery and pub. After another stop in Rogue River to visit relatives, we spent several days at Klamath Falls, along with 650 other tandem riders, for the 30th Anniversary Northwest Tandem Rally. Then, we headed north, following the Sierra Crest Route to Bend, then over the Cascades to camp at the beautiful Silver Falls State Park, hiking to several of the breathtaking waterfalls.

Judy with Julia, Christina, and Dana, friends from Ottawa, Canada cycling from Vancouver to San Francisco.

While camping in Oregon, we got several Warm Showers requests, which we regretfully had to decline. But we would be home in time to receive Christina and her friends. Knowing we were arriving from our own trip at about the same time, they graciously offered to bring and cook dinner. What a fun evening, and it gave us time to unpack before they arrived.

Hugh (right) and Liam, a father-son team cycling the Pacific Coast route from their home in North Vancouver, BC.
Chris, from southern California, cycling back home from Vancouver, BC. Chris’ arrival got delayed a day to ship his front rack and panniers home to lighten the load on the hills ahead, on his first self-supported tour.
Jamine, Taylor, Mia, and Nicole, housemates from Portland on a tour to Bellingham.
Jacy and Tom, on the last day of their tour from New York to Virginia to Oregon to Seattle.
Ryan, from Philadelphia, on tour on the Pacific Coast, starting from Vancouver.

Jacy, Tom, and Ryan arrived about the same time, from different directions, and at different ends of their tours. It was interesting to see the contrast between seasoned tourists about to finish a long tour and someone just starting out. Many of our travelers start in Vancouver or Seattle, on their first long tour, and are just finding their limits, so they arrive in that period of doubt about the feasibility of continuing on, whether the destination is 200, 2,000 or 20,000 kilometers away. This year, the 40th anniversary of the Trans-Am tour and founding of the Adventure Cycling Association, has seen more riders finishing that tour with a final week-long dash from Newport, Oregon to Seattle, as well as riders following the warm weather north on the relatively new Sierra Crest route.

Ludo, Pierre, and Phillip, friends from Montreal, cycling from the Pacific Coast. They intended to start in Seattle, but had to switch plans to start in Vancouver, so rescheduled to arrive three days later than planned.

Seasoned tourists Pierre and Ludo, knowing how hard it is to fill up hungry cyclists, supplemented our pizza and salad offering with a pound of spaghetti, with pesto sauce, and also broke out packets of oatmeal in the morning to supplement our bagel/cold cereal/fruit. buffet

Genie and Lydia, a mother-daughter team on the last day of their tour. Lydia started her tour in Paraguay 19 months ago, and Genie joined her in Los Angeles for the trip north, riding the Sierra Crest to Yosemite, and the Pacific Coast the rest of the way, ending in Seattle.

Genie and Lydia had arranged to meet Brad, a cycle tourist they met in the Sierras, who lives in Puyallup, for dinner, so invited us along as well. A fun evening, at a local BBQ restaurant we hadn’t been to before, being vegetarian. However, we found lots of good items on the menu with meat optional.

As has been our custom, we publish two lists of Warm Showers guests, divided at mid-summer or before and after our own tour, typically in late summer. This year, we changed tour plans in mid-tour, breaking up what was to be a four-month expedition into a series of short tours and weekend cycle/camping outings. We’re probably going to be unavailable most of the rest of the summer now, with our own travel schedules, but will, no doubt, take in tourists when we are home for more than a few days.

And Now, a Word From Our Sponsor…

The new, $9 CHIP computer, which comes complete with WiFi and installed Linux OS (mouse, keyboard, power supply, and monitor not included, of course): running “headless” as just another network appliance, along with the five nearly as small Raspberry Pi computers and numerous virtual machines.

The last few months, our articles have focused on our bicycle adventures, notably, the preparation for, launch of, and, ultimately, termination of our planned four-month expedition from Florida up the east coast.  We arrived home just less than two months after departing, and just in time to perform some much-needed maintenance on the Chaos Central computer network.

As the title of this blog indicates, we have, for the last 25 years or so, depended on Unix, Solaris, and Linux for both our livelihood and, of course, to operate our in-house network.  The majority of our systems run GNU/Linux, in various distributions: Ubuntu and Mint Linux on desktops and laptops, CentOS on the server and virtual machines, and Raspian on the collection of Raspberry Pi micro-machines (and the above CHIP nano-computer) that are rapidly becoming the backbone of the home network.

GNU/Linux is very stable: we have, in the past, run systems for up to two years without a reboot–and then only because we suffered a major power outage.  But, with a collection of systems, something is bound to go wrong.  First, less than a month after we left on our trip, a power surge that made it through the power conditioner/battery on the server took out the virtual machine that renders the timelapse videos from our driveway surveillance system.  We actually didn’t notice this until I went to review the current day’s timelapse progress and found the video was an hour out of date.  Ah, this was because I had programmed a failover plan into the system: the videos were now being rendered by the Raspberry Pi cluster in the basement, much, much more slowly on a 32-bit ARM single-core processor with 512 MB RAM than on the Intel Xeon quad-core processor with 8GB RAM in the virtual machine host.

The server rebooted without incident when we got home: it actually didn’t reboot when the power hit came, but had an error that locked up the processor, an unusual condition.  Had we not been headed for home at the time we discovered it, we could have instructed our house-sitter in how to cycle power and bring up the system.

Then, a couple of weeks after we returned, the surveillance system, which is also the remote login gateway, simply stopped, which would have been a show-stopper had we not been at home.0  We happened to have a spare Raspberry Pi, one that had seen duty as a print server and scanner server before we got a new WiFi-enabled printer/scanner.  It took a couple of hours to add the necessary software packages to run the camera and web server and configure the machine to perform all of the necessary duties of the old one, including limiting access to specific machines and login accounts, and we were back in business–for a while.  A few days later, the external disk drive that we use to store the camera output had an unrecoverable error.  The files affected could not be erased due to the error, but renaming the folder and creating a new one kept the system running until we could get a new disk and copy the rest of the files onto it.  The old disk had been re-purposed from use as a portable backup for travel, and is about six years old, so it’s time to replace it, anyway.

After taking care of the disk issues, I revisited the Raspberry Pi failure: it turned out that the SD card that the Pi uses as the internal system drive had simply expired of  natural causes.  SD flash memory chips have a finite lifetime, and can be rewritten only so many times before becoming useless.  The culprit here was the surveillance system software (which I wrote, so I only have myself to blame)–even though the camera photos, taken every 10 seconds, are written to the external hard drive, my program copied the latest one to the system disk, in the web space.  Every 10 seconds, 8 to 18 hours a day, for a year and a half. That’s about 2 million writes, all in the same location, in addition to logging system activity.   So, a simple fix to preserve the new system: put the web file on the external drive.

The discovery of the worn-out SD card meant that the old Raspberry Pi was still OK, it just needed a new system drive.  About this time, I replaced my 3-year-old Android phone with an iPhone.  I had installed an SD card in the old phone for photos, so I removed that, backed up the files, reformatted it, and built a new Raspian “Jessie” operating system on it (the rest run the older “Wheezy” version), and booted up the once-dead Pi.  Yeah!

This uses up nearly the last of the 8GB cards around the house, though I still have a 2GB card in an old Kodak camera that I use to document our Warm Showers bicycle visits.  We have a few 16GB cards yet:  the smallest cards on the general market (Costco, Best Buy, etc) are 32GB.  I have one 64GB card, installed in a GoPro camera, which required installing an additional set of packages to handle the exFAT (no, not skinny: it’s an acronym for EXtended File Allocation Table) file system when copying files to Linux systems.  New purchases tend to be the micro-SD footprint, since most new devices, plus phones and POV cameras, take those, and the older devices use adapters that are supplied (for now) in the package.  Speed is important for high-resolution cameras and video devices.  But, when cost is a factor, we still look for the lowest capacity and speed, as older devices have a size limit, and won’t operate with the new cards.  In the age of mass-production, the devices themselves become obsolete while still functional because the supply of suitable storage media dries up.

So it goes–it has been said that Linux is free, but only if your time is worth nothing.  It takes a lot of time to build a custom system, but the flexibility is enormous.  Each machine takes on a personality of its own, as it develops different capabilities, selecting from among the many different distributions available and the thousands of software packages downloadable for free in addition to the basic system.  Plus, the machines acquire a collection of custom scripts over time, that don’t exist anywhere else.  As a software and web developer, having instant and free access to database engines, web servers, and many different programming systems is priceless.

When I need to run several different software systems or distributions, I can use virtual machines, running all versions at the same time, on the same physical machine.  And, there are choices, with no buyer’s remorse penalties with free software. I’ve tried three different non-linear video editors, and stick with an older version of one (the new version isn’t compatible with the old project files…).  The stock desktop systems come with web browsers and office productivity software, and several different graphical desktop systems, which can be chosen at login time.

The latest addition to our Linux/Unix obsession is the CHIP computer, by Next Thing, which I pre-ordered for $8 back in January and which arrived direct from the factory (in China) a couple of days ago.  The CHIP is a bit smaller than the Rpi, with no HDMI (TV output), only one USB port, but a built-in 4GB flash drive, WiFi, and Bluetooth, which are all not included in the Rpi.  The CHIP is low-power, has a battery connector (3.7v rechargeable battery not included), and can be  programmed via the micro-USB power cable if connected to a laptop.  This device is more suitable to mobile (read: robotic) applications, as, like the Pi, also includes a number of digital/analog input/output circuits.  And, being a full-featured Linux computer, is more versatile than the Arduino micro-controller popular for hobby embedded applications.   Unlike tablets and phones, which are powerful miniature computers in their own right, and microcontroller-based devices like thermostats and security systems, these small experimenter’s devices are completely programmable and physically extensible, becoming whatever tool your imagination can envision.

So it goes: in our 21st-century cottage (built in the early 20th), computing devices are as ubiquitous as light bulbs, with Windows becoming as irrelevant and obsolete as incandescent lights.  But, “some assembly required” becomes “a lot of assembly, some compiling, and a bit of fabrication essential.”  And, you may have to write your own documentation, operations manual, and maintenance plan, as well as some software.

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

%d bloggers like this: