Inferno (operating system)

Contributors to Wikimedia projects · Wikimedia Foundation, Inc. ·

17 min read Original article ↗

Distributed operating system

Operating system

Inferno

Inferno 4th Edition

Developer
Inferno
Bell Labs, Vita Nuova Holdings, Terzarima Systems Inferno64: Caerwyn Jones
Written inC,[1] Limbo
Working state
Inferno
Current; No paid support avaliable
Inferno64: Current
Source modelOpen-source
Initial release
Inferno
Bell Labs Release 1996; 30 years ago (1996)
Inferno64: 2022; 4 years ago (2022)
Latest releaseInferno 4th Edition / inferno-os April 21, 2026; 3 months ago (2026-04-21)
Inferno64: July 8, 2026; 34 days ago (2026-07-08)
Repository
Inferno https://github.com/inferno-os/inferno-os
Inferno 64 https://github.com/caerwynj/inferno64
Available inEnglish
Supported platformsInferno:
ARM, x86
Inferno64: AArch64, x86-64
Historic: MIPS, PowerPC, SPARC, PA-RISC
Kernel typeVirtual machine (Dis)
Influenced byResearch Unix, Plan 9
License2021: MIT[2][3]
2005: Dual[a][4][5]
2003: Dual[b][6][7][8][9]
2000: Inferno[c][10]
Original: Proprietary
Official website
Inferno
github.com/inferno-os/inferno-os
Inferno64 inferno64.org

Inferno is a MIT licensed[3] distributed operating system started at Bell Labs[11], is now held by Vita Nuova Holdings and maintained by Terzarima Systems.[2][12] Inferno was based on the experience gained with Plan 9 from Bell Labs, and the further research of Bell Labs into operating systems, languages, on-the-fly compilers, graphics, security, networking and portability. The name of the operating system, many of its associated programs, and that of Vita Nuova were inspired by Dante Alighieri's Divine Comedy. In Italian, Inferno means "hell", of which there are nine circles in Dante's Divine Comedy. Inferno64 is a continuation of Inferno for 64-bit Edge Computing platforms.[13]

Inferno was created in 1995 by members of the AT&T Bell Labs Computing Sciences Research Center to bring ideas derived from their previous operating system, Plan 9 from Bell Labs, to a wider range of devices and networks. Lucent would later shutdown the Bell Labs Computing Sciences Research Center in 2005. [14]

Inferno is a distributed operating system based on three basic principles:

  • Resources as files: all resources are represented as files within a hierarchical file system[15]
  • Namespaces: a program's view of the network is a single, coherent namespace that appears as a hierarchical file system but may represent physically separated (locally or remotely) resources;[16] Derived from Plan 9 namespaces[17]
  • Standard communication protocol: a standard protocol, called Styx, is used to access all resources, both local and remote[18]

To handle the diversity of network environments it was intended to be used in, the designers decided a virtual machine (VM) was a necessary component of the system. This is the same conclusion of the Sun Microsystems Oak project that became Java, but arrived at independently.

The Dis virtual machine is a register machine intended to closely match the architecture it runs on, in contrast to the stack machine of the Java virtual machine. An advantage of this approach is the relative simplicity of creating a just-in-time compiler for new architectures. This was inspired by AT&T's work on the CRISP processor. [19]

The virtual machine provides memory management designed to be efficient on devices with as little as 1 MiB of memory and without memory-mapping hardware. Its garbage collector is a hybrid of reference counting and a real-time coloring collector that gathers cyclic data.[20]

The Inferno kernel contains the virtual machine, on-the-fly compiler, scheduler, devices, protocol stacks, the name space evaluator for the file name space of each process, and the root of the file system hierarchy. The kernel also includes some built-in modules that provide interfaces of the virtual operating system, such as system calls, graphics, security, and math modules.[15]

The Bell Labs Technical Journal paper introducing Inferno listed several dimensions of portability and versatility provided by the OS as of first public release in 1997:[1]

  • Portability across processors: it currently runs on ARM, SGI MIPS, HP PA-RISC, IBM PowerPC, Sun SPARC, and Intel x86 architectures and is readily portable to others.
  • Portability across environments: it runs as a stand-alone operating system on small terminals, and also as a user application under Bell Labs Plan 9, Windows NT, Windows 95, and Unix. In all of these environments, Inferno programs see an identical interface.
  • Distributed design: the identical environment is established at the user's terminal and at the server, and each may import the resources (for example, the attached I/O devices or networks) of the other. Aided by the communications facilities of the run-time system, programs may be split easily (and even dynamically) between client and server.
  • Minimal hardware requirements: it runs useful applications stand-alone on machines with as little as 1 MiB of memory, and does not require memory-mapping hardware.
  • Portable programs: Inferno programs are written in the type-safe language Limbo and compiled to Dis bytecode, which can be run without modifications on all Inferno platforms.
  • Dynamic adaptability: programs may, depending on the hardware or other resources available, load different program modules to perform a specific function. For example, a video player might use any of several different decoder modules.

These design choices were directed to provide standard interfaces that freed content and service providers from concern of the details of diverse hardware, software, and networks of the 1990s over which their content was delivered. The majority of IoT Hardware operating in 2024 used Linux in comparison to the hardware challenges that the Inferno designers faced.[21]

Inferno runs either as a native operating system or as a hosted application on several existing operating systems, including Linux, Windows, Plan 9, FreeBSD, Solaris, Mac OS X, and IRIX. Supported processor architectures include Intel x86, ARM, PowerPC, and SPARC.[11][22] Inferno64 which abandons previous 32-bit processing platforms, supports x86-64 and Aarch64.[13]

Applications are written in the Limbo programming language, which provides static typing, garbage collection, and built-in concurrency features. Limbo code is compiled into architecture-independent bytecode executed by the Dis virtual machine. The Dis VM can interpret the bytecode or compile it just-in-time into native instructions, allowing applications to run consistently across different platforms.[11][23]

All resources in Inferno, such as devices, services, and network connections, are represented as files in a hierarchical namespace and accessed using standard file operations like open, read, write, and close. Inferno uses the Styx protocol, equivalent to Plan 9's 9P2000, to interact with both local and remote resources in a uniform manner.[11][18] Inferno64 further manages resources through the Owen labor exchange which also allows for intelligent network discovery, first conceptualised in 2004 for Inferno 4th Edition. [13][24]

Security features include per-process namespaces, authentication, and encryption. Applications operate within restricted namespaces, limiting their access to only authorized resources. The system supports a range of cryptographic protocols, including RSA, Diffie–Hellman, and symmetric encryption methods such as RC4 and DES.[25] Inferno64 continues this with support for the latest versions of SSH and TLS 1.3. [26]

Inferno provides a full development environment that includes a compiler, graphical debugger, scripting tools, and libraries for networking and user interfaces. It supports dynamic module loading and can operate with low resource requirements, such as systems with 1 MB of memory.[11][27] Inferno64 includes built-in AI coding agents.[13]

Lucent advertisement for Inferno in IEEE Internet Computing, Volume 1, Number 2, March–April 1997

Inferno is a descendant of Plan 9 from Bell Labs, and shares many design concepts and even source code in the kernel, particularly around devices and the Styx/9P2000 protocol. Inferno shares with Plan 9 the Unix heritage from Bell Labs and the Unix philosophy. Many of the command line tools in Inferno were Plan 9 tools that were translated to Limbo.[28]

In the mid-1990s, Plan 9 development was set aside in favor of Inferno.[29] The new system's existence was leaked by Dennis Ritchie in early 1996, after less than a year of development on the system, and publicly presented later that year as a competitor to Java. At the same time, Bell Labs' parent company AT&T licensed Java technology from Sun Microsystems.[30] The Inferno business unit was founded by Lucent after the AT&T spin-off and staffed with a team of 20 personnel. [31]

In March–April 1997 IEEE Internet Computing included an advertisement[32] for Inferno networking software. It claimed that various devices could communicate over "any network" including the Internet, telecommunications and LANs. The advertisement stated that video games could talk to computers,–a PlayStation was pictured–cell phones could access email and voice mail was available via TV.

Lucent used Inferno in at least two internal products: the Lucent VPN Firewall Brick[33],and the Lucent Pathstar phone switch.[34] They initially tried to sell source code licenses of Inferno but found few buyers. Lucent did little marketing and missed the importance of the Internet and Inferno's relation to it. During the same time Sun Microsystems was heavily marketing its own Java programming language, which was targeting a similar market, with analogous technology, that worked in web browsers and also filled the demand for object-oriented languages popular at that time. Lucent licensed Java from Sun, claiming that all Inferno devices would be made to run Java. A Java byte code to Dis byte code translator was written to facilitate that.[35] However, Inferno still did not find customers; Lucent also held a Limbo programming contest in 1998 in an attempt to attract student developers.[36]

The Inferno business unit ceased operations in 2000 after 3 years of its founding, and Lucent sold Inferno to Vita Nuova Holdings based in York.[37] The historic working papers of the former Lucent/Bell Labs Inferno business unit prior to 2000 can be found archived here.

Vita Nuova continued development and offered commercial licenses to the complete system, and free downloads under non-GPL compatible licenses for all of the system except the kernel and VM. They ported the software to new hardware and focused on distributed applications. In 2004, Vita Nuova released the 4th edition under more common free software licenses, and in 2021 they relicensed all editions mainly under the MIT License.[6][2][3] In 2026, It was explained by former Vita Nuova architect Charles Forsyth that Vita Nuova is now effectively defunct but remains actively registered for historic copyright reasons.[38]

In 2022, Inferno was forked into the active Inferno64[39] project which added 64-bit capabilities, however this made all applications written for the original 4th edition 32-bit Dis Virtual Machine incompatible with the newer 64-bit version of Dis. Inferno64 development remains active.[40] The previous official formal Dis Virtual Machine specification had been last published in 2000[41] with additional changes made in 2003.[42]

As of 2026, 32-bit Inferno 4th Edition is maintained with occasional developments added by Charles Forsyth of Terzarima Systems[12] and is held on the appropriate GitHub repository.[43] A port of 32-bit Inferno OS to RISC-V has been discussed by Charles Forsyth alongside an updated formal specification of the Dis Virtual Machine. [44]

Release timeline
Date Release Comment
1996 Inferno Beta Released by Bell Labs
May 1997 Inferno Release 1.0 Winter 1997 Bell Labs Technical Journal Article
July 1999 Inferno 2nd Edition Released by Lucent's Inferno Business Unit. Bell Labs CSRC closed in 2005.
June 2001 Inferno 3rd Edition Released by Vita Nuova
2004 Inferno 4th Edition Open Source release; changes to many interfaces (incompatible with earlier editions); includes support for 9P2000; re-released under MIT License in 2021.
2022 Inferno64 Forked release with MIT licensed source; extends Dis VM to 64 bits and uses built-in SQLite; latest revisions include the LLM Fileserver for manipulating LLMs.
April 2026 Inferno-OS Currently maintained development branch of Inferno 4th Edition; maintained by Charles Forsyth of Terzarima Systems. Inferno 5th Edition to be planned.

Inferno runs on native hardware directly and also as an application providing a virtual operating system which runs on other platforms. Programs can be developed and run on all Inferno platforms without modifying or recompiling.

Native ports historically included these architectures: x86, MIPS, ARM, PowerPC, SPARC.

Historic hosted or virtual OS ports included: Microsoft Windows, Linux, FreeBSD, Plan 9, Mac OS X, Solaris, IRIX, UnixWare.

The updated April 2026 Inferno 4th edition Inferno-OS development branch only has only has current ports for x86 and ARM.[43]

Hosted ports supported by the April 2026 Inferno 4th edition Inferno-OS development branch are: Linux, macOS, NetBSD, Windows 11, and Plan 9. [43]

Inferno could also be hosted by a plug-in to Internet Explorer.[45] Vita Nuova said that plug-ins for other browsers were under development, but they were never released.[46] The plug-in code was deleted from the current Inferno-OS branch in 2021.[47]

Inferno has also been ported to Openmoko,[48] Nintendo DS,[49] SheevaPlug,[50] Raspberry Pi Pico,[51] and Android.[52][53]

Hosted Inferno64 is limited to modern 64-bit platforms such as macOS 12, Windows 11, 9front, and Android 10 or later. [54]

Inferno 4th edition was released in early 2005 as free software. Specifically, it was dual-licensed under two structures.[6] Users could either obtain it under a set of free software licenses, or they could obtain it under a proprietary license. In the case of the free software license scheme, different parts of the system were covered by different licenses, including the GNU General Public License, the GNU Lesser General Public License, the Lucent Public License, and the MIT License, excluding the fonts, which are sub-licensed from Bigelow and Holmes.

In March 2021, all editions were relicensed under mainly the MIT License.[2][3] Inferno64 continues under the same MIT License. [55]

  1. ↑ "The Free Software Scheme" and "Commercial Developer Licence"
  2. ↑ "Vita Nuova Liberal Source Licence" and "Vita Nuova Commercial Developer Licence"
  3. ↑ "Vita Nuova Inferno Subscription License"
  1. 1 2 Dorward, Sean; Pike, Rob; Presotto, David Leo; Ritchie, Dennis M.; Trickey, Howard; Winterbottom, Phil (1997). "The Inferno Operating System". Inferno Documentation. Vita Nuova. Retrieved 2014-05-02.{{cite web}}: CS1 maint: url-status (link)
  2. 1 2 3 4 "Inferno Licence Terms". Archived from the original on 2021-04-27. Retrieved 2021-06-17. The bulk of Inferno 4th Edition is provided under the `MIT' licence.
  3. 1 2 3 4 "GitHub - inferno-os/inferno-os". Retrieved 2025-10-05.
  4. ↑ "Inferno Licence Terms". Archived from the original on 2005-08-11. The Free Software Scheme" and "Commercial Developer Licence
  5. ↑ "Vita Nuova Commercial Developer License - 9 November 2005". Archived from the original on 2006-05-02.
  6. 1 2 3 "Inferno Licence Terms". Archived from the original on 2003-10-26. Vita Nuova Liberal Source Licence" and "Vita Nuova Commercial Developer Licence
  7. ↑ "Vita Nuova Liberal Source License - 29 May 2003". Archived from the original on 2005-04-05.
  8. ↑ "Vita Nuova Liberal Source License - 14 May 2003". Archived from the original on 2004-02-23.
  9. ↑ "Vita Nuova Commercial Developer License - 22 April 2003". Archived from the original on 2004-06-25.
  10. ↑ "Vita Nuova Inferno Subscription Licence". Archived from the original on 2000-12-08.
  11. 1 2 3 4 5 Dorward, Steven; Fioravanti, Alan; Nehab, Marcelo; Pike, Rob; Trickey, Howard; Winterbottom, Phil (1997). "The Inferno Operating System". Bell Labs Technical Journal. 2 (1): 5–18.
  12. 1 2 "Charles Forsyth (Terzarima Systems)". www.terzarima.net. Archived from the original on 2026-05-20. Retrieved 2026-08-07.
  13. 1 2 3 4 "Inferno64 - Distributed Compute Grid". inferno64.org. Retrieved 2026-08-07.
  14. ↑ "Unix Review > Dept. 1127: going, Going, GONE!". www.unixreview.com. Archived from the original on 2005-10-27. Retrieved 2026-08-09.
  15. 1 2 Sharma, Ravi (1999-06-01). "Distributed application development with Inferno". DAC '99: Proceedings of the 36th annual ACM/IEEE Design Automation Conference. ACM: 146–150. doi:10.1145/309847.309904. ISBN 978-1-58113-109-3.{{cite journal}}: CS1 maint: periodical has ISBN (link)
  16. ↑ Breitstein, Steven R. (1999-06-26). "Inferno Namespaces". Inferno White Papers. Lucent Technologies. Archived from the original on 1998-06-11. Retrieved 2026-08-10.
  17. ↑ Pike, Rob; Presotto, Dave; Thompson, Ken; Trickey, Howard; Winterbottom, Phil (1993-04-01). "The use of name spaces in Plan 9". ACM SIGOPS Operating Systems Review. 27 (2): 72–76. doi:10.1145/155848.155861. ISSN 0163-5980. Archived from the original on 2025-06-28.
  18. 1 2 Pike, Rob; Ritchie, Dennis M. (1999-06-30). "The Styx® architecture for distributed systems". Bell Labs Technical Journal. 4 (2): 146–152. doi:10.1002/bltj.2169. ISSN 1538-7305.
  19. ↑ Winterbottom, Phil; Pike, Rob (1997-02-26). "The design of the Inferno virtual machine". 9p.io. Proceedings, IEEE COMPCON 97 : San Jose, California, February 23-26, 1997. ISBN 978-0818678042. Retrieved 2026-08-10.{{cite web}}: CS1 maint: periodical has ISBN (link)
  20. ↑ Huelsbergen, Lorenz; Winterbottom, Phil (1998). Very Concurrent Mark and Sweep Garbage Collection without Fine-Grain Synchronization (PDF). 1998 International Symposium on Memory Management.
  21. ↑ "Linux Usage In IoT Devices By Category Statistics 2026". 2026-04-08. Retrieved 2026-08-08.
  22. ↑ "Inferno Ports: Hosted and Native". doc.cat-v.org. Vita Nuova. Retrieved 2026-08-09.
  23. ↑ Dorward, Sean; Pike, Rob; Presotto, Dave; Trickey, Howard; Winterbottom, Phil (1996). "Inferno: la Commedia Interattiva". USENIX 2nd Symposium on OS Design and Implementation (OSDI '96) Works In Progress Reports - Session Program.
  24. ↑ "Owen - Bitbucket". bitbucket.org. Retrieved 2026-08-07.
  25. ↑ Presotto, David Leo (1997-02-23). "Inferno security". Proceedings IEEE COMPCON 97. Digest of Papers. IEEE Comput. Soc. Press: 251–253. doi:10.1109/CMPCON.1997.584721. ISBN 978-0-8186-7804-2.{{cite journal}}: CS1 maint: periodical has ISBN (link)
  26. ↑ "caerwy (@caerwy) on X". X (formerly Twitter). 2026-04-07. Retrieved 2026-08-07.
  27. ↑ "Inferno". Archived from the original on 2026-01-04. Retrieved 2025-08-03.
  28. ↑ Peppé, Roger. "Program Development under Inferno". inferno-os.org. Vita Nuova Holdings. Archived from the original on 2022-06-27. Retrieved 2026-08-11.
  29. ↑ Pontin, Jason (19 February 1996). "AT&T reveals plans for Java competitor". InfoWorld. p. 3.
  30. ↑ Hayes, Frank (19 February 1996). "Bell Lab's Inferno aims to rival Java". Computerworld. p. 6.
  31. ↑ "Lucent wants to burn Java with Inferno - CNET". CNET News Staff. 1996-05-06. Retrieved 2026-08-09.
  32. ↑ "IEEE Internet Computing". IEEE Internet Computing. 1 (2). 1997-04-30. ISSN 1089-7801.
  33. ↑ Coles, Delitha Morrow; Cunningham, Donna (1997-12-09). "Lucent Technologies Announces the Next Generation in Internet Security | Newswise". www.newswise.com. Retrieved 2026-08-11.
  34. ↑ Fossaceca, John M.; Sandoz, James D.; Winterbottom, Philip (1998-12-31). "The PathStar access server: Facilitating carrier-scale packet telephony". Bell Labs Technical Journal. 3 (4): 86–102. doi:10.1002/bltj.2130. ISSN 1538-7305.
  35. ↑ Yurkoski, C. F.; Rau, L. R.; Ellis, B. K. (1998). Mueller, Frank; Bestavros, Azer (eds.). "Using Inferno™ to execute Java™ on small devices". Languages, Compilers, and Tools for Embedded Systems. Berlin, Heidelberg: Springer: 108–118. doi:10.1007/BFb0057784. ISBN 978-3-540-49673-1.{{cite journal}}: CS1 maint: periodical has ISBN (link)
  36. ↑ "Inferno Limbo Championship". www.lucent-inferno.com. Archived from the original on 1999-04-24. Retrieved 2026-08-09.
  37. ↑ "York firm hits Internet gold". York Press. 2000-06-28. Retrieved 2026-08-09.
  38. ↑ Development, PodBean. "Episode 17 - Plan 9 and Inferno OS | The Living in the Future Podcast". www.livinginthefuture.rocks. Retrieved 2026-08-10.
  39. ↑ "History". www.caerwyn.com. Retrieved 2026-08-07.
  40. ↑ "State of inferno64". groups.google.com. Retrieved 2026-08-08.
  41. ↑ "Dis Virtual Machine Specification". www.inferno-os.org. Vita Nuova. Archived from the original on 2026-02-12. Retrieved 2026-08-08.
  42. ↑ "Dis Virtual Machine Specification". doc.cat-v.org. Vita Nuova. Retrieved 2026-08-08.
  43. 1 2 3 inferno-os/inferno-os, Inferno Operating System, 2026-08-07, retrieved 2026-08-07
  44. ↑ "Formal Specification for Dis VM?". groups.google.com. Retrieved 2026-08-08.
  45. ↑ "Supporting code to allow Inferno to act as a plugin in various browsers".
  46. ↑ "Inferno - Plug-in". Vita Nuova. Archived from the original on 2021-05-08.
  47. ↑ inferno-os. "remove mention of long obsolete IE plugin · inferno-os/inferno-os@e99c80a". GitHub. Retrieved 2026-08-11.
  48. ↑ "inferno-openmoko - inferno for openmoko neo freerunner - Google Project Hosting". Retrieved 2012-06-04.
  49. ↑ Lukkien, Mechiel (2024-01-22), mjl-/inferno-ds, retrieved 2024-01-25
  50. ↑ "inferno-kirkwood - Inferno for the Marvell Kirkwood/Sheevaplug - Google Project Hosting". Retrieved 2012-06-04.
  51. ↑ J, Caerwyn (2026-03-30), caerwynj/inferno-pico, retrieved 2026-08-09
  52. ↑ "Inferno OS Running On Android Phones". Slashdot. 2011-09-17. Retrieved 2025-10-05.
  53. ↑ John Floren (2011-09-16). "Announcing Inferno for Android phones". Retrieved 2025-10-05.
  54. ↑ J, Caerwyn (2026-07-20), caerwynj/inferno64, retrieved 2026-08-07
  55. ↑ caerwynj. "inferno64/NOTICE at main · caerwynj/inferno64". GitHub. Retrieved 2026-08-07.
  • Stanley-Marbell, Phillip (2003). Inferno Programming with Limbo. Chichester: John Wiley & Sons. ISBN 0-470-84352-7. describes the 3rd edition of the Inferno operating system, though it focuses more on the Limbo language and its interfaces to the Inferno system, than on the Inferno system itself. For example, it provides little information on Inferno's versatile command shell, which is understandable since it is a programming language textbook.
  • Stuart, Brian (2008). Principles of Operating Systems: Design and Applications. Course Technology. ISBN 978-1-4188-3769-3., uses Inferno for examples of operating system design.
  • Atkins, Martin; Forsyth, Charles; Pike, Rob; Trickey, Howard. The Inferno Programming Book: An Introduction to Programming for the Inferno Distributed System. was intended to provide an operating-system-centric point of view, but was never completed.