1.2.3.3. Fedora
Table of Contents
Overview
Fedora is a community driven Linux distribution sponsored by Red Hat. It focuses on showcasing modern, cutting edge open source software while still following well defined policies and quality standards. Many technologies that eventually appear in Red Hat Enterprise Linux are first tested and refined in Fedora. This gives Fedora a unique role as both a user friendly desktop system and a proving ground for enterprise features.
Fedora is primarily known for three characteristics. It adopts new software versions quickly, it stays close to upstream projects with minimal modifications, and it has a strong emphasis on free and open source software. For a beginner this means you get access to recent software, a clean and consistent system layout, and very good documentation that often matches upstream guides.
Editions and Use Cases
Fedora is published in several editions that target different use cases. The most common one for new users is Fedora Workstation. This edition is designed for laptops and desktops, and ships with the GNOME desktop by default. It focuses on being easy to install and use, with sensible defaults for everyday tasks such as web browsing, office work, development, and media playback, once you enable the appropriate repositories.
For systems that will not primarily run a graphical desktop there is Fedora Server. This edition is tailored for server workloads and puts tools for managing services and network roles at the center. It still uses the same underlying Fedora base, so software packages and administration tools are familiar if you come from Fedora Workstation.
There are also Fedora Spins and Labs. Spins are alternative desktop variants such as KDE Plasma, XFCE, or LXQt, built on the same Fedora base but with different desktop environments and default applications. Labs are curated collections of software targeted at specific tasks such as scientific computing or security testing. The existence of Spins and Labs lets you pick an environment that matches your hardware and workflow without learning a completely different distribution.
Package Management and Software Sources
Fedora uses the RPM package format with the DNF package manager as its main tool for installing and updating software from repositories. DNF resolves dependencies automatically and integrates with Fedora’s update infrastructure. Although details of package management are handled elsewhere in the course, what is specific to Fedora is the way its repositories are structured and what they prioritize.
Fedora’s official repositories include only free and open source software. This is a deliberate policy decision. As a result certain codecs and proprietary drivers are not available directly from the default repositories. To access those, Fedora users commonly enable third party repositories. Among these, RPM Fusion is widely used for additional free software that Fedora does not ship, and for nonfree software such as proprietary codecs or drivers. This separation keeps the official system strictly open source, while still giving users a path to install restricted software when needed.
In addition to RPM packages, Fedora integrates well with modern universal packaging formats. Flatpak is especially prominent on Fedora Workstation, and the graphical Software application supports installing Flatpak applications with minimal configuration. This provides access to sandboxed desktop applications that can stay up to date independently of the core system.
Release Cycle and Updates
Fedora follows a relatively fast, fixed release cycle. New Fedora versions typically appear about every six months. Each release receives support and security updates until one month after the second following release. In practice this means a single Fedora version is supported for roughly 13 months.
This schedule has a few consequences. Fedora users get new versions of the desktop environment, kernel, and user applications regularly, often earlier than users of more conservative distributions. At the same time, staying on a supported release requires upgrading at least once a year. Fedora provides tools to make upgrades straightforward, and most users can move from one release to the next without reinstalling. However, this pattern suits users who are comfortable applying frequent updates and occasional system upgrades.
Daily updates on Fedora tend to be more frequent and contain newer software builds than on many long term support distributions. This makes Fedora appealing if you want recent compiler versions, development libraries, or desktop features. It may feel less suitable if you prefer an environment that changes as little as possible over time.
System Characteristics and Technology Choices
Fedora generally aims to be close to upstream projects, which means it tries not to carry many Fedora specific patches. Configuration locations, default behaviors, and file layouts often match upstream documentation. This can simplify learning because tutorials written for upstream software usually apply directly.
The distribution often adopts new Linux technologies relatively early. Systemd, Wayland, SELinux, Btrfs as the default filesystem on desktops, and other modern components have been integrated promptly. For a user this means Fedora is a good platform for understanding how contemporary Linux systems operate. It also means you may encounter changes earlier than users of slower moving distributions, such as a new default display protocol or updated configuration tools.
Security is another notable characteristic. Fedora enables SELinux in enforcing mode by default, which adds an extra layer of access control on top of traditional Unix permissions. While the details of SELinux are covered elsewhere, on Fedora you are likely to see it in action more often, including its logs and context labels.
Hardware Support and Proprietary Components
Because Fedora focuses on free and open source software, it does not include proprietary drivers and firmware beyond what is permitted by its licensing policies. On modern hardware this usually still results in a functional system, especially for most CPUs, chipsets, and many network devices. However, certain graphics cards and wireless adapters may work better with proprietary drivers, which are not directly available in Fedora’s default setup.
Fedora users often address this by enabling third party repositories and vendor provided software where needed. Out of the box, Fedora Workstation offers an option to enable some third party sources during installation or first boot, which can simplify installation of proprietary applications such as popular communication tools or hardware specific utilities.
This approach can influence how suitable Fedora feels, depending on your hardware and tolerance for extra configuration. If your hardware is well supported by open source drivers, Fedora can offer a clean and cohesive experience. If you rely heavily on proprietary drivers, you might need to perform some additional steps after installation.
Community and Documentation
Fedora has an active community that includes both volunteers and Red Hat employees. Development is organized through open processes, with public mailing lists, issue trackers, and special interest groups. Decisions about system defaults and packaging policies are documented and discussed openly, which can be helpful if you want to understand why certain choices were made.
Documentation for Fedora is relatively complete and is published through official websites and wikis. New releases come with updated release notes that summarize major changes, new features, and known issues. This can be especially valuable because Fedora evolves quickly, so reading the notes for each version can prevent surprises during upgrades.
The community also offers user support through forums, chat channels, and question and answer platforms. Because Fedora is quite close to Red Hat Enterprise Linux in many technical aspects, learning Fedora can also prepare you for environments where Red Hat based systems are used, even though their goals and lifecycles differ.
When Fedora Might Be the Right Choice
Fedora is a good fit if you want a desktop or workstation system that gives you new open source software shortly after it is released, and if you are comfortable performing regular system upgrades. It is especially attractive for developers, system enthusiasts, and users who want to learn technologies that are common in enterprise Linux deployments, while still having a distribution suitable for daily personal use.
For beginners, Fedora Workstation provides a polished GNOME based environment and a straightforward installer. The main tradeoffs are the relatively short support period for each release and the need to understand how to obtain proprietary codecs or drivers when required. If you like the idea of a modern, open source focused distribution that stays close to upstream projects, Fedora is a strong candidate to consider.
Views: 0
Where to Move
Move chapter:
- ☰ 1. PART I — Linux Fundamentals (Beginner)
- ☰ 1.1. What Is Linux?
- ☰ 1.1.1. What is an operating system
- ☰ 1.1.2. History of Unix and Linux
- ☰ 1.1.3. The Linux kernel
- ☰ 1.1.4. GNU and the Free Software Foundation
- ☰ 1.1.5. Open source philosophy
- ☰ 1.1.6. Where Linux is used today
- ☰ 1.1.7. Desktop vs server vs embedded Linux
-
- ☰ 1.2. Choosing a Linux Distribution
- ☰ 1.2.1. What is a distribution?
- ☰ 1.2.2. Package formats (deb, rpm, pacman)
- ☰ 1.2.3. Popular distributions
- ☰ 1.2.3.1. Ubuntu
- ☰ 1.2.3.2. Debian
- ☰ 1.2.3.3. Fedora
- ☰ 1.2.3.4. Arch Linux
- ☰ 1.2.3.5. openSUSE
-
- ☰ 1.2.4. Rolling vs fixed release
- ☰ 1.2.5. Choosing the right distribution
-
- ☰ 1.3. Installing Linux
- ☰ 1.3.1. Creating a bootable USB
- ☰ 1.3.2. Installing on real hardware
- ☰ 1.3.3. Dual booting with Windows
- ☰ 1.3.4. Installing in a virtual machine
- ☰ 1.3.5. Partitioning
- ☰ 1.3.5.1. `/` (root)
- ☰ 1.3.5.2. `/home`
- ☰ 1.3.5.3. Swap
-
- ☰ 1.3.6. First-time setup
-
- ☰ 1.4. First Steps After Installation
- ☰ 1.4.1. Desktop environment basics
- ☰ 1.4.2. Updating the system
- ☰ 1.4.3. Installing essential tools
- ☰ 1.4.4. Setting up drivers
- ☰ 1.4.5. Using the software center
-
- ☰ 1.5. Linux Filesystem Hierarchy
- ☰ 1.5.1. Overview of the root filesystem
- ☰ 1.5.2. Important directories
- ☰ 1.5.2.1. `/etc`
- ☰ 1.5.2.2. `/var`
- ☰ 1.5.2.3. `/usr`
- ☰ 1.5.2.4. `/tmp`
- ☰ 1.5.2.5. `/dev`
- ☰ 1.5.2.6. `/proc`
- ☰ 1.5.2.7. `/sys`
-
- ☰ 1.5.3. File types
- ☰ 1.5.4. Absolute vs relative paths
-
- ☰ 1.6. The Linux Graphical Environment
- ☰ 1.6.1. GNOME
- ☰ 1.6.2. KDE Plasma
- ☰ 1.6.3. XFCE
- ☰ 1.6.4. File managers
- ☰ 1.6.5. System settings
- ☰ 1.6.6. Workspaces and window management
-
-
- ☰ 2. PART II — Command Line Essentials
- ☰ 2.1. Terminal and Shell Basics
- ☰ 2.1.1. What is a shell?
- ☰ 2.1.2. Bash vs Zsh vs Fish
- ☰ 2.1.3. Command structure
- ☰ 2.1.4. Environment variables
- ☰ 2.1.5. Getting help
- ☰ 2.1.6. Command history and autocomplete
-
- ☰ 2.2. Files and Directories
- ☰ 2.2.1. Listing files
- ☰ 2.2.2. Navigating directories
- ☰ 2.2.3. File operations
- ☰ 2.2.4. Wildcards and globbing
- ☰ 2.2.5. Searching files
-
- ☰ 2.3. Viewing and Editing Text Files
- ☰ 2.3.1. Viewing tools
- ☰ 2.3.2. Editing with nano
- ☰ 2.3.3. Introduction to vim
- ☰ 2.3.4. Input/output redirection
-
- ☰ 2.4. Users, Permissions, and Ownership
- ☰ 2.4.1. Users and groups
- ☰ 2.4.2. Permission types (r, w, x)
- ☰ 2.4.3. Changing permissions
- ☰ 2.4.4. Changing ownership
- ☰ 2.4.5. Using sudo
-
- ☰ 2.5. Package Management
- ☰ 2.5.1. Software repositories
- ☰ 2.5.2. APT (Debian/Ubuntu)
- ☰ 2.5.3. DNF (Fedora/RHEL)
- ☰ 2.5.4. Pacman (Arch Linux)
- ☰ 2.5.5. Snap, Flatpak, AppImage
- ☰ 2.5.6. System upgrades
-
- ☰ 2.6. Working with Processes
- ☰ 2.6.1. What is a process?
- ☰ 2.6.2. Viewing processes
- ☰ 2.6.3. Killing processes
- ☰ 2.6.4. Foreground and background jobs
- ☰ 2.6.5. System services and daemons
-
- ☰ 2.7. Introduction to Shell Scripting
- ☰ 2.7.1. Writing your first script
- ☰ 2.7.2. Variables
- ☰ 2.7.3. Conditionals
- ☰ 2.7.4. Loops
- ☰ 2.7.5. Functions
- ☰ 2.7.6. Making scripts executable
-
-
- ☰ 3. PART III — Intermediate System Administration
- ☰ 3.1. Systemd and Service Management
- ☰ 3.1.1. What is systemd?
- ☰ 3.1.2. Managing services (systemctl)
- ☰ 3.1.3. Boot targets
- ☰ 3.1.4. System logs (journalctl)
- ☰ 3.1.5. Creating custom services
-
- ☰ 3.2. Storage and Filesystems
- ☰ 3.2.1. Devices and partitions
- ☰ 3.2.2. Filesystems (EXT4, XFS, Btrfs)
- ☰ 3.2.3. Mounting and unmounting
- ☰ 3.2.4. Disk usage tools
- ☰ 3.2.5. Archiving and compression (tar, gzip, xz)
-
- ☰ 3.3. Networking Fundamentals
- ☰ 3.3.1. IP addressing
- ☰ 3.3.2. Subnets and routing
- ☰ 3.3.3. DNS and hostnames
- ☰ 3.3.4. Networking tools (ip, ss, ping)
- ☰ 3.3.5. Editing network configuration files
-
- ☰ 3.4. User and Group Administration
- ☰ 3.4.1. User information files
- ☰ 3.4.2. Creating and removing users
- ☰ 3.4.3. Password policies
- ☰ 3.4.4. Managing groups
- ☰ 3.4.5. Shell configuration
-
- ☰ 3.5. System Monitoring
- ☰ 3.5.1. CPU and memory monitoring
- ☰ 3.5.2. Disk and I/O monitoring
- ☰ 3.5.3. Log files in /var/log
- ☰ 3.5.4. Boot performance
- ☰ 3.5.5. Monitoring running services
-
- ☰ 3.6. Backup and Restore
- ☰ 3.6.1. Backup strategies
- ☰ 3.6.2. Using rsync
- ☰ 3.6.3. Creating tar archives
- ☰ 3.6.4. Using snapshot systems
- ☰ 3.6.5. Automating backups
-
- ☰ 3.7. Basic System Security
- ☰ 3.7.1. Firewalls (UFW, firewalld)
- ☰ 3.7.2. Authentication policies
- ☰ 3.7.3. SSH security basics
- ☰ 3.7.4. SELinux and AppArmor overview
- ☰ 3.7.5. Intrusion detection basics
-
-
- ☰ 4. PART IV — Advanced Linux Skills
- ☰ 4.1. Advanced Shell Scripting
- ☰ 4.1.1. Script structure
- ☰ 4.1.2. Error handling
- ☰ 4.1.3. Debugging scripts
- ☰ 4.1.4. Scheduled tasks (cron)
-
- ☰ 4.2. The Linux Boot Process
- ☰ 4.2.1. BIOS vs UEFI
- ☰ 4.2.2. Understanding GRUB2
- ☰ 4.2.3. Kernel loading
- ☰ 4.2.4. initramfs
- ☰ 4.2.5. Troubleshooting boot issues
-
- ☰ 4.3. Kernel Management
- ☰ 4.3.1. What is the kernel?
- ☰ 4.3.2. Kernel modules
- ☰ 4.3.3. Kernel parameters
- ☰ 4.3.4. Compiling a custom kernel
- ☰ 4.3.5. Kernel versioning and updates
-
- ☰ 4.4. Advanced Filesystems and Storage
- ☰ 4.4.1. LVM concepts
- ☰ 4.4.2. Logical volumes
- ☰ 4.4.3. RAID levels
- ☰ 4.4.4. Full disk encryption (LUKS)
- ☰ 4.4.5. Snapshots and rollbacks
-
- ☰ 4.5. Network Services
- ☰ 4.5.1. SSH server configuration
- ☰ 4.5.2. NFS
- ☰ 4.5.3. Samba
- ☰ 4.5.4. FTP/SFTP
- ☰ 4.5.5. Firewalls in depth
-
- ☰ 4.6. Logging and Auditing
- ☰ 4.6.1. Systemd logging
- ☰ 4.6.2. Traditional logs in /var/log
- ☰ 4.6.3. Auditd
- ☰ 4.6.4. Log rotation
- ☰ 4.6.5. Creating custom logs
-
- ☰ 4.7. Virtualization and Containers
- ☰ 4.7.1. Virtual machines (KVM/QEMU)
- ☰ 4.7.2. Linux containers (LXC/LXD)
- ☰ 4.7.3. Docker fundamentals
- ☰ 4.7.4. Podman vs Docker
- ☰ 4.7.5. Container networking
-
-
- ☰ 5. PART V — Server Administration (Expert)
- ☰ 5.1. Web Servers
- ☰ 5.1.1. Apache basics
- ☰ 5.1.2. Nginx basics
- ☰ 5.1.3. Virtual hosts
- ☰ 5.1.4. SSL/HTTPS
- ☰ 5.1.5. Reverse proxy concepts
-
- ☰ 5.2. Database Servers
- ☰ 5.2.1. MySQL/MariaDB
- ☰ 5.2.2. PostgreSQL
- ☰ 5.2.3. Database backup strategies
- ☰ 5.2.4. Database hardening
-
- ☰ 5.3. Email Services
- ☰ 5.3.1. SMTP fundamentals
- ☰ 5.3.2. Configuring Postfix
- ☰ 5.3.3. IMAP/POP3 with Dovecot
- ☰ 5.3.4. Spam filtering systems
- ☰ 5.3.5. Email routing concepts
-
- ☰ 5.4. DNS and DHCP
- ☰ 5.4.1. Understanding DNS
- ☰ 5.4.2. Setting up BIND
- ☰ 5.4.3. DNS zones and records
- ☰ 5.4.4. DHCP server configuration
- ☰ 5.4.5. DNS troubleshooting
-
- ☰ 5.5. Load Balancing
- ☰ 5.5.1. HAProxy fundamentals
- ☰ 5.5.2. Nginx as a load balancer
- ☰ 5.5.3. Session persistence
- ☰ 5.5.4. High availability concepts
-
- ☰ 5.6. Clustering and High Availability
- ☰ 5.6.1. Failover principles
- ☰ 5.6.2. Pacemaker
- ☰ 5.6.3. Corosync
- ☰ 5.6.4. Cluster resource management
- ☰ 5.6.5. Distributed filesystems
-
-
- ☰ 6. PART VI — DevOps and Cloud
- ☰ 6.1. Linux for Developers
- ☰ 6.1.1. Compiler toolchains (gcc, make)
- ☰ 6.1.2. Git fundamentals
- ☰ 6.1.3. Debugging tools (gdb, strace)
- ☰ 6.1.4. Build automation (Makefile, CMake)
-
- ☰ 6.2. DevOps on Linux
- ☰ 6.2.1. CI/CD principles
- ☰ 6.2.2. YAML basics
- ☰ 6.2.3. GitHub Actions
- ☰ 6.2.4. GitLab CI/CD
- ☰ 6.2.5. Automated testing
-
- ☰ 6.3. Configuration Management
- ☰ 6.3.1. Ansible basics
- ☰ 6.3.2. Playbooks and inventories
- ☰ 6.3.3. Puppet overview
- ☰ 6.3.4. Chef overview
-
- ☰ 6.4. Infrastructure as Code
- ☰ 6.4.1. Terraform fundamentals
- ☰ 6.4.2. Providers and resources
- ☰ 6.4.3. Modules
- ☰ 6.4.4. Cloud provisioning with Terraform
-
- ☰ 6.5. Cloud Computing with Linux
- ☰ 6.5.1. Linux on AWS
- ☰ 6.5.2. Linux on Azure
- ☰ 6.5.3. Linux on GCP
- ☰ 6.5.4. Cloud networking basics
- ☰ 6.5.5. Scaling and monitoring
-
-
- ☰ 7. PART VII — Master Topics
- ☰ 7.1. Hardening a Linux System
- ☰ 7.1.1. Hardening principles
- ☰ 7.1.2. Kernel hardening
- ☰ 7.1.3. File integrity monitoring
- ☰ 7.1.4. Vulnerability scanning
-
- ☰ 7.2. Forensics and Incident Response
- ☰ 7.2.1. Collecting evidence
- ☰ 7.2.2. Log and file recovery
- ☰ 7.2.3. Analyzing suspicious processes
- ☰ 7.2.4. Incident response workflow
-
- ☰ 7.3. Performance Tuning
- ☰ 7.3.1. CPU tuning
- ☰ 7.3.2. Memory tuning
- ☰ 7.3.3. Disk and I/O optimization
- ☰ 7.3.4. Profiling tools
-
- ☰ 7.4. Writing Linux Tools
- ☰ 7.4.1. Bash-based tools
- ☰ 7.4.2. Python command-line tools
- ☰ 7.4.3. Writing tools in C
- ☰ 7.4.4. Using Linux system APIs
-
- ☰ 7.5. Linux Internals
- ☰ 7.5.1. Process lifecycle
- ☰ 7.5.2. Memory management
- ☰ 7.5.3. Signals and IPC
- ☰ 7.5.4. Namespaces
- ☰ 7.5.5. cgroups
-
- ☰ 7.6. Becoming a Linux Expert
- ☰ 7.6.1. Career paths
- ☰ 7.6.2. Certifications (RHCE, LFCS, LPIC)
- ☰ 7.6.3. Building a homelab
- ☰ 7.6.4. Contributing to open source
-
-
Comments
Please login to add a comment.
Don't have an account? Register now!