<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unix on cloudmato.com</title><link>https://cloudmato.com/tags/unix/</link><description>Recent content in Unix on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Mon, 15 Jun 2026 12:21:31 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/unix/index.xml" rel="self" type="application/rss+xml"/><item><title>The History Behind 10 Unix Commands You Use Every Day</title><link>https://cloudmato.com/posts/top-10-unix-commands-history/</link><pubDate>Mon, 15 Jun 2026 12:21:31 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/top-10-unix-commands-history/</guid><description>&lt;p&gt;I type &lt;code&gt;ls&lt;/code&gt;, &lt;code&gt;cd&lt;/code&gt;, and &lt;code&gt;grep&lt;/code&gt; probably a few hundred times a day. Never once, in 8+ years of doing this, did I stop to wonder where these tiny two-and-three letter words actually came from. Turns out, almost every single one of them has a story — some guy at Bell Labs in the early 1970s, working on a machine slower than your smartwatch, solving a problem he had &lt;em&gt;that exact day&lt;/em&gt;. Let&amp;rsquo;s go through ten of the most-used Unix commands and dig into why they exist.&lt;/p&gt;</description></item></channel></rss>