snxraven/ravenscott-blog
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update

Browse Source
This commit is contained in:
Raven Scott
2026-04-06 21:26:12 -04:00
parent 511abb3c59
commit e8dee53272
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
markdown/BareOS: The Seeded Operating System.md
+2 -1
View File
@@ -19,10 +19,11 @@ Most “operating systems” assume a single publisher pushes a monolithic image
The motivating vision is nonetheless sharp. If you believe that **self hosting** and **decentralized distribution** should be first class, then the artifact you boot should be the same replicated structure your friends, colleagues, or fleet operators can obtain without a single CDN choke point. Bare OS is a **P2P first** “system image” in that sense: a **seeder** stages the kernel tree into a system Hyperdrive and publishes a tiny **512 byte MBR** as block zero; a **booter** joins the swarm, reads the MBR, opens the system drive, attaches a separate **personal** Hyperdrive for mutable state, constructs a rich **`ctx`** object, and executes **`/boot/init.js`**. The stack is intentionally aligned with **Holepunch** style runtimes (**Bare** and **Pear**), so the same ecosystem that already thinks in terms of **Hypercore**, **Hyperdrive**, and encrypted streams can reason about an “OS shaped” guest without pretending the guest is Linux. The motivating vision is nonetheless sharp. If you believe that **self hosting** and **decentralized distribution** should be first class, then the artifact you boot should be the same replicated structure your friends, colleagues, or fleet operators can obtain without a single CDN choke point. Bare OS is a **P2P first** “system image” in that sense: a **seeder** stages the kernel tree into a system Hyperdrive and publishes a tiny **512 byte MBR** as block zero; a **booter** joins the swarm, reads the MBR, opens the system drive, attaches a separate **personal** Hyperdrive for mutable state, constructs a rich **`ctx`** object, and executes **`/boot/init.js`**. The stack is intentionally aligned with **Holepunch** style runtimes (**Bare** and **Pear**), so the same ecosystem that already thinks in terms of **Hypercore**, **Hyperdrive**, and encrypted streams can reason about an “OS shaped” guest without pretending the guest is Linux.
Want to try it? Follow this:
<div style="text-align: center;"> <div style="text-align: center;">
Want to try it? Follow this:
`npm i pear -g` `npm i pear -g`
`pear run pear://xc5xw4odfpd7txd1b3xr4u37rfpbjoqtb6zp3xxutgbbmrbtogio` `pear run pear://xc5xw4odfpd7txd1b3xr4u37rfpbjoqtb6zp3xxutgbbmrbtogio`