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.
After 30 years in front of the keyboard, I decided to refine my craft and learn to touch type. It’s been about a month, and I’m improving. Keeping my fingers on “home keys” got me thinking about how often I remove them to touch the mouse. All these keys at my finger tips and they are almost useless for navigation within a file. Hello Vim.
I’ve used Vim for editing text files on a server for years. I knew the basics: insert mode, save, and exit. One of the powerful features of Vim is its modes. The two primary modes are Normal and Insert. When in normal mode, the keys are used to navigate, copy and paste, find, and much more. You don’t need to mouse or cursor keys; in fact, you shouldn’t be using them. To modify text, you enter insert mode, which is the only mode in most text editors. The capabilities of Vim are mind-blowing.
To get started, I watched several videos on Youtube and began a slow transition. While it’s a gradual transition, you will see the benefits quickly. I hope to replaced VS Code with Vim someday. I love the idea of using the same tool proficiently on a desktop, VPS, or Raspberry Pi.
How to get started
Vim Mode – using your existing IDE, such as VS Code, adding a Vim extension to give you basic Vim workflow and key bindings. This is a good bridge from where you are today to Vim 100%.
Six Part Series – Recently, Youtuber, The Primeagan, released an excellent six part series to learn Vim. His videos are educational and entertaining. Watch video 1 and don’t moved to the second video until you don’t need to think about basic navigation keys. I’m not through them all yet.
Explore – There are many Vim tutorial available online. You them to explore the capabilities of Vim to do things easier and faster.
It’s the spring of 2020, and we are all quarantined. Video conferencing tools, like Zoom, are being used daily for work and play. Family chats, games nights, and parties are a regular occurrence in the Cross family.
One of the challenges with family video conferences is when you have multiple people in the same home using separate devices. People scatter to different areas of the house so they can be seen and heard without echos and feedback, which defeats the purpose of gathering together. In the business world, people sit around a conference table and use a conference phone. Everyone uses a single microphone and speaker placed in the center of the table. You can setup the same configuration using a USB conference microphone.
At my home, we all sit at the dining room table with our computers or iPads connected to the Zoom call, and one computer connects to the audio on the Zoom call. All others connect to Zoom video-only. The audio designated computer connects to a USB conference microphone and uses that as the microphone.
I have a mic from MXL, the AC404 USB Conference Mic. It’s one of those things you don’t use often, but it’s very handy when the time comes, such as, a Football Fantasy Draft and Quarantine Party. There are a variety USB Conference mics available from $30 to $100.
Most of my education and entertainment (aka content) comes from podcasts and YouTube. My Linux journey started from those sources and continues today. While this list is fluid, in February 2020 my podcast and YouTube subscriptions include, in no particular order:
Linux for Everyone – Host, Jason, recently switched to Linux and has the switcher insight into Linux. He is a talented writer and entertainer.
Ask Noah Show – Weekly tech radio show with a Linux slant.
Destination Linux – A podcast from techies that love Linux.
Going Linux – Long time show (380+ episodes), a discussion format, much like my show TalkingDrupal.com. It’s just a good listen.
Big Daddy Linux – A weekly live show and “spotlight” interviews with people in the Linux world.
Distro Tube – In depth videos about all things Linux.
Chris Titus Tech – Another switcher that shares how-to and review videos.
Joe Collins – Also known as EzeeLinux, educated on a broad range of Linux topics. His channel is a great resource learning in plain English.
Luke Smith – An open source, privacy guy. Simple and insightful.
LearnLinuxTV – A well rounded show about a variety of software and hardware topics.
Local Drupal development has moved to docker based environments with solutions like Lando and DDEv. With these tools, it’s fast and easy to spin up a local environment and manage many projects. The days of MAMP and WAMP are (long) gone.
Here’s the problem, Mac OS is the dominant development platform for Drupal developers, and Docker runs terribly on it. Docker interacts differently with macOS than it does with Linux. The source code on the host computer is shared with Docker containers. The multiple layers of communication between Docker and the macOS file system make file-sharing very slow. While Docker’s direct access to the Linux file system makes it very fast. This video, Improving Docker Desktop File Sharing Performance, from DockerCon 18 describes this issue in detail.
The file-sharing performance issue became apparent when working with a colleague to set up a new Drupal 8 website build. I was shocked to see the local build process taking over 8 minutes on my colleague’s computer and less than 30 seconds on my computer.
In an unscientific way, with some help from my friends, I tested the build process on a few Macs and Linux computers with different hardware specs. Each computer had Docker and Lando installed. The website is a Drupal 8 Standard profile with Acquia’s BLT. The test is simple, run the BLT artifact build, blt artifact:build
Below are the results of this test.
ThinkPad T420 (2011)
i5 (2 cores), 8GB RAM, SSD
Linux (Endevour OS)
Custom Build (2020)
Ryzen i7 (8 cores), 32GB, SSD
Linux (Endevour OS)
Macbook Air (2018)
i5 (2 cores), 8GB RAM, SSD
MacBook Pro (2015)
i7 (4 cores), 16GB RAM, SSD
There are some potential solutions. Lando has an undocumented Mac-only feature called “Turbo Mode”. Reviewing the issue thread, there are mixed results with this implementation. Turbo Mode had little impact on my test case shaving off 30 to 60 seconds. A 5% to 10% improvement is good, but when comparing it to performance on Linux, there is no practical improvement. Others have seen better improvements with Turbo Mode. This approach is easy to implement and worth exploring, but Turbo Mode hasn’t made it’s way into Lando as a supported feature. Use with caution.
Some tweaks can be made to your Docker configuration. Increasing the default RAM usage from 2GB to 4GB is a starting point. You can also limit the number of shared folders Docker watches, by default, the entire /Users folder is included. I tested the memory upgrade and limited the shared folders to only the necessary application folders. Similar to the results with Turbo Mode, they were minimal for my test case. You may have more promising results. There are many online resources with recommendations to improve performance, search “Docker Mac performance”.
The beauty of using Lando is simplicity, which starts to diminish with lots of OS based tweaks. I suspect more research and testing could result in better performance on Mac. BUT, using Linux for Drupal development with Docker will get you the best performance by far, with ease. It’s that simple.
Over the past two years, I switched from Mac to Linux. I’ve also been breathing life into old computers with upgrades and Linux. With some projects coming up that need more computing power, I decided to build a desktop. After some research, advice from friends, posting questions on forums, and watching many YouTube videos, I built the courage to get started.
I didn’t have a budget, per se, but didn’t want to spend more than necessary. I decided to go with an eight core AMD CPU instead of Intel. A middle of the road GPU. A motherboard and power supply that will handle growth. All wrapped in a low-end case.
AMD Ryzen 7 2700 CPU
MSI x470 Gaming Plus Motherboard
AMD Radeon RX 580 GPU
Corsair 32GB (2x16GB) 3200MHz DDR4 DRAM
500MB m.2 SATA Drive
ROSEWILL ATX Mid Tower Gaming Computer Case
Rosewill ARC Series 750W Power Supply
A pile of parts, where to begin? I had different advice on where to start. I put the CPU, heat sync, RAM, and m.2 on the motherboard first. I then attached the motherboard to the case. I then installed the GPU and plugged the case cables for the front panel buttons and ports into the motherboard. The last step, connect the power supply.
Due to inexperience, I made some minor mistakes and struggled through a few steps.
DDR4 RAM comes in different sizes, 260 pin SO-DIMM for laptops, and a larger 288 pin DIMM for desktops. I assumed the 32GB SO-DIMM I already had could be used in the new computer. I noticed the issue when unboxing the motherboard. I quickly sold the SO-DIMMS on eBay and purchased the proper RAM
When attaching the motherboard to the case, there was no mention in the instructions of ‘stand-off’ screws, which raise the motherboard off the side of the case. I tightened down the motherboard directly on the case without stand-offs. Recognizing a twisted motherboard is likely not correct, I found the answer with a Google search. Luckily, no damage was done. Stand-offs installed.
After checking and double-checking that everything was plugged in properly, the moment of truth arrived, pushing the button. The lights came on, the fans started spinning, but nothing appeared on the screen. I removed the GPU and plugged the screen into the onboard HDMI port. Again nothing. I feared that I didn’t install the CPU correctly. It turned out I plugged the CPU fan into power for the system fan, as you seen in the photo below.
The next step, install Linux. I then discovered the system did not recognize the m.2 500GB drive. Following recommendations from an MSI forum, I re-seated the m.2. No luck. I then updated the BIOS. As a rookie, I felt nervous about doing this step, but it was easy enough. No luck. I also reset the CMOS. No luck. Then I moved the m.2 to the second m.2 location, and it worked. This could be an issue with the motherboard, but is more likely an issue with my understanding of the configuration. I need to do more research on this.
My new desktop is up and running with Endevour OS. It runs great. With three case fans, power supply fan and CPU fan, I’m surprised at how quiet the computer is. I have a few tasks remaining.
Cable management – cables are hanging everywhere inside the case, I need to organize them better.
M.2 – Figure why the m.2 doesn’t work in the first m.2 slot.
Fans – I need to understand where the fans power should be plugged into. The motherboard has spots for pump fans and system fans. I suspect there is a way to control fans for optimum use.
Wireless and Bluetooth – I need to order a card for wireless and bluetooth.
This was a fun project and great learning experience.
Destination Linux – The Destination Linux Network is a great Linux resource. They have great podcasts and a supportive community.
Carey Holzman – Carey is a professional computer technician. His YouTube channel is a good resource for learning about computer builds and repairs.
My Friends – Tim and Nic have experience building computers and were supportive in answering my many questions.
When Apple released MacOS Majove in 2018, the minimum hardware requirements abandon lots of great hardware. While the hardware is still usable, macOS and Apple software cannot be updated to their current releases. That sucks.
This post outlines the process of moving a Mac Mini (mid-2011) to Linux.
The Mac Mini I’m rescuing is a mid-2011 with i5-2415M, 2GB RAM and 500GB HDD, running macOS High Sierra (version 10.13). It’s dreadfully slow. The goal is to use this machine as a general purpose computer in a classroom for high school students.
In addition to changing the operating system from macOS to Linux, the RAM will be upgraded to 8MB and 550GB hard drive replaced with 128GB SSD.
The overall steps:
Order new hardware
Upgrade RAM and Hard disk drive (HDD)
I use Crucial’s website to help determine the parts I can upgrade. Using the model of the computer you’re working on, Crucial will show you the options for memory, hard drive, and SSD upgrades. I often buy the parts on Amazon.
Upgrading this Mac mini is straight-forward. It was built in the days when ‘upgrade-ability’ was built into the hardware design. Finding a YouTube video to guide you through the steps of taking the Mac Mini apart is very helpful. I used this video from MacSales.
The parts inside the Mac mini fit just right. The first time I did one of these upgrades, the SSD wasn’t aligned properly which prevented the wifi from fitting, and the screw holes did not align. Take your time and don’t force anything.
I’ve been using Elementary OS for a few weeks, and I’m impressed. I appears to be a good distribution choice for someone coming from MAC. While my day-to-day distribution is currently Pop_OS!, I’m going to give Elementary a try with this upgrade.
Installing Linux is the same basic process for any distribution.
Download .iso file from the distribution’s website.
Create a bootable USB Drive with the .iso. There are utilities to do that with; I use Etcher.
Boot the target computer from the USB Drive and follow the prompts.
I expected to have issues with wifi. In my experience, when installing Linux on Macs from this era, wifi does not work out of the box. I was pleasantly surprised the Elementary install screen recognized the wifi card and connected to it, and downloaded the latest software update.. After the installation was complete and the computer rebooted, the wifi card was no longer recognized. I needed to install drivers. As in the past, running the following command from the terminal fixes the issue:
sudo apt-get install firmware-b43-installer
Up and running
This upgrade was simple and straight-forward. It’s a fun project for someone that has no experience with hardware upgrades or Linux.
This is my first experience running any type of benchmark. I used GeekBench on the Mac Mini before and after the upgrade. I don’t have much insight into what these numbers mean; I expect to in the future. But my hands-on benchmark tells me this computer runs as fast as much newer hardware and is totally usable.
Before – MacOS w/2GB RAM and HDD
After – Elementary OS w/8GB RAM and SSD
The performance of this Mac Mini would have improved with only the hardware upgrades (without switching to Linux). But on Linux, the performance is really good.
A more important point is that Apple abandoned this Mac Mini. When Mojave was released in 2018, the minimum hardware requirements are:
MacBook: Early 2015 or newer
MacBook Air: Mid 2012 or newer
MacBook Pro: 2012 or newer, Retina display not needed
Mac Mini: Late 2012 or newer
iMac: Late 2012 or newer
Struck at High-Sierra, this computer would only receive security updates, moving forward. Many software applications cannot be updated either. After switching to Linux, this computer can run the latest operating system and applications available on Linux.
I did this upgrade for my friend, Chris. I look forward to see what experience he has in the classroom with Elementary OS.
(It took me 3x longer to write this post than it did to save that Mac mini)
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-composer/drupal-project:8.x-dev 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 ‘drupal8’ for the database name, username and password. Also, use ‘database’ for the host name (under the Advanced settings.
You should be up and running,
12/10/2019 – As of Drupal 8.8.0, Composer project templates are now available as part of Drupal core. The composer create-project command was updated to reflect this change.