<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bash on Linux Security</title><link>https://linuxtransfer.com/tags/bash/</link><description>Recent content in Bash on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 16 Aug 2026 10:26:56 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/bash/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Duplicate Entries in Your Bash History with a Simple Script</title><link>https://linuxtransfer.com/post/2026-08-16-taming-duplicate-entries-in-your-bash-history/</link><pubDate>Sun, 16 Aug 2026 10:26:56 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-08-16-taming-duplicate-entries-in-your-bash-history/</guid><description>&lt;h2 id="introduction-to-bash-history">Introduction to Bash History&lt;/h2>
&lt;p>As a long-time Linux user, I&amp;rsquo;ve come to rely on the command line to get my work done. The Bash shell is an incredibly powerful tool, and one of its most useful features is its ability to store a history of previously executed commands. This history is stored in the &lt;code>~/.bash_history&lt;/code> file and can be accessed using the &lt;code>history&lt;/code> command. However, as our systems see more use, the Bash history can become cluttered with duplicate entries, making it tough to find the commands we need.&lt;/p></description></item></channel></rss>