Commands, distributions, and practical Linux guidance
Learning center
Use these guides when a one-line command mapping is not enough. They focus on the mental models that Windows users need when files, packages, permissions, services and the shell behave differently on Linux.
Guides
13 guides
Migration guide
Moving to Linux is easier when you treat it as a staged migration instead of a one-day operating-system replacement. This guide shows how to inventory what you use, test Linux safely, replace Windows-specific workflows and verify that your files and peripherals work before you commit.
Read the full guide →Beginner guide
The Linux shell is not simply Command Prompt with different command names. The biggest gains come from understanding paths, text streams, quoting, help systems and how small tools are combined.
Read the full guide →Filesystem guide
Windows and Linux both organize data into files and directories, but they present storage differently. Understanding the single Linux directory tree, mount points and common system locations prevents many early migration mistakes.
Read the full guide →Permissions guide
Linux permissions are compact and predictable once you separate three questions: who owns the object, which group is associated with it, and what the owner/group/others are allowed to do.
Read the full guide →Software guide
Linux software installation is usually repository-first. The command names differ between distribution families, but the underlying workflow—refresh metadata, install signed packages, resolve dependencies and apply updates—is consistent.
Read the full guide →System administration guide
Windows separates Task Manager, Services, Event Viewer and Task Scheduler into familiar tools. Linux exposes the same underlying ideas through processes, service managers, logs and schedulers, with both graphical and command-line interfaces.
Read the full guide →Networking guide
Windows networking knowledge carries over well to Linux, but the tools and configuration layers are different. This guide maps familiar tasks such as viewing addresses, routes, DNS settings and listening ports to modern Linux tools and shows a safe troubleshooting order.
Read the full guide →Storage guide
Windows users often think in drive letters. Linux presents storage as filesystems mounted into one directory tree. This guide explains the tools that identify devices, show mounted filesystems, measure space and make persistent mounts without guessing at device names.
Read the full guide →Shell guide
PowerShell and Bash are both powerful shells, but they move data differently. PowerShell pipelines commonly pass .NET objects; traditional Unix pipelines pass text and byte streams. Understanding that difference explains many of the syntax and workflow changes Windows users encounter.
Read the full guide →Troubleshooting guide
Linux troubleshooting becomes much easier when you collect evidence before changing configuration. This guide shows where system and service messages live, how systemd journal queries differ from plain log files and how to narrow a problem by time, service and severity.
Read the full guide →Developer guide
A project that works on Windows can expose path, filename, permission and line-ending assumptions when moved to Linux. This guide focuses on the environment differences that most often affect development work.
Read the full guide →Hardware guide
Linux handles drivers differently from the familiar Windows download-and-install model. Many drivers ship with the kernel, while firmware and proprietary graphics components may come from distribution packages. The safest workflow begins by identifying the hardware and reading kernel messages.
Read the full guide →Virtualization guide
Containers and virtual machines solve different problems. Linux users commonly encounter Docker or Podman for containers and KVM/libvirt for full virtualization. This guide explains the layers so Windows users can choose the right tool and troubleshoot the right boundary.
Read the full guide →Use a guide when you are learning a Linux concept or planning a migration decision. Use the command library when you already know the Windows task and need the closest Linux command, options and examples. Use the translator for quick lookup in either direction.