HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
froggey
Mezzano
Common Lisp2015–2025
froggey / Mezzano

Mezzano

An operating system written in Common Lisp

53Distinct people
78Mentions
0Explicit recommenders
3.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An operating system written in Common Lisp

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year78 dated mentions

Observed mentions: 2015-01-27 19:30:44 UTC to 2025-08-24 11:35:35 UTC.

0369122015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC523
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC523
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC716
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC725
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC12210
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC817
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1129
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC10010
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC725
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC514

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Mezzano, an operating system written in Common Lisp. Pre-built images Demo releases are available through GitHub. These releases are designed to be run in VirtualBox, though QEMU is also supported. 2GB of RAM, a virtio-net NIC and an Intel HDA audio controller are recommended. x86-64 images are published. AArch64 has been made to work on some hardware. But to set expectations: making Mezzano run on any given piece of hardware or emulator is still typically a project that requires the user to dig into the code. Building from source See the MBuild repo: (https://github.com/froggey/MBuild) For help & support or to follow development, join the #mezzano IRC channel on Libera Chat (irc.libera.chat) Major changes since Demo 4 USB stack by fittestbits Improved overall file system support by fittestbits EXT2/3/4 support has been implemented by Bruno Cichon (ebrasca) GMA950 modesetting display driver Hardware accelerated 3D support via qemu's Virgl device Multicore/SMP support Improved atomic operations Async APIs: wait-for-objects, dispatch, and thread pools Networking improvements: Server support, DHCP, TCP retransmit Source locations are tracked for many kinds of definitions Weak hash tables and other weak objects Cleanup of object representation and unifcation of standard-object/structure-object Unboxed structure slots Short floats implemented using IEEE half floats Unboxed (unsigned-byte 64) arithmetic Stack overflows and memory faults are trapped and can be recovered from Support for building on Windows Major improvements to CLOS and MOP conformance Keymap picker More bug fixes, performance improvements and features Major changes since Demo 3 FAT32 support has been implemented by Bruno Cichon (ebrasca). McCLIM has been ported by fittestbits. Quicklisp has been ported by Peter S. Housel. Improved introspection tools: DISASSEMBLE and ED have been implemented. Generational collection has been added to the garbage collector. New SSA-based compiler backend, supporting unboxed value representations. Gray streams support has been overhauled. Major changes since Demo 2 Trentino, a media player, has been implemented by Eugene Zaikonnikov. Further improvements to conformance, stability and performance. The CLOS implementation follows the MOP much more closely. More traditional window management. Booting from CD/USB on real hardware is now possible. Driver support for Intel HDA audio devices. VirtualBox guest (mouse & display) integration. Major changes since Demo 1 Many improvements to conformance, stability and performance. The editor has been greatly improved, thanks to Burton Samograd. The system now functions correctly on computers with more than 1GB of RAM. The allocator and garbage collector now make much better use of available memory, with far fewer GC cycles occuring. (ROOM T) prints more detailed information about allocated objects. Transparency and premultiplied alpha support in the GUI. And more! Additional information "Hypothymis azurea - Kaeng Krachan" by JJ Harrison (jjharrison89@facebook.com) [CC BY-SA 3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons https://commons.wikimedia.org/wiki/File:Hypothymis_azurea_-_Kaeng_Krachan.jpg "Mandarin Pair" by © Francis C. Franklin / CC-BY-SA-3.0. Licensed under CC BY-SA 3.0 via Wikimedia Commons - http://commons.wikimedia.org/wiki/File:Mandarin_Pair.jpg "Handsome" by Andy Morffew - https://www.flickr.com/photos/andymorffew/19377769093/in/album-72157630893775092/ [CC BY 2.0 (http://creativecommons.org/licenses/by/2.0)] Includes Dejavu Fonts 2.37 (https://dejavu-fonts.github.io/) Some icons from Icojam (http://www.icojam.com)
Read the full README on GitHub

What Hacker News says

8 sources
> why not design a new Lisp? Hell no. Here is why: 1. The Common Lisp standard is brilliant. If your new Lisp is designed by anything less than a committee with people like Kent Pitman, Guy Steele, and Richard P. Gabriel, chances are that you will end up with something worse. 2. Common Lisp has one feature that people often forget about, but that is crucial for an operating system - you can rely on the fact that the semantics doesn't change. Lisp programs written in 1960 can usually be run on today's Common Lisp without modification, so there is hope that programs written today will still run properly even in centuries. 3. Common Lisp has the most powerful object system and the most powerful condition handling system. Both these features are invaluable for an operating system. This is actually my main motivation for contributing to t
Read the rest
his project. I want my programs to communicate via objects, and I want a system-wide mechanism for recovering from errors without crashing or unwinding the stack. 4. By relying on a very good existing language instead of reinventing this wheel, there is a chance that CLOSOS will actually get finished. > I'm sure with a little bit of effort SBCL could run as a unikernel and provide a good base for the system. Probably. But to make CLOSOS actually useful, we need an abstraction for having multiple first class global environments. And bolting that on top of SBCL without breaking existing things is about as painful as a full rewrite. The other big point is that SBCL values performance more than safety. But for CLOSOS, safety is crucial. > Movitz We intend to borrow some ideas from Movitz. But since we managed to bootstrap Common Lisp directly from Common Lisp, we hope that some things can be done more elegantly. The other project that should be mentioned here is Mezzano (https://github.com/froggey/Mezzano). We even borrow some code from Mezzano and are actively collaborating with its author.
In Closos: Specification of a Lisp operating system (2013) [pdf]
It's far from comprehensive, but here are a handful of operating system projects that have caught my eye: [1] MezzanoOS, an OS written in Common Lisp (https://github.com/froggey/Mezzano) [2] SerenityOS, a Unix-like OS (https://github.com/SerenityOS/serenity/). The primary author has a youtube channel (https://www.youtube.com/c/AndreasKling/) [3] RedoxOS, a microkernel OS written in Rust (https://www.redox-os.org/) [4] Nebulet, a microkernel based on webassembly (https://github.com/nebulet/nebulet) [5] It was never released by Microsoft, but Midori OS had some fascinating ideas like software isolated processes, asynchronous message passing and object capabilities. Nice write-up about the project by Joe Duffy here http://joeduffyblog.com/2015/11/03/blogging-about-midori/
In Learn to write a simple OS kernel with keyboard/screen support (2014)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.