<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Splice on Sanketh's Blog</title><link>https://sankethbk.github.io/blog/tags/splice/</link><description>Recent content in Splice on Sanketh's Blog</description><generator>Hugo -- 0.164.0</generator><language>en-us</language><lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sankethbk.github.io/blog/tags/splice/index.xml" rel="self" type="application/rss+xml"/><item><title>The Pipes</title><link>https://sankethbk.github.io/blog/posts/operating-systems/linux/2026-07-08-pipes/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://sankethbk.github.io/blog/posts/operating-systems/linux/2026-07-08-pipes/</guid><description>&lt;h1 id="the-pipes"&gt;The Pipes&lt;/h1&gt;
&lt;h2 id="file-descriptors"&gt;File Descriptors&lt;/h2&gt;
&lt;p&gt;To understand file descriptors (FDs), you have to look at one of the core design philosophies of Unix and Linux: &amp;ldquo;Everything is a file.&amp;rdquo; Whether a process is interacting with a regular text file, a directory, a hardware device (like a hard drive), a network socket, or an in-memory pipe, the kernel represents all of them as &amp;ldquo;files.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;A file descriptor is simply the lightweight handle that user-space processes use to talk to these files. Here is the low-level architectural breakdown of how they work.&lt;/p&gt;</description></item></channel></rss>