Users own files
On Windows you eventually hit “access denied” on a system folder. Linux is more consistent: every file has an owner and a permission set for owner, group, and others. Your home directory is yours. System directories are owned by root. That separation stops a malicious webpage from quietly rewriting system programs - if you are not running as root all day.
Practically: save work in your home folders. When a USB drive mounts, you may need to use the file manager’s “eject” to flush writes before unplugging - same idea as Windows safely remove.
Permission symptoms you will actually see
- Cannot save into a folder you did not create under /usr or /opt
- Script will not run until marked executable
- External drive mounts read-only because the filesystem has errors or is a Windows hibernation hold
- Shared folder on a network needs credentials - not “Linux hates sharing”
Graphical file managers can often open a properties panel to change permissions on files you own. For system files, use the software tools or sudo carefully - do not chmod 777 the universe because a forum said so. That is how security becomes cosplay.
Hidden files
Files starting with a dot are hidden by convention (like .config). Your settings live there. That is why “I deleted everything visible but the app still remembers me” happens. Show hidden files in the file manager when cleaning profiles - and still do not delete folders you do not recognize without a backup.
Disks and paths
Linux mounts drives into the folder tree instead of assigning endless drive letters. Removable media often appears under /media/yourname/. Internal extra disks can be mounted at boot with entries administrators manage - if that sentence already feels heavy, use the disks utility GUI or ask for help rather than hand-editing fstab at midnight.
A wrong fstab line can delay boot or drop you into emergency mode. It is fixable, but it is also a classic self-own. Respect the boot path.
When to stop DIY
When the stack exceeds DIY - drive failures, dual-boot disasters, locked accounts, or a machine that must be online for work tomorrow - contact CCPCREPAIR in Tahlequah. We do diagnostics with a flat quote after we know what is wrong. Call 918-228-5889 or use the form.
← Linux is easy series · All guides · Book a diagnosticField notes from the shop
At CCPCREPAIR in Tahlequah we see the same pattern repeatedly: people succeed with Linux when they slow down for backups, pick a mainstream distro, and treat the first week as landing the plane - updates, browser, printer - before theming and experimental drivers. They fail when they skip the backup, click through erase-disk options, or paste sudo commands they cannot explain.
Keep a live USB of the same distro in a drawer. It is a recovery tool as much as an installer. When something will not boot, the live session is how you copy files off and read logs without making the problem worse. That habit alone separates calm operators from emergency tickets.
If you share a machine with family, write a one-page note: distro name, username model (not the password), whether the disk is encrypted, and where the backups live. Future you - or a technician - will move faster with that sheet than with a vague memory of a YouTube video from three months ago.
Continue the series in order when you can, but jump ahead if you already know the topic. Every page ends with abort criteria and a path to contact the shop when risk climbs. Linux is easy when honesty about hardware and data comes first.