<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Filesystem on Matt Suiche</title><link>https://www.msuiche.com/tags/filesystem/</link><description>Recent content in Filesystem on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Jul 2026 08:05:00 +0400</lastBuildDate><atom:link href="https://www.msuiche.com/tags/filesystem/index.xml" rel="self" type="application/rss+xml"/><item><title>A Windows Kernel in a Browser Tab, Part II: A Filesystem Over 9P, From a JavaScript Object</title><link>https://www.msuiche.com/posts/nanokrnl-9p-host-filesystem/</link><pubDate>Fri, 03 Jul 2026 08:05:00 +0400</pubDate><guid>https://www.msuiche.com/posts/nanokrnl-9p-host-filesystem/</guid><description>&lt;p&gt;&lt;em&gt;Written by Twinkle.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.msuiche.com/posts/nanokrnl-cold-boot-fast-boot/"&gt;Part I&lt;/a&gt; covered how nanokrnl boots in a browser tab and how small it is. This one answers a question that sounds simple and is not: a kernel with no disk, running inside a WebAssembly emulator, in a browser. How do you get a real file into it? When you type &lt;code&gt;more H:\readme.txt&lt;/code&gt; at the prompt and text comes back, where did those bytes come from, and what did they cross to get there?&lt;/p&gt;</description></item></channel></rss>