Another “missing and missed” functionality in MySQL is a data type for arrays.

While MySQL is not there yet, it’s now possible to cover a significant use case: storing denormalized columns (or arrays in general), and accessing them via index.

In this article I’ll give some context about denormalized data and indexes, including the workaround for such functionality on MySQL 5.7, and describe how this is (rather) cleanly accomplished on MySQL 8.0.

• Terminology
• Storing and indexing arrays in MySQL 5.7: an approach, and problems
• The MySQL 8.0 implementation: data type and index
• Performance expectations
  • Why multiple arrays can’t be indexed
• How do I declare an ARRAY UNSIGNED column?
• Conclusion
• Footnotes

Another interesting feature released with MySQL 8.0 is full support for functional indexes.

Although this is not a strictly new concept in the MySQL world (indexed generated columns provided the same functionality), I find it worth reviewing, through some applications, notes and considerations.

All in all, I’m not 100% bought into functional indexes (as opposed to indexed generated columns); I’ll elaborate on this over the course of the article.

As a natural fit, generated columns are included in the article; additionally, some constructs build on my previous article, in relation to the subject of CTEs.

Updated on 12/Mar/2020: Found another bug.

Contents:

• Terminology
• Generated columns, and their application on JSON data
• Functional indexes
• JSON functional index gotchas
  • Expression exactness
  • Inconsistent behavior between generated columns with index, and functional indexes
  • Encoding inconsistency based on the index usage
• An example of functional index with dates
  • Gotcha: JOINs don’t use functional key parts
• Bugs
  • Bug on CREATE TABLE ... SELECT
  • Bug on LOAD DATA INFILE
• Conclusion

A long-time missing (and missed) functionality in MySQL, is sequences/ranges.

As of MySQL 8.0, this functionality is still not supported in a general sense, however, it’s now possible to generate a sequence to be used within a single query.

In this article, I’ll give a brief introduction to CTEs, and explain how to build different sequence generators; additionally, I’ll introduce the new (cool) MySQL 8.0 query hint SET_VAR, and a pinch of virtual columns and functional indexes (“functional key parts”, another MySQL 8.0 feature).

Contents:

• A brief introduction to Common Table Expressions (CTEs)
• Recursive CTEs, and generating a linear sequence of integers
  • Per-statement variables setting
• Generating a sequence of random integers
• Generating a characters interval
• Generating a dates interval
• Conclusion
• Footnotes

Sometimes, either in scripts or direct commands, there is a series of repetitive, similar, commands, which could be executed in parallel.

Bash offers means for very basic parallelization (& and wait), however, they’re not very practical for generic solutions.

In this article, I’ll explain how to use GNU Parallel, which makes parallelization trivial, and, as usual, introduce some other useful shell concepts.

Contents:

• Using Bash built-in commands
  • Conclusion
• Enter the stage: GNU Parallel
  • Important to known: CPU count, from a Linux perspective
  • Base example: untarring multiple archives in parallel
  • Using positional parameters
  • Running multiple commands from a file
• Escaping strings in Bash
• Sending the content of a file to a process
• $XDG_RUNTIME_DIR
• Conclusion
• Post-conclusion

I’ve been a long time user of SBCs; as part of my equipment, I’ve always had the need for a small home server, which they fit increasingly well.

My previous SBC has been an ODROID XU4, which I’ve covered in a previous article.

I’ve been reasonably happy of it, however, my requirements overgrew its limitations, therefore, as soon as the second batch of ODROID H2 was available, I jumped at the chance to switch.

Like in the XU4 article, I will make some general considerations about small home servers and how to H2 fits the (my) requirements, and how ARM and x86 board nowadays relate.

Contents:

• Part 1: History and considerations
  • What do I do with a home server?
  • The bumps
  • ARM boards come with an expiry date
    • A specific example of the difference between a modified kernel and a vanilla one
  • Requirements
  • A brief look at the evolution of SBCs
• Part 2: The ODROID H2
  • The bad: the enclosure
  • The OK
  • The good: all the rest
  • The alternatives
• Part 3: A comparison of H2, N2 and Pi 4
  • The ODROID N2
  • Benchmarks
  • Pricing
• Part 4: The future
  • ARM
  • x86
• Conclusion

In this post I’ll expand on the subject of my MySQL pre-FOSDEM talk: what dbadmins need to know and do, when upgrading from MySQL 5.7 to 8.0.

I’ve already published two posts on two specific issues; in this article, I’ll give the complete picture.

As usual, I’ll use this post to introduce tooling concepts that may be useful in generic system administration.

The presentation code is hosted on a GitHub repository (including the the source files and the output slides in PDF format), and on Slideshare.

Contents:

• Summary of issues, and scope
• Requirements
• The new default character set/collation: utf8mb4/utf8mb4_0900_ai_ci
  • Summary
  • Tooling: MySQL RLIKE
  • How the charset parameters work
  • String, and comparison, properties
  • Collation coercion, and issues general <> 0900_ai
    • Comparisons utf8_general_ci column <> literals
    • Comparisons utf8_general_ci column <> columns
    • Summary of the migration path
  • The new collation doesn’t pad anymore
  • Triggers
    • Sort-of-related suggestion
  • Behavior with indexes
  • Consequences of the increase in (potential) size of char columns
• Information schema statistics caching
• GROUP BY not sorted anymore by default (+tooling)
• Schema migration tools support
• Obsolete Mac Homebrew default collation
  • Modify the formula, and recompile the binaries
  • Ignore the client encoding on handshake
• Good practice for (major/minor) upgrades: comparing the system variables
• Conclusion

When managing Ubuntu Server installations, for example image templates in the cloud, one of the main issues one comes across is apt locking, which causes the the annoying error Could not get lock /var/lib/apt/lists/lock, typically “at the worst times”.

This seems to be a matter of discussion on the Stack Overflow network, but there are no working and stable solutions.

In order to get an idea of the confusion about the subject, check out the number and scope of solutions in this Stack Overflow question.

In this post I’ll talk about a few approaches, and the stable solution I’ve implemented.

Readers interested in just solving the problem can skip to the Eureka™ section.

Contents:

• The general setup
• Assumptions
• The problem
• Potential solutions
  • Retrying in case of errors
  • Inspecting the running processes
  • Disabling the services
  • Waiting on cloud-init to complete
  • Using flock
  • Using fnctl
  • The “screw it” solution: replace /usr/lib/apt/apt.systemd.daily
• Eureka™
• Conclusion

Every month, I purge the files trashed more than one month before.

Since it’s been scientifically proven that manual operations cause PTSD in system administrators, I’ve made a script.

In this small article, I’ll explain some concepts involved, most notably, working with dates and numbers in Bash, and some other scripting-related concepts.

Contents:

• The base structure
• Writing safer Bash scripts
  • errexit
  • nounset, with pattern
  • pipefail
    • pipefail versus grep -q
• First step: Handling dates, cycling the data
• Splitting a string via Perl
• Splitting a string via cut
• Dates, arithmetic, and putting all together
• Conclusion
• Footnotes

While researching a MySQL subject, I needed to process the MySQL server status variables (output), in order to extract and process some.

A computed value in particular (the max checkpoint age) required more elaborate processing.

This post explains a few Perl text processing functionalities (optionally aided by Awk), through many approaches to solving the problem.

Contents:

• Input data, problem, and clarifications
• The approaches
  • Slurp mode, with single regex
  • Slurp mode, with global match
  • Conditional line matching
  • Two-passes processing, with single-line intermediate output
  • Two-passes processing, with readline in the second pass
• Conclusion: should cryptic (Perl) scripts be avoided in a team context?

Yesterday, I’ve officially released my ZFS Ubuntu installer.

This project will hopefully help the adoption of ZFS, at least by appealing curious/interested sysadmins.

Canonical is about to officially release an Ubuntu with built-in ZFS support, however, it has extremely limited functionality.

Create a VM, launch the program, and have fun playing with ZFS!

Although there is a complexity threshold for the convenience of shell scripting, there is still plenty that (in my opinion) can be done before hitting such ceiling.

In this brief article, I’ll explain how to use indirect references to write a function that prints the names and content of the variables passed; this is useful when writing debugging code for a script.

Contents:

• Specification
• Quick introduction to Bash array data types
  • Arrays
  • Associative arrays
• Other notions
• Indirect references, and writing the function
• Debugging goodies
• Conclusion

Debugging a live/stuck Ruby process is a well-known subject.

The way it’s generally exposed is simply a series of instructions and their outcome; given the expectation, this is fine of course, however, when I saw that a manual copy/paste operation was required, I decided to… step in (pun intended 😂).

This article adds only a few concepts, operatively speaking, but it clarifies all the concept involved, and employs neat approaches to accomplish the task. I will also employ several goodies available to Linux systems.

Contents:

• Premises
• A brief overview of debugging a process, and ptrace
• Using pgrep
• A brief overview of file descriptors
• Putting together Ruby and GDB (with fancy grep!)
• Basic GDB usage
• The procedure
  • The procedure, neater!
• Safety of messing with file descriptors
• Other GDB/Ruby tools
  • Evaluating Ruby statements
  • An alternative option to redirecting stdout/stderr
  • Other interesting sources
• Conclusion

In my latest sysadmin experimentations, I’ve configured the unattended upgrades on my new server (an Odroid H2 😍).

Among the other things, I had to add a PPA to the list of allowed origins to automatically upgrade. This required some interesting text processing, so I decided to dig into Perl’s text processing functionalities.

This post describes how to enable unattended upgrades for a PPA, while explaining several useful Perl features, in particular, how to process key/value tuples; a few regular expression functionalities are also used.

Contents:

• Update
• A high level overview of how to enable unattended upgrades for a PPA
• Premises, and structuring the procedure
  • Capturing groups
  • Processing the input text as a single string
    • The “multiple lines” match operator modifier (m)
  • The “global” match operator modifier (g)
  • The join() function
  • Adding a line to an input, after a match
• The final commands
• Conclusion

A functionality that I require, relatively frequently, when scripting, is to print the last N fields of a stream, with awk.

A typical example, is to copy part of the commits of a git cherry/log command:

+ 81061edd2023c399539f1ff5cfdc267fd41c5c43 Ruby GUI development article: add `Some references` section
+ 5c60b7ef357683137b5f772f8590ab7d12c8e218 Ruby GUI development article: add `Footnotes` section
+ b6fe3469bc2ae59a7eba629c16ab11c67b7fbcbf Ruby GUI development article: add note about browser-based toolkits
[...]

This post explains how to do it, with some extra goodies.

Contents:

• Reformulating the approach
• The pieces
  • Automatically printing the newline (in Perl 5.x)
  • Autosplit
  • Slicing an array
  • Send the stdout of a process to the global clipboard
• Putting everything together
• Conclusion
• Footnotes

2019 is a very exciting year for people with at least a minor interest in storage. First, in May, the ZFS support for encryption and trimming has been added, with the release 0.8; then, in August, Canonical has officially announced the plan to add ZFS support to the installer¹ in the next Ubuntu release.

As of now, achieving a full-ZFS system (with a ZFS root (/)) is possible, although non trivial. In this walkthrough, I’ve made the procedure as simple as possible, additionally setting up encryption and mirroring (RAID-1).

I’ll also give an introduction about the concepts involved, so that one has better awareness of the purpose of all the steps (but feel free to jump directly to the procedure).

Note that this guide is stable, but I’ll keep adding a few more sections and content in general.

Contents:

• Update
• An introduction to the concepts involved
  • The boot process: BIOS and EFI
  • GRUB
  • The /boot directory/mount
  • /boot vs. /boot/efi
  • Ubuntu’s ZFS support
  • Chroot
  • Udev
  • ZFS pools, filesystems and volumes
• Philosophy and limitations
• Requirements and specifications
• Procedure
  • EFI check
  • Preparations
  • Install the ZFS module in the live (loaded) kernel
  • Find the disks
  • Prepare the disk(s)
  • Install Ubuntu
  • Chroot and prepare the jail
  • Install ZFS 0.8 packages
  • Install and configure the bootloader
  • Cloning the EFI partition
  • Configure the boot pool import, and remaining settings
  • End
• Tweaks
  • Databases
• Conclusion
• Footnotes

Today we’ve had an emergency in production, which caused us to process log files.

An operation that comes very helpful in these situations is to quickly compute aggregates for values found in logs (or text files, in general).

This is possible, and actually easy, with the usual *nix tools; in this post I’ll explain three approaches to this problem.

Contents:

• Premises
• The generic and flexible, but a bit clunky solution: Perl + SQLite
• The simple and elegant solution: GAWK or Perl
• Working around OS X
• Bonus
• Conclusion

Fairly recently, we’ve upgraded to MySQL 8; it’s been a relatively smooth transition, however, some minor differences needed to be handled. One of them is the behavior of trailing spaces.

Trailing spaces are a (not in a good way) surprising, but also widely covered argument. This article gives a short overview, and relates it to how this affects people upgrading to MySQL 8.0.

Contents:

• Premises/Requirements
• Behavior in different contexts
  • Comparison (=) predicate (1)
    • Inspecting the collations
  • Comparison (=) predicate (2)
  • LIKE predicate
  • Unique indexes
  • DISTINCT predicate
  • GROUP BY clause
• Conclusion

Unexpectedly, the SQL Standard (ISO/IEC 9075) documents, while public, are not free - they’re copyrighted, and available for purchase.

Still, some versions can be found on the web. PostgreSQL has a related section in their wiki, however, one link is out of date.

This is the up to date list of the documents, stored in the Wayback Machine, so that they’re permanent:

• 1992 (draft, txt)
• 1999 (part 2, pdf)
• 2003 (zip)
• 2011 (preliminary, zip)

For reference, the most relevant part is #2.

During my last vacation, I wanted to watch some very old cartoons, during the daily break, on the digital media player that the apartment provided.

The player was very old, and couldn’t handle the video file (a modern MP4). Therefore, this was a good occasion to exercise the FFmpeg conversion and processing capabilities.

This post will give a glimpse of the tools that FFmpeg provides, showing how easy it is to perform the video/audio conversion, with extra processing.

I will also explain general concepts of media handling, like containers and encoding formats.

Contents:

• What is FFmpeg (and Libav)
• A brief introduction to video file related concepts and formats
• First attempt: a basic audio/video conversion
• Interlude: encoding bitrate modes
• Scaling (down) the video
• Backpedaling to CBR
• Mixing (down) the audio channels
• Splitting the file
• Conclusion

When it comes to configuring MySQL, a fundamental step is to find out which configuration files the MySQL server reads.

The operation itself is simple, however, if we want to script the operation, using text processing in a sharp way, it’s not immediate what the best solution is.

In this post I’ll explore the process of looking for a satisfying solution, going through grep, perl, and awk.

Contents:

• Assumptions
• Input data (finding the configuration files read by MySQL)
• First step: grep+tail
• Second step: expanding the tilde
• Final step: awk’s super powers
• Extra step: using the output
• Conclusion

Recently, I needed to test some operations to be performed during the installation of Ubuntu on a system.

This requires multiple sessions and reboots, so retaining the changes on the installation media would considerably streamline the task.

VirtualBox doesn’t support booting a VM from a USB flash drive though, so a workaround is required.

This small article explains how to do this.

Contents:

• Options and procedure(s)
  • Using the VMDK format
  • Using the key dump as a disk
• Conclusion and considerations

Due to some constraints, at Ticketsolve we sometimes need to work with an ancient file format: the Paradox Database.

This file format was in use between the 80s and 90s. In order to perform some operations on Paradox databases, nowadays, there are libraries based on the file format reverse engineering work by individual open source programmers, or ad hoc commercial programs.

Additionally, one can use Paradox 7, the reference commercial software originally published in 1992, now abandoned.
This software works good enough in Wine, however, the installer generally raises an error on installation, complaining that there isn’t enough disk space.

In this post we’ll use Radare2, one of the most powerful open source reverse engineering frameworks, in order to statically analyze and patch the installation binary, so that the pesky error is not triggered anymore.

There are no requirements for the reader; knowing x86/32 assembler and the PE executable format will improve the understanding, but it’s not a requirement by any means.

Contents:

• Disclaimer
• Tools
• Problem
• Finding a starting point
• Examining the relevant function
• Deciding and approach, testing the theory, and patching the binary
• Digging further
• Taking the simplest approach, and creating the final patch
• Distributing the patch
• Conclusion

I wanted to tweak a script of mine; it included the conventional find </path> -maxdepth 1 -type f. I wasn’t fully convinced it was the best choice, so I checked out what’s the ls equivalent.

This post is about the research I’ve done; as usual, it’s an exercise in extensive usage of the available tools.

Note that I’ve been notified by a reader of the ls parameter -A, which simplifies the logic. I’ve kept both sections, for two reasons:

• the concepts not needed with the new approach are interesting to know regardless;
• in the new section I don’t explain in detail the concepts already explained in the old one.

Contents:

• Introduction to the problem, and the find tool
• Exploring ls
• A better approach, via ls -A
• Conclusion

We’re in the process of upgrading our MySQL databases from v5.7 to v8.0; since one of the differences in v8.0 is that the default encoding changed from utf8 to utf8mb4, and we had the conversion in plan anyway, we anticipated it and performed it as preliminary step for the upgrade.

This post describes in depth the overall experience, including tooling and pitfalls, and related subjects.

Contents:

• Introduction
• Migration plan: overview and considerations
  • !! COLLATION WARNING !!
  • Free step: connection configuration
    • How do charset settings affect database operations?
  • Step 2: Preparing the the ALTER statements
    • Issue: Column/index size limits
    • Issue: Triggers/Functions
    • Issue: Joins between columns with heterogeneous charsets
  • Step 3: Altering the schema and tables
  • Warnings
    • Other schemas
    • Always run ANALYZE TABLE
    • Don’t rush the DROP TABLE
• Notes about Mathias Bynens’ post on the same subject
• Conclusion
• Footnotes

We recently had to drop a column in production, from a relatively large (order of 10⁷ records) table.

On modern MySQL setups, dropping a column doesn’t lock the table (it does, actually, but for a relatively short time), however, we wanted to improve a very typical Rails migration scenario in a few ways:

1. offloading the column dropping time from the deploy;
2. ensuring that in the time between the column is dropped and the app servers restarted, the app doesn’t raise errors due to the expectation that the column is present;
3. not overloading the database with I/O.

I’ll give the Gh-ost tool a brief introduction, and show how to fulfill the above requirements in a simple way, by using this tool and an ActiveRecord flag.

This workflow can be applied to almost any table alteration scenario.

Contents:

• Gh-ost
• Setup and workflow
  • Existing configuration
  • Configure ActiveRecord for ignoring the column, and performing the deploy
  • Using gh-ost to drop the column
  • Remove the ignored_columns and redeploy
• Conclusion

The bindings for the standard Ruby GUI toolkit, Tk, need some trickery in order to be installed on Ubuntu. This article shows how to do it.

Contents:

• Some history
• Prerequisites
• Workaround and installation

I’ve recently moved from Bash to Zsh, and I needed to port my tab completion scripts. Zsh has a sophisticated built-in tab completion, however, the documentation is not very beginner-friendly; moreover, Bash scripts can be used with no or little change in Zsh. Therefore, I’ve opted for using them directly.

This article will explain how to write tab-completion scripts in any language, with an example in Ruby, and how to use them in both Bash and Zsh.

As typical of this blog, the script is also used as an exercise in shell scripting, therefore, it contains additional (arguably) useful/interesting commands/concepts.

Contents:

• General notes
• Ruby Library
• Writing a tab-completion script
• Specification of the target program
• Writing the tab completion script
• Setting up autocompletion
• Debugging
• Conclusion

Seldom, the subject of how to wipe the disk(s) of a headliness linux server comes up; there are a few resources online about it. This blog summarizes all the information around into a clean, stable and generic script that can be used in order to perform this task.

As typical of this blog, the script is also used as an exercise in shell scripting and system administration, therefore, it contains (arguably) useful/interesting commands/concepts.

Contents:

• Preamble/specifications
• Procedure

Although the concepts involved in preparing a Debian (.deb) source package and publishing it on an Ubuntu PPA are simple, due to the many moving parts involved, it’s not easy to find a single source of information.

This article provides all the information required to perform the process, using a trivial program as an example.

Contents:

• About the approach and standards
• Conventions
• The procedure
  • Setup
    • Preparing the system
    • Setting up and publishing the PGP key(s)
    • Setting up a Launchpad account
    • Creating the PPA
  • Preparing the source package
    • Introduction to Debian packaging
    • Preparing the source code
    • The makefile
    • Debian packaging metadata creation and core concepts
    • Updating changelog
    • Updating control
    • Updating copyright
  • Building the source package
  • Uploading the package
  • Deleting a package
• Using the PPA
• Conclusion

With the large diffusion of SBCs [Single Board Computers], and subsequent maturation of their ecosystem, it’s now relatively easy to setup a home server.

I’ve had three SBCs until now; a Raspberry Pi 2 model B, a 3 model B, and recently, an Odroid XU4.

In this post, I’m going to share some considerations about their usage as home servers.

Updated on 3/Jul/2019: added new generation boards section.

Contents:

• Considerations about new generation (A7x and Goldmont Plus) boards
• General characteristics of an SBC/home server
• Brief informations about ARM processors
• Raspberry Pi 3 Model B
  • Specifications
  • Support and documentation
    • BEWARE: Stay far from the Ubuntu Pi Flavour Maker
  • Usage impressions
• Odroid XU4
  • Specifications
  • Support and documentation
  • Usage impressions
  • Power draw
  • The infamous fan noise
    • Introduction
    • Base setup
    • Solutions and references
  • Performance tweaking
• Alternatives
• Benchmark
• Conclusions
• Footnotes

In system administration, it’s typical to perform long-running commands on remote hosts.

With GNU Screen and one supporting script, it’s possible to efficiently perform such operations, by running them asynchronously and receiving an email at the end, all in a single command.

Contents:

• Some GNU Screen concepts
• Purpose and overview of the script
• Script requirements
• Script source
• Script explanation
• Conclusion
• References

Ruby GUI development is a seldom mentioned subject, but it has value. Probably after some Rails development (cough…), developing a desktop tool may be an interesting diversion (or even a requirement).

During the development of my PM-Spotlight desktop application, I evaluated most of the Desktop Ruby GUI toolkits, and prototyped the application with three of them (Shoes 3, FXRuby, and Tk).

This article presents a summary of what I’ve experienced (or gathered) while I was “Developing GUI applications with Ruby”!

Updated on 03/Oct/2019: Added update section about the article archival.

Contents:

• Update
• TL;DR: The summary
• Extension/mistakes
• Frameworks
  • Shoes 3/4
  • FXRuby
  • Ruby-GNOME2
  • qtbindings
  • Tk
  • wxRuby
• Conclusion
• Some references
• Footnotes

It’s very convenient to run service processes (for development purposes!) without admin permissions, rather starting it as system service.

This guide will show how to easily setup PostgreSQL (both via package and binary tarball) to be run by an unprivileged user, with the data in any directory owned by him/her.

Contents:

• Setup notes/requirements
• Installation via apt package (Ubuntu)
• Installation via binary tarball (universal)
• Persisting the PGSQL data location, and adding the binaries to the $PATH
• Conclusion

GitLab offers a functionality for cherry picking a merge request (PR).

This functionality doesn’t exist in GitHub, and in Git, either; it is useful in some cases.

In this article I’ll explain some git fundamentals, and in the last section, how to cherry pick a PR/merge request.

Contents:

• Disclaimer
• What is a git merge
• Rebasing onto a new base
• Finding the merge base
• Cherry-picking a PR/merge request
• Merging the PR
  • Maintaining the PR exactly as it is
  • Changing the PR branch history
• Conclusion

In a project of mine, I’m implementing a feature that runs a background job in order to perform a search; in particular, it needs to support stopping at any time.

There is a variety of strategies to do this in Ruby. In this article I will expose what is the exact outcome of the common strategies, examining how this affects the underlying operating system.

The analysis is targeted to POSIX operating systems, although, at least part of it applies to Windows machines as well.

Contents:

• Brief introduction to Ruby concurrency
• Technical context and preliminary notes
• Problem statement
• Effect of the common strategies on a Linux operating systems
  • Threads, and Thread#kill
  • Kernel#fork
  • Dealing with zombie processes: Process.detach
  • Kernel#spawn
• Introduction to process groups and their usage
  • Non-working usage of process groups
  • Working implementation, using setsid
• Conclusion

This is the Part 3 (of 3) of the shell scripting adventures.

Updated on 11/Oct/2019: Use mapfile for the check list widget returned entries.

The following subjects are described in this part:

• Introduction to Whiptail
• The mysterious redirections (3>&1 1>&2 2>&3)
• Widgets, with snippets
  • Message box
  • Yes/no box
  • Gauge
  • Radio list
  • Check list
  • Password box
• Other widgets
  • Input box
  • Text box
  • Menus

Since Whiptail is simple to use, the objective of this post is rather to show some useful code snippets/patterns.

The examples are taken from my ZFS installer project and RPi VPN Router project installation scripts.

Previous chapters:

• Introduction
• Part 1
• Part 2

This is the Part 2 (of 3) of the shell scripting adventures.

The following subjects are described in this part:

• Awk/sed/perl considerations
• Perl text processing
  • Regex modifiers
  • Replace multiple lines
    • m modifier
    • s modifier
  • Isolating ambiguous group references
  • Printing a matching group (of matching lines)
• Awk text processing
• Progress bars processing with awk (and stdbuf)
  • Processing single-line progress outputs
  • Working around the buffering
  • Streams processing
  • Putting things together

The examples are taken from my RPi VPN Router project installation script.

Previous/following chapters:

• Introduction
• Part 1
• Part 3

This is the Part 1 (of 3) of the shell scripting adventures.

The following subjects are described in this part:

• Associative arrays (hash maps)
• ANSI-C quoting
• Escape strings
• Expand strings into separate options
• Regular expressions matching
• Find a filename’s basename
• Replace the extension of a filename
• Cycle a multi-line variable
• Heredoc

The examples are taken from my RPi VPN Router project installation script.

Previous/Following chapters:

• Introduction
• Part 2
• Part 3

I’ve always thought of shell scripting as a second class scripting form, being awkward and limited. After a deep dive in my RPi VPN router project, I still think it’s awkward and limited, but I do appreciate it as first class choice under specific conditions.

Shell scripting generally can’t be disassociated from system/infrastructure administration, so developing the project has been actually, as a whole, a very interesting and pleasant undertaking.

This post lays the structure of the future posts I’ll publish about the experience.

Following chapters:

• Part 1
• Part 2
• Part 3

Mysql 5.7 added native support for JSON data type. This opens up several interesting possibilities, but it’s not natively supported in Rails 4 (only in v5).

I’ve released a gem, JSON on Rails, for supporting this functionality on Rails 4.

This article describes how the gem works, for those interested in the inner workings, or who want to implement the functionality by themselves.

MySQL 5.7.19 fixes a quite dangerous functionality that causes corruption of a slave when changing the delay (CHANGE MASTER TO MASTER_DELAY=<seconds>) while the slave threads are stopped; since one wouldn’t expect this condition to cause harm, users of such setup should upgrade, if possible.

Users trying to perform the update on Ubuntu 14.04 LTS will face the mysql service not starting.

In my VGA Passthrough guide, I explain how to configure an Ubuntu machine for VFIO.

With the release of QEMU 2.10, some bugs in the OVMF firmware surfaced, which make Windows guests unstable; such bugs have been fixed in the master branch of the EDK II Project repository, so, in order to use QEMU 2.10, it’s required to build the firmware from scratch.

In the vein of the previous article, we’ll examine here the impact of using the ENUM data type.

Such data type is very interesting, although it requires a careful examination, since it has very important design implications.

Recently, we decided to clean our data model, in particular, the OLTP section of our schema. We have a reasonably well structured model, but it falls short when it comes to the data type definitions.

In this article we explore the storage requirements of a (InnoDB) table of ours, and the impact of choosing more strictly defined columns.