Written 1 Sep 2026. This is a how-to, not a product card.

See printable text with strings

After od (or after writing a practice file), use strings so you see readable text without dumping every byte. You don't need extra software beyond binutils.

Peek at file bytes showed every character and control marker. Empty or shrink a practice file changed size without deleting the name. Tonight you take a quieter look: ask for the printable runs only. strings walks a file and prints sequences of readable characters. It skips the noise you don't need tonight. That is not printing a whole text file as text. That is read a file without opening the editor. That is not a full byte peek. That is peek at file bytes. That is not searching for a word. That is find a word in a file. You are still only practicing in home on the computer. It does not need hex editors, htop, Grafana, or a NAS for this one job.

Skip until SSH already works

SSH from the couch should already get you a prompt. If you only need to write practice words, that is print words exactly or put a short line into a file. If you only need a full byte peek, that is peek at file bytes. If you only need the text as text, that is read a file without opening the editor. If you only need to change size, that is empty or shrink a practice file. Skip this whole note if you only need a house share other computers browse. That is a folder the house can open.

What this is

strings finds printable character runs inside a file and prints each run on its own line. Tonight that means: you see words you can read, without a full dump of every byte. Default minimum length is usually four characters (tool-dependent). Optional -n sets that minimum. Optional -a scans the whole file the same way on some systems. It does not rewrite the file. It does not invent a checksum. It does not decide the file kind. Those jobs already have their own notes.

Practice strings in home

SSH in. Make sure home is where you sit:

pwd

You want a path that ends in your login name. If not:

cd ~

Park a tiny practice file with a couple of readable lines (see printf):

printf 'hello\nsecret-ish\n' > ~/strings-a.txt

Optional: mix in a gentle non-printable between words (a null byte). Keep it tiny:

printf 'hello\0world\n' > ~/strings-a.txt

Optional peek first (see od):

od -c ~/strings-a.txt

Show printable runs (tonight's job):

strings ~/strings-a.txt

You want lines like hello and secret-ish (or hello and world if you used the null-byte version), then the prompt back. That is enough for tonight: readable text without dumping every byte.

Optional minimum length (same tiny file):

strings -n 4 ~/strings-a.txt

Or bump the floor a little:

strings -n 5 ~/strings-a.txt

Shorter runs drop out. Don't make length tuning the whole lesson. Default is fine for tonight.

Optional whole-file scan flag (lightly, only if your man page mentions it):

strings -a ~/strings-a.txt

On a tiny home practice file this usually looks the same as plain strings. Skip deep flag school.

Debian and Ubuntu usually already have strings from binutils. Don't make apt the lesson. If it is somehow missing:

sudo apt install binutils

Then stop. That install is not a reason to buy a hex editor or a forensic kit.

When you are done practicing:

rm -i ~/strings-a.txt

Ask first. Say yes only if the name matches. That careful delete is delete a file carefully. Skip rm -rf.

Useful extras, still home-safe

Skip strings on /etc, huge binaries, whole disks, or anything outside home. Tonight: one tiny home practice file.

Skip huge binaries as tonight's job. Tonight: a tiny practice file, not firmware images or giant packages.

Skip piping strings into rm. Strings peeks at printable text. Rm deletes. Don't mix those jobs.

Skip hexdump and xxd as tonight's job. Full byte peeks stay on od.

Skip awk, sed, and install as new pages this cycle. Free space is already see if the computer still has room.

Skip dd, shred, screen, tmux, port 22 forwarding, apt as the lesson, htop, Grafana, and a NAS. Keep SSH on the house network: keep the computer on the house network. Don't forward port 22.

What this is not

This is not od. That peeks at every byte: peek at file bytes. It is not truncate. That changes size: empty or shrink a practice file. It is not cat. That prints text as text: read a file without opening the editor. It is not grep. That searches for a word: find a word in a file. It is not file. That guesses the kind of file: see what kind of file this is. It is not cmp. That compares two files: see whether two files match byte for byte. It is not sha256sum. That fingerprints one file: check a file fingerprint. It is not printf or echo. Those write words: print words exactly, put a short line into a file. It is not rm. That removes the name: delete a file carefully. It is not opening SSH to the internet so you can scan files from a coffee shop. That is keep the computer on the house network. Don't forward port 22.

What next

Need a full byte peek first? Peek at file bytes. Need to empty or shrink without deleting the name? Empty or shrink a practice file. Need exact practice words? Print words exactly. Need the text as text? Read a file without opening the editor. Need a fingerprint? Check a file fingerprint. Need the throwaway gone? Delete a file carefully. Keep SSH on the house network: keep the computer on the house network. Don't forward port 22.

Skip

Skip if SSH still fails. Finish SSH from the couch first.
Skip od, truncate, printf, or echo as tonight's job if you only came for printable text. Those notes already exist.
Skip cat, grep, file, cmp, and sha256sum as tonight's job. Link those pages instead.
Skip strings on /etc, huge binaries as the job, and piping strings into rm.
Skip hexdump/xxd as the job (use od), awk/sed/install as new pages this cycle, dd/shred, screen, tmux, apt as the lesson, htop, Grafana, and a NAS.
Skip rm -rf. Careful delete only: delete a file carefully.
Skip opening SSH to the internet. That is keep the computer on the house network. Don't forward port 22.

Sources

Debian: strings(1). Ubuntu: strings(1). GNU binutils: strings. Official pages only. For the byte peek, see peek at file bytes. For size without deleting the name, see empty or shrink a practice file. For exact words, see print words exactly. For a careful delete, see delete a file carefully. For the login, see SSH from the couch.

Also on this topic

SSH from the couchType commands on the computer from your laptop, on the house network. Password login first. Don't open this to the internet. Peek at file bytesAfter writing a practice file, peek with od so you see the characters and bytes that are actually on disk. You don't need extra software beyond coreutils. Empty or shrink a practice fileAfter od, use truncate so you empty or shrink the file without deleting its name. You don't need extra software beyond coreutils. Print words exactlyPrint words exactly with printf so a practice file gets the text you meant, without the extra newline echo always adds. You don't need extra software for this. Put a short line into a fileAfter SSH works, put one short line into a file with echo so you don't need to open nano. You don't need a file manager for this. Read a file without opening the editorAfter SSH works, print a file with cat so you can read it without opening nano. Short files only. You don't need a file viewer for this. Find a word in a fileAfter SSH works, search a file with grep so you see only the matching lines. You don't need a file viewer for this. Delete a file carefullyAfter SSH works, delete one file with rm -i. Ask first. Skip rm -rf. You don't need a NAS for this. See if the computer still has roomBefore you buy a bigger drive, check free space with df. Turn off password login once the key worksAfter the laptop key login is boring, tell SSH to stop accepting the password. The key is how you get in. A keyboard on the computer is the backup now. Keep the computer on the house networkSSH and Pi-hole belong on the house network. Skip this if you never opened the router settings. Don't forward port 22.