Never did I imagine a government request to wear a mask while in public, and when it began, I never imagined I would have an opinion about the design of a mask, but I do.
I expect most people own at least three masks and maybe a dozen or more. For those like my wife, Erica, who wears a mask nine or more hours a day while teaching at school, fit, comfort, and protection are important.
A friend, Johanna, is making masks and gifted one to me. I’ve worn store-bought and homemade masks, and Johanna’s mask is, by far, better than any other I’ve worn. This is why…
My previous masks are not shaped to fit my face. They are basically a strip of material with ear loops on either end. Some have a little shape for better coverage, but none have a place for my nose and chin, and have large gaps around the edges.
Before making my mask, Johanna asked for a measurement from the tip of my nose to the tip of my chin. I expect that is part of the secret sauce.
A – Pocket for the nose B – Pocket for the chin C – No gap around the nose D – No gap on the cheeks E – No gap around the neck
Other than using an N-95 mask, I’ve had trouble with my glasses fogging. Without a gap at C, fogging is not a problem.
Since the mask fits well, it’s comfortable and easily worn for longer periods of time.
I’m not an expert in clothing, but the mask feels well made. It’s my daily driver. It’s been through the wash many times and still holds its shape.
For more information, and to order your own custom-made mask, visit Johanna’s website at www.rayojohis.com. Tell her Stephen sent you!
Create a local folder. <app> will be the name of your application folder and Lando instance.
Position your working directory as your new folder
Initialize Lando and answer a few questions. This utility creates a .lando.yml file in your working directory. When you start Lando in the next step, this file is used to define the Lando configuration.
Choose: current working directory
Enter for webroot: web
Enter for app: <app>
Install Drupal code using composer. Note – Drupal is being install in a Docker container, not on your local computer.
lando composer create-project drupal/recommended-project blah -n
The above command uses composer to install Drupal and it’s dependencies into a folder called ‘blah’. Now, the files/folders in ‘blah’ will be move up one level into your directory and the ‘blah’ folder will be removed.
mv blah/* .
mv blah/.* .
rm -rf blah
Rebuild Lando containers.
lando rebuild -y
On a success rebuilt on Lando, it’s time to install Drupal 8. Goto the local URL for your Drupal 8 website.
Follow the steps in the Drupal installation Wizard. When the database page appears, use ‘drupal9‘ for the database name, username and password. Also, use ‘database‘ for the host name (under the Advanced settings.
In my post Pop!_OS Tiling – Always Float, I describe Window Exceptions and how to implement them manually. The latest release of Pop!_OS Shell, installed with the most recent Pop!_OS 20.04 update, now includes a graphical tool for managing Window Exceptions.
Floating Window Exception is part of Pop!_OS’s Tile Windows feature. It allows you to define a set of windows/applications that will float when they are opened, instead of tiling. This is helpful for utility type applications, like a calculator.
Adding an Exception
To add a new exception, open the application you would like to float. Then open the Floating Window Exception tool from the Tiling Menu. Choose the “Select” button, then select the running window.
You have the option of creation an exception all windows related to the application or only the current window.
After adding the exception, you will see it listed under System Exceptions. In the example below, there are two exceptions for Firefox. You could float all Firefox windows with the “Firefox” exception or just float a specific Firefox window, like “Firefox / Employee Home – Mozilla Firefox”. When floating a specific window, it’s based on the window title. If the window title changes, the exception will not work.
Out of the box, Float Windows Exceptions include “System Exceptions”, which appear to be community curated recommendations. System exceptions default to “On”. I don’t agree with all of the system exceptions and turned a few off.
Floating Window Exceptions settings are stored in .config/pop-shell/config.json. Prior to the new graphics tool, I updated this file manually. The file format is easy to understand and update.
I like to sync this file to multiple computers to keep my configuration the same on all machines.
In 2008, my daughter Allie and I recorded seven episodes of a podcast called With Liberty and Justice for All. Allie was in 5th grade learning about the election in school. It was my idea to create a podcast and she was enthusiastic, for seven episodes anyway. Enjoy!
I’m a fan of tiling window managers. Pop!_OS introduced tiling windows, known as Pop Shell, in version 20.04. While the Pop implementation is not as powerful and functional as a tiling windows manager, like i3 or Awesome, it’s a great start but needs some improvements. In my post, Pop!_OS Switch Workspaces with Super + Number, I recommend adding keyboard mapping to move between workspaces easier.
Some windows don’t work well in tiling mode. The Settings and Calculator applications work better as floating windows
The Pop Shell team is working on improvements for managing a combination of floating and tiling windows. [UPDATE: Pop Shell has been update – read more here]. In the meantime, you can define specific windows to open in floating mode by default. The .config/pop-shell/config.json file below defines the Settings window, “Gnome-control-center”, and Calculator, “Gnome-calculator”, to open in floating mode.
Currently, only the window class is required in config.json.
How to determine the window class
Finding a window class is simple. Open the application (window). Also open the terminal. In the terminal, run the command: xprop | grep WM_CLASS, then click on the window you want the class for. Back in the terminal you will see the class information. Use the second string as the class.
At the beginning of the year, I built my first computer. This post is about my first hardware issue with that computer.
I should title this section, ‘User Failure’ or ‘Idiot’. My computer has been fantastic and worked flawlessly until I decided to upgrade, adding a second m.2 drive for expanded storage. While adding the new drive, I turned my back, and the computer fell from my desk onto the floor. Ugh. Then it would not boot.
The computer appeared to turn on, I could see lights and fans were spinning, but nothing appeared on the display. I’ve since learned this behaviour is called a “no post”. A POST is a Power On Self-Test, a process that runs on each boot and tests the system hardware before loading the operating system. On a successful POST, you will likely see the motherboard logo and option to enter the BIOS.
Resolving No Post
There is a wealth of information online to help resolve a no POST. It boils down to understanding the minimum hardware you need for a successful POST and eliminating each as causing the problem. Basically, with just the CPU, Power and RAM you should get a successful POST.
I removed the parts not required to have a successful POST, the m.2 storage, Wifi card, and GPU. I disconnected all power cables and connectors except the motherboard power, CPU power and power switch connector. I verified the CPU and RAM were seated properly. The only external connections were to the power and display (via HDMI port). On power-up, the fans spun up, but no POST.
RAM I tried each memory sticks alone and verified they were in the right location. Power-up, no POST. It was unlikely both sticks of RAM were faulty. Move onto BIOS.
BIOS I used a jumper to reset the BIOS, removed the battery, and pushed the CMOS reset. Power-up, no POST. I have three parts left, Power Supply, Motherboard, and CPU.
Power Supply Since the fans are spinning and lights are on, I assumed the power supply was working fine. My research explained that the power supply could be faulty and still provide some power, like a battery that powers the radio but will not start the car. I purchased a power supply. Again, power-up, no POST.
Motherboard Unlike the power supply, which I could purchase at Best Buy fifteen miles away, I had to order a motherboard online. Again, power-up, no POST.
RAM Part 2 Since I had to wait a few days for the motherboard, why not replace the RAM. Back to Bestbuy. Power-up, no POST.
CPU My research indicated the CPU was the most unlikely problem, but I had nothing else to replace. I ordered a new CPU and waited another two days. Ugh, power-up, no POST.
Less the case, I built a new computer and had the same problem. This reminded me of my father’s old joke, “The lumberjack said, I used the same axe for 25 years, I’ve replaced the handle ten times and head five times”. Something was going on here I did not understand. Clearly, the issue was between my ears.
There is a set of lights on the motherboard called Check EZ Debug LED indicator, used for debugging the POST process. The VGA indicator was lit during each test, which made sense because that is the problem I was trying to solve. If I removed the RAM, the RAM indicator would light up.
I put the GPU back into the system, and the VGA indicator remained on. This is when MY light went on. While there is an HDMI port on the motherboard, there is no onboard graphics. The CPU (or motherboard) would need to have graphics support, which my CPU does not. The fine print regarding Onboard Graphics for the MSI X470 Gaming Plus reads:
Only support when using Radeon™ Vega Graphics and 2nd Gen AMD Ryzen™ with Radeon™ Graphics/ Athlon™ with Radeon™ Vega Graphics Processors
The issue, all along, was the GPU. One more trip to Best Buy and I was up and running.
The issue was very straight forward, but my lack of experience turned a one-day minor problem into a ten-day, painful, costly issue. If there was graphics support on the motherboard or CPU, I would have discovered the issue quickly. Because there wasn’t and I didn’t understand that, I saw the same No POST issue with the GPU and without it.
My take away: The presence of an HDMI port does not mean it’s usable, onboard graphics must be supported.
I did enjoy the learning process, and I’m more comfortable inside the computer.
For developers, I recommend using Pop!_OS as your first Linux distribution. After using MacOS for fifteen years, my first Linux experience was with Pop!_OS, and I’ve explored other Debian and Arch-based distros. I’m currently using Pop!_OS and EndevourOS.
Pop!_OS is an excellent transition distribution for developers moving to Linux for the following reasons:
Made by developers for developers.
Pop!_OS is maintained by System 76, a leading manufacturer of professional hardware designed to run Linux. In the hands of System76, there is a focus on performance, reliability, and usability for the developer. System76 descried Pop!_OS as “an operating system for STEM and creative professionals who use their computer as a tool to discover and create.”
While Pop!_OS comes pre-installed on System76 computers, it will install on any (Linux friendly) computer. While there are distributions designed to run well on old, underpowered hardware, I have found Pop!_OS to be lightweight enough to perform well on a broad range of hardware. I’m currently running it on a System76 Laptop, custom-built tower, and the good old classic Thinkpad T420. Pop!_OS also supports modern, cutting edge hardware and is often the choice of gamers.
As a recovering Mac “fan boy”, I appreciate an operating system that looks and feels premium. Before switching to Linux, I had the impression that Linux would look and feel old. While some Linux desktop environments look old, many, like Pop!_OS and Elementary, are beautiful. Out of the box, without customization, Pop!_OS is not a step down from Mac OS.
The Pop!_OS desktop is clutter-free. No dock. No Menu. Just a status bar at the top of the window. This minimal interface can be a jarring when coming from Windows and macOS. I now appreciate the OS getting out my way and valuable screen space is reserved reserved for my work.
While it’s possible to add a macOS like dock (with Dash to Dock), I encourage people to use op!_OS defaults for a few weeks before making changes. As I mentioned earlier, Pop!_OS is made by developers; the default settings are purposeful.
While Pop!_OS comes with very few applications installed, the Pop Store provides one-click installation of hundreds of applications. From Slack and VS Code to photo editors, video editors, office tools, and games. The Pop Shop catalog has grown a lot in two years. It supports APT, and Flatpack installs.
Tiling Window Manager
Pop!_OS introduced a “tiling window” like feature with version 20.04. With tiling window mode on, windows don’t overlap. When a window opens, it splits the space with the existing windows. Without tiling windows mode on, Pop!_OS works like macOS and Windows, with floating windows. Windows are resized by you and can overlap. Tiling windows allow you to maximize screen space and increase productivity using keyboard shortcuts.
Pop!_OS also supports Workspaces, which are virtual desktops. The combination of Tiling Windows, Workspaces makes for a powerful combination. (I make a minor tweak to the keyboard shortcuts to switch workspaces with Super + Number.)
Switching to Linux can be challenging. Choosing a Linux distribution that looks and works great out of the box makes the transition easier. In my experience, Pop!_OS ‘just works’, allowing you to get comfortable in the Linux world.
Pop!_OS introduced a “tiling window” like feature with version 20.04. With tiling window mode on, windows don’t overlap. When a window opens, it splits the space with the existing windows. Tiling windows allow you to maximize screen space and increase productivity using keyboard shortcuts.
Pop!_OS also supports Workspaces, which are virtual desktops. The combination of Tiling Windows, Workspaces and dual monitors makes for a powerful combination.
I like to setup Workspace 1 for communication with e-mail and chat clients (Slack, Telegram, Mattermost…). Workspace 2 for developments with terminals, IDE, and browsers. Workspace 3 for documentation with text editors, note taking apps and browsers.
Pop!_OS has a set of keyboard shortcuts to navigate between windows and workspaces. I find them inadequate when it comes to switching between Windows and Workspaces. With the additional keyboard bindings below you can switch between Workspaces using SuperKey + Number.
SuperKey + 1 switches to workspace 1 and SuperKey + 2 to workspace 2, etc… up to 9. Add the Shift key, and the current focus window moves it to the workspace.
This minor change to Pop!_OSs titling window keyboard shortcuts make it far more usable.
Copy and paste the code below at the terminal.
gsettings set org.gnome.mutter dynamic-workspaces false
gsettings set org.gnome.desktop.wm.preferences num-workspaces 8
gsettings set org.gnome.shell.keybindings switch-to-application-1 
gsettings set org.gnome.shell.keybindings switch-to-application-2 
gsettings set org.gnome.shell.keybindings switch-to-application-3 
gsettings set org.gnome.shell.keybindings switch-to-application-4 
gsettings set org.gnome.shell.keybindings switch-to-application-5 
gsettings set org.gnome.shell.keybindings switch-to-application-6 
gsettings set org.gnome.shell.keybindings switch-to-application-7 
gsettings set org.gnome.shell.keybindings switch-to-application-8 
gsettings set org.gnome.shell.keybindings switch-to-application-9 
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-1 "['<Super>1']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-2 "['<Super>2']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-3 "['<Super>3']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-4 "['<Super>4']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-5 "['<Super>5']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-6 "['<Super>6']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-7 "['<Super>7']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-8 "['<Super>8']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-9 "['<Super>9']"
gsettings set org.gnome.desktop.wm.keybindings switch-to-workspace-10 "['<Super>0']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-1 "['<Super><Shift>1']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-2 "['<Super><Shift>2']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-3 "['<Super><Shift>3']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-4 "['<Super><Shift>4']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-5 "['<Super><Shift>5']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-6 "['<Super><Shift>6']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-7 "['<Super><Shift>7']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-8 "['<Super><Shift>8']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-9 "['<Super><Shift>9']"
gsettings set org.gnome.desktop.wm.keybindings move-to-workspace-10 "['<Super><Shift>0']
I have two Linux computers at my desk. A (closed) laptop connected to a monitor and a home grown tower connected to two monitors. Three monitors in all. I frequently switch between these computers and control them with one keyboard and mouse.
For the past few years, I’ve been using a Logitech wireless keyboard (K780) and mouse (M585) that support multiple computers. One computer is connected to the keyboard and mouse via a wireless dongle, and the other is connected via Bluetooth. A set of keys switches the keyboard between computer, and a button switches the mouse. While the switching works most of the time, sometimes there is a delay. It’s frustrating when keystrokes are delayed or missing.
I recently switched to a wired keyboard and mouse and control the switching with software KVM (Keyboard Video Mouse). After using this for a week, I wish I had made this change sooner. Barrier is an open-source solution that works on Linux, Mac and Windows.
This solution is for sharing a single keyboard and mouse with multiple computers. Each computer requires a monitor.
After installation, you set up one computer as the server, and others as clients. On the Barrier server, you add a screen for each client computer using it’s machine name and position it relative to the server screen. For example, my computer called “pop-os” is to the left of “rebel-tower”.
On the client machines, you identify the address of the Barrier server.
After Barrier is running on the clients and server, when working on rebel-tower and moving the mouse off the screen to the left, the mouse will begin moving on the pop-os screen. Wherever the mouse is active, the keyboard is active. You move the mouse to the computer you want to type on. This implementation is more natural to use than pushing keys and buttons, and it’s fast and smooth.
I have not used any of Barrier’s advanced settings, maybe someday. You can define keystrokes to switch computers and activate advanced functionality. Barrier’s Linux version does not support drag and drop between computers, but Mac and Windows is supported. While this feature could be useful, it’s not critical for me.
I’m always surprised by the quality and abundance of open source Linux applications.
I recently returned from a trip to Arizona, helping my daughter, Allie, move to Phoenix to pursue a PhD at Arizona State University. We drove from Rhode Island to Arizona. We drove 2,699.3 miles, over three and a half days, with two cars, a UHaul, four adults, a cat, and, a hedgehog.
Day 1 – Bristol, RI to Springfield, OH – 764 miles Day 2 – Springfield, OH to Emporia, KS – 764 miles Day 3 – Emporia, KS to Albuquerque, NM – 674 miles Day 4 – Albuquerque, NM to Phoenix, AZ – 419 miles
With the first day being the longest drive, we traveled approximately 12 hours on the first three days and 6.5 hours on the last day. We lost an hour each day with the time zone change. Choosing “no tolls” when planning the route took us off the main highways and only added an hour to the overall trip. I believe we took a more scenic, rural route.
While I expected the drive to be tedious and exhausting, it was relaxing and enjoyable. We switched drivers about every 3-4 hours and stopped for bathroom breaks and gas every few hours. As we started each day at 5 am, in the dark, we ended each night around 5 pm, had dinner after the day’s drive was complete, and got proper rest each night.
Traveling with Pets
Draco is a 20lb, easy-going, cool, black cat, but we didn’t know how he would tolerate a four-day road trip. Fortunately, he remained cool, thanks to his mom’s preparation. Allie outfitted the back seat with a pet hammock that covered the backseat and prevented Draco from getting on the floor. He had comfortable blankets and a portable litterbox, which he never used in the car. Draco and Winston, a hedgehog, slept all day, which is what they do anyway. We stayed in pet-friendly hotels each night. Some charge a fee, and others are free. Winston had a full setup each night with a five-foot cage, running wheel, heat lamp, hay, food, and water. It was easy, but I didn’t do anything.
The year 2020 will be memorable for the global pandemic, Covid-19. It wasn’t the best time to drive across the country, sleep in different hotels every night, have an extended stay in the country’s hottest zone, and fly home. Each US state has different guidelines and is in various phases of re-opening. To our dismay, there were no indications of a serious pandemic in our mid-west stops. Many, maybe most, people did not wear masks. We stayed at national chain hotels, and they were all excellent at following guidelines. My wife, Erica, did a thorough cleaning of the room each night, and we were all cautious.
New Mexico was the standout for implementing guidelines. Everyone wore masks and stores strictly enforced distancing. In Arizona, we had the impression they just realized the country was in a pandemic. There was a sign in the hotel indicating masks are required as of June 20. Really? In Rhode Island, they have been required since April.
Thanks to a doctor friend, we had two N-95 masks for the trip home. Both flights were full, with not an empty seat to be found. We wore the N-95s for 11 hours, with only a few minutes of relief for water and a small snack. Moving to the exit row with just two seats for the five-hour flight made is feel safer, but it likely didn’t make a difference.
Unfortunately, the most entertaining moment was provided by me. Each day started with coffee and a gas fill-up. I pulled into the gas station, started the gas pump, and went into the store for milk. After paying for the milk, I hopped back in the Jeep and pulled away, taking the gas line with me. The hose, which was once connected to the pump, was now dragging behind the car. As gas poured from the pump onto the pavement, I ran inside to alert the attendant of the pending ‘breaking news’ explosion. I was a little panicked. Little did I know this was a regular occurrence; the hose has a quick release and shutoff. The attendant casually walked out with a bucket of sand to clean up the gas and had the hose reconnected with a minute or two. In the other car, my daughter was disappointed she didn’t get a photo of the event and proceeded to laugh for 20 minutes and share the experience with family via text.
The last day’s drive from Albuquerque, New Mexico to Phoenix, Arizona was fantastic. While the terrain changed by the day during our journey, it changed by the hour for the last 420 miles. We went from 65 degrees Fahrenheit to 117 degrees in six hours traveling from the flat desert of New Mexico through the mountain ranges and into the desert of Arizona. We didn’t see cacti until we started to descend from the pine tree rich 6,000 ft mountain elevation into Phoenix’s valley. As the temperature rose, the cacti appeared. It was a breathtaking view for us New Englanders.
Because the purpose of our trip was moving, not sightseeing, we are thinking about a more leisurely trip across the US in the future.