Daily driver account
Use a normal user for email and browsing. That account can request admin powers via sudo or a graphical password prompt when installing software. Living as root full-time is like duct-taping the key in the ignition and leaving the truck running in a parking lot.
Create separate accounts for kids or roommates when they need isolation. Guest sessions exist on some desktops for short-term use.
Password habits that transfer from Windows
Long unique passphrases beat clever substitutions. Use a password manager. Enable disk encryption on laptops. Turn on the screen lock. These are not Linux-specific morals - they are how you keep a lost backpack from becoming an identity incident.
If you use FIDO2 hardware keys for web accounts, keep a backup factor documented. Pair shop work on Swissbit keys with Linux desktops when you want phishing-resistant admin logins - see our Swissbit page and hardware keys guide.
sudo etiquette
Read the command. Check you are in the right directory. Prefer tools that ask once per logical action over chains of opaque one-liners. If a command wants to purge half your desktop environment, stop.
Forgot the password? Recovery depends on whether the disk is encrypted and whether you have another admin user. That is a support scenario - do not factory-reset over the only copy of homework.
Shared family machines
Standard accounts for everyone, admin for the adult who does updates. Browser profiles per person. Discuss “do not download random installers” the same way you would on Windows. Linux reduces some malware paths; it does not remove social engineering.
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.