macOS for Beginners

Yes. Underneath the desktop, macOS runs Darwin, a certified Unix core built on BSD foundations. You can confirm it yourself by opening the Terminal and running uname -a; the first word of the output is Darwin. Because of this, the same command-line skills professionals use on Linux servers work directly on your Mac.

Press Command and Space to open Spotlight, type Terminal and press Return. A window with a text prompt appears, running zsh, the shell macOS uses by default. From there you can type commands such as pwd to see where you are, ls -la to list files, and sw_vers to check your macOS version.

They are the three main macOS guardrails. Gatekeeper checks that an app is from a trusted, signed source before it runs. SIP, System Integrity Protection, keeps the core system files read-only even for an administrator. TCC, Transparency Consent and Control, is the privacy layer that makes apps ask before using your camera, microphone or folders.

Use sudo rarely and only after you understand the command. It runs the next command with administrative rights for a moment, temporarily setting the guardrails aside, then power drops back down. A command you do not understand, run with sudo, can do real harm, so read it first, check its man page, and elevate only when a task genuinely needs system-level power.

No. macOS is Unix, so paths use forward slashes and start from a single root written as /. There are no drive letters; a plugged-in disk appears under /Volumes. Your personal space is your home folder at /Users/you, which the Terminal abbreviates as a tilde, so ~/Desktop means /Users/you/Desktop.

Permission denied comes from classic Unix file permissions: the file or folder belongs to another account, often root, and sudo could change that. Operation not permitted comes from a macOS protection layer on top, such as SIP for system areas or TCC privacy for folders like Mail, and sudo does not get past it.