<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ubuntu Administration on MeerStory</title><link>https://linux.meerstory.com/categories/ubuntu-administration/</link><description>Recent content in Ubuntu Administration on MeerStory</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 13 Oct 2026 02:08:04 +0900</lastBuildDate><atom:link href="https://linux.meerstory.com/categories/ubuntu-administration/index.xml" rel="self" type="application/rss+xml"/><item><title>Reporting Bash Bugs on Ubuntu with bashbug: Full Guide</title><link>https://linux.meerstory.com/ubuntu/20261013_020548_58/</link><pubDate>Tue, 13 Oct 2026 02:08:04 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261013_020548_58/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>When unexpected shell glitches arise on Ubuntu, GNU provides a built-in diagnostic utility called &lt;code>bashbug&lt;/code> to bundle and dispatch comprehensive environment data straight to the upstream maintainers. This walkthrough explores how &lt;code>bashbug&lt;/code> operates under the hood, demonstrating how to generate pre-filled issue templates, inspect vital compilation flags, and safely export reports to local storage without unintentionally firing off emails.&lt;/p>
&lt;h2 id="1-locating-the-bashbug-executable-and-inspecting-the-local-bash-environment">1. Locating the bashbug Executable and Inspecting the Local Bash Environment&lt;/h2>
&lt;p>Begin by querying the filesystem to determine where the diagnostic binary resides using &lt;code>which bashbug&lt;/code>.&lt;br>
Standard Ubuntu distributions package this utility directly within &lt;code>/usr/bin/bashbug&lt;/code>.&lt;br>
⚙️ [Command-Line Arguments]&lt;/p></description></item><item><title>Lock Ubuntu Package Versions &amp; Manage Dependencies with apt-mark</title><link>https://linux.meerstory.com/ubuntu/20261012_014920_46/</link><pubDate>Mon, 12 Oct 2026 01:50:16 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261012_014920_46/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Maintaining production stability on Debian-based platforms frequently demands pinning critical software versions to avoid breaking changes during routine system upgrades. Similarly, keeping server environments tidy requires fine-grained control over which components count as direct requirements versus transient dependencies. This guide explores the capabilities of &lt;code>apt-mark&lt;/code>—a built-in maintenance utility that lets system administrators lock specific package builds in place, inspect installation metadata, and reclassify packages between automated and manual installation tiers to safeguard infrastructure reliability.&lt;/p></description></item><item><title>Mastering Ubuntu PPAs</title><link>https://linux.meerstory.com/ubuntu/20261010_021207_30/</link><pubDate>Sat, 10 Oct 2026 02:13:50 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261010_021207_30/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Canonical ships stable, thoroughly tested software stacks in the standard Ubuntu repositories, but upstream projects often release critical updates and newer versions long before they reach standard distribution channels. Personal Package Archives (PPAs) bridge this gap. This guide breaks down how the &lt;code>add-apt-repository&lt;/code> utility operates under the hood, demonstrates how to integrate third-party Launchpad archives seamlessly, resolves the ubiquitous &amp;ldquo;command not found&amp;rdquo; error in minimal setups, and details the proper workflow for safely purging repositories to maintain long-term system integrity.&lt;/p></description></item></channel></rss>