Text Manipulation Utilities Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

Case conversion, a line sort that counts unique lines, a byte size in powers of 1024, and a UTC date a number of days ahead are readings. The random string uses the browser random source and says to store it as a secret.

Do not paste the token into the ticket or into git. Do not treat the date tool as a scheduler. One value at a time.

192.0.2.10/24 and example.com are documentation. They stay in the note.

The change you can finish

Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.

Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.

Pick one tool.
Read the result.
Store a token outside the note.
Stop.

Mistakes that outlive the command

Text Manipulation Utilities Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

A token saved in the ticket.
The date treated as a job that was created.
A secret used as the sample text.
Several tools mixed into one change.

Decisions to write down

One decision for Text Manipulation Utilities Guide: One tool. A token is not in the note. No job was created. And the result was read.

Checks before you call it done

Confirm this before you call the change done: The tool is named. The result is written or the token is stored. No token is in the note. No job was created. And the result was read. If one of those fails, stop.

# A random token is a secret.
# Do not file it in the note.
# The date tool does not create a job.

Before you leave the host

Text Manipulation Utilities Guide ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.

192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.

One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.

A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Everyday Utilities for Sysadmins

More in this cluster

The pillar for this page, and the next published pages filed with it.