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
Oracle Linux Commands Cheat Sheet is a reading list for Oracle Linux. Oracle Linux. The kernel you boot, UEK or the compatible kernel, is a choice you write down. It is not Ubuntu, and apt is the wrong command.
A version, a hostname, and the status of one service are the reads. A command that changes the host waits for the how-to that owns that change.
The package tool is dnf. Logs live in the journal, and /var/log/secure for SSH. SELinux stays enforcing. Do not set it permissive to make a service start.
The generator drafts a command. It does not log in. Do not paste a change from this sheet. 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.
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.
- Confirm the hostname.
- Read the version.
- Read the one service or site the ticket names.
- Confirm a rollback copy exists before any later change.
- Do not paste a change from this sheet.
- Hand a change to the how-to for that task.
Mistakes that outlive the command
Oracle Linux commands goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A change command used because it was short.
- The wrong host.
- A secret copied into the note.
- A command from a different platform.
- No note of what you read.
Decisions to write down
One decision for Oracle Linux commands: This sheet is for reading. The platform is Oracle Linux. The hostname matches. Secrets stay out of the note. And the how-to owns any change.
Checks before you call it done
Confirm this before you call the change done: The version was read. The hostname matches. No change was pasted from this page. No secret is in the note. And the next action is a named how-to, or a stop. If one of those fails, stop.
| You may read | You do not treat as safe to paste |
|---|---|
| Version, hostname, and one service status | A full sample from a forum |
| The file or the unit named in the ticket | A second product added because it was on the same page |
| The path of the rollback copy | A password, a key, or a token |
# Read first. Change later, from the how-to.
# Oracle Linux.
# prompt-for-this is not a secret to keep.Before you leave the host
Oracle Linux Commands Cheat Sheet 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.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.