5. Next-Gen Containers: Using Podman Instead of Docker

 

Briefing: Containerization is a critical skill, but CentOS Stream ships with Podman natively instead of Docker. The best part? Podman runs without requiring root access, making your server significantly more secure out of the box.

Detailed Explanation:

While Docker revolutionized containers, it traditionally relies on a central daemon running as the root user. If that daemon is compromised, the whole server is at risk. CentOS Stream natively integrates Podman and Buildah as modern, secure alternatives.

Why Podman Wins for Beginners:

1. It is a Drop-in Replacement: Podman uses the exact same commands as Docker. You can literally set an alias (alias docker=podman) and keep using commands like docker run or docker ps without learning a new syntax.

2. Rootless Containers: You can deploy and manage containers as a standard, non-privileged user. If an attacker breaks out of the container, they only gain access to your standard user account, keeping the root system safe.

3. Daemonless Architecture: There is no background service running constantly. Containers only run when you execute them, saving system resources.

Learning Podman on CentOS Stream prepares you for modern enterprise container orchestration in a highly secure way.

4. Managing Services Like a Pro with Systemd

 Briefing: systemd is the beating heart of modern CentOS. It manages everything from starting your database on boot to keeping your network running. Mastering it is non-negotiable for new system administrators.

Detailed Explanation: When a web server fails to start, knowing how to interact with systemd is the difference between a five-minute fix and a two-hour headache. The primary tool you will use is systemctl.

The Core Workflow:

• sudo systemctl start [service] – Starts a service immediately.

• sudo systemctl enable [service] – Tells the service to start automatically every time the server boots.

• sudo systemctl status [service] – The most important command. It tells you if the service is running, if it crashed, and displays the most recent log entries.

Viewing Logs with Journalctl: systemd handles logging natively. If systemctl status doesn't give you enough information about a crash, type sudo journalctl -u [service]. This isolates the logs for that specific service, allowing you to easily read through its history and identify exactly what went wrong.

3. Taming the Beast: A Beginner's Guide to SELinux

 Briefing: Security-Enhanced Linux (SELinux) is notorious for causing headaches for beginners, leading many to instantly disable it. Here is why you should keep it on and how to troubleshoot it without pulling your hair out.

Detailed Explanation: SELinux is a security architecture built into the Linux kernel that enforces Mandatory Access Control. It ensures that if a service (like a web server) gets compromised by a hacker, the attacker is strictly contained and cannot take over the rest of your system.

Because it is so strict, SELinux will silently block services if file permissions or contexts are wrong.

How to Troubleshoot Instead of Disabling:

1. Check the Status: Run sestatus. It should say "Enforcing".

2. Test Temporarily: If a service isn't working, run sudo setenforce 0 to put SELinux into "Permissive" mode (it logs errors but doesn't block them). If your service suddenly works, you know SELinux is the culprit. Always run sudo setenforce 1 immediately after testing.

3. Read the Logs: Use sealert -a /var/log/audit/audit.log. This tool translates cryptic security logs into plain English and often provides the exact command you need to run to fix the blockage.

2. Ditch yum and Master dnf for Package Management

 Briefing: While many older guides still use yum, the modern standard for installing and managing software on CentOS Stream is dnf. Here is how to use it effectively.

Detailed Explanation: Package managers handle the heavy lifting of downloading, installing, and updating software. On modern CentOS releases, dnf (Dandified YUM) is the default package manager. It is faster, uses less memory, and resolves dependencies much better than its predecessor.

Essential dnf Commands:

• sudo dnf update – Updates all installed packages to their latest versions.

• sudo dnf search [name] – Searches the repositories for a specific software package.

• sudo dnf install [package_name] – Installs the software and any required dependencies.

• sudo dnf remove [package_name] – Uninstalls software.

The Pro Tip: Application Streams CentOS Stream features modular streams. In the past, you were stuck with whatever version of a programming language (like Python or Node.js) shipped with the OS. Now, you can use dnf module list to see different supported versions of the same software and choose exactly which stream to install, keeping your development environments flexible without breaking base system dependencies.

1. The New Era of CentOS: Understanding CentOS Stream

 Briefing: CentOS has fundamentally changed. It is no longer a downstream clone of Red Hat Enterprise Linux (RHEL)—it is the upstream version. Here is what that means for your servers and how it compares to alternatives like Rocky Linux and AlmaLinux.

Detailed Explanation: If you are reading older Linux tutorials, they likely refer to CentOS Linux, which officially reached its End of Life on June 30, 2024. Today, we have CentOS Stream.

In the past, CentOS was a free replica built after RHEL releases. Now, CentOS Stream is a continuous delivery platform that sits ahead of RHEL. It acts as a proving ground where future RHEL features and updates are tested.

What does this mean for beginners?

• Rolling Updates: You get faster access to new features, bug fixes, and security patches.

• Development Focus: It is excellent for developing and testing applications that will eventually run on enterprise RHEL environments.

• The Alternatives: If you need the old "1:1 exact RHEL clone" experience for highly stable production workloads, the community has built excellent alternatives like Rocky Linux (created by the original CentOS founder) and AlmaLinux.

If you are learning modern Linux administration, starting with CentOS Stream gives you a sneak peek into the future of the enterprise Linux ecosystem.

What is LiveCD?

A live CD can be used for a quick demo or test of Ubuntu. Try Ubuntu without any changes to your machine! Windows or whatever you use normally is unaffected after trying this and then rebooting. 

The standard Ubuntu Cd can be used as a LiveCd as well as an installer. Live mode is the default option when booting from CD. Only some of the non-standard downloads (such as the "Alternate Cd") lack this functionality. Windows users might be familiar with the term 'boot CD' or 'bootable CD' or 'Recovery/Restore Media'. A "LiveCD" is more than that because it gives the option of running a normal desktop environment with all the normal programs and some extras. A LiveCD usually finds your wired internet connection and Firefox should be able to surf the internet into here. 

This guide has screen-shots of the 8.04 and 10.04 Desktop Edition of Ubuntu. However, Lubuntu, Xubuntu, Kubuntu and even unofficial Ubuntu-based distros as well as other versions all tend to have similar screens & menus. 

Most distributions (versions or "distros" of Linux) have this LiveCd functionality on their installer CD, a few have a separate Cd to download. It is rare to find a distro that has no LiveCd session at all. Ubuntu tries to make their LiveCD the easiest to use. Although a LiveCD session is a good way to demo Ubuntu without making changes to a machine, a LiveCD will always be slower than a proper installation to the hard-drive. Cd-drives & Dvd-drives are physically slower than hard drives. 

You can use a persistent image to keep data & settings safe after shut-down. This does go against many reasons for using a LiveCd session (rather than an installation) but it can be useful for multi-user machines, such as offices or in third world education projects.

Reasons for Using a LiveCD Session

LiveCD sessions are good to:

• give a 'demo' session on a machine before installing or upgrading 
  • checks hardware works as expected 
  • check the look & feel of the distro
• repair or preparation for awkward installations 
  • repair/replace/install grub perhaps after (re)installing Windows
  • fix Windows problems on a machine that doesn't have a dual-boot
  • anti-virus problems on a Windows system 
  • data recovery 
  • resizing partitions to give Ubuntu more (or less) room
  • adding a new partition(s) to your hard-drive for other distros or for a new Windows
• preparing a machine for installing Ubuntu, if you are shy of using default or automatic settings or if the hardware is too unique or awkward
• 'showing off' Ubuntu to people on their own machine
• using on a random computer where access is limited
• a familiar desktop environment on an unfamiliar machine 
• safely using a computer which seems to have poor security or lacks privacy. This is particularly good if you have a Usb stick or something to save your data and settings on (see 'persistent image')

clipboard / GLIPPY / Glipper / ClipIt / Diodon / klipper / parcellite Installation

What is Clipboard?
The Clipboard is a temporary storage area for information that you have copied or moved from one place and plan to use somewhere else. You can select text or graphics and then use the Cut or Copy commands to move your selection to the Clipboard, where it will be stored until you use the Paste command to insert it elsewhere. For example, you might want to copy a section of text from a website, and then paste that text into an e‑mail message.

Different OS users different clipboards and for CentOS the name of the software is parcellite.

Parcellite is a stripped down, basic-features-only clipboard manager with a
small memory footprint for those who like simplicity. In GNOME and Xfce the clipboard manager will be started automatically. For other desktops or window managers you should also install a panel with a system tray or notification area if you want to use this package.

Parcellite has both 32 bit and 64 bit packages

CentOS 32 bit : parcellite-0.9-1.el6.rf.i686.rpm
CentOs 64 bit  : parcellite-0.9-1.el6.rf.x86_64.rpm


Download Link :

CentOS 32 bit  : http://apt.sw.be/redhat/el6/en/i386/rpmforge/RPMS/parcellite-0.9-1.el6.rf.i686.rpm

CentOS 64 bit  : http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/parcellite-0.9-1.el6.rf.x86_64.rpm


Once downloaded, double click the rpm and install it using package management software or use command line. If using package management, the yum will repositories will be working and so the dependencies will be automatically be installed.