A→Z
AtoZ WIKI
The Living Compendium
A-Z INDEX: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Compendium / Letter I / Inferno (operating system)
📅 Sep 2026 📖 Open Compendium
AtoZ Compendium #I CC BY-SA 4.0

Inferno (operating system)

Distributed operating system

Audio Narration Natural Voice
Press play to listen
⚡ Executive Synopsis TL;DR Overview

Inferno is a MIT Licensed distributed operating system started in 1995 at Bell Labs, which is now held by Vita Nuova Holdings and maintained by Terzarima Systems. 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.

Inferno (operating system)

Inferno
Inferno 4th Edition
Developer
Inferno
Bell Labs, Vita Nuova Holdings, Terzarima Systems
Inferno64: Caerwyn Jones
Written inC, Limbo
Working state
Inferno
Current; No paid support available
Inferno64: Current
Source modelOpen-source
Initial release
Inferno
Bell Labs Release 1996 (1996)
Inferno64: 2022 (2022)
Latest releaseInferno 4th Edition / inferno-os April 21, 2026 (2026-04-21)
Inferno64: July 8, 2026 (2026-07-08)
Repository
Inferno https://github.com/inferno-os/inferno-os
Inferno64 https://github.com/caerwynj/inferno64
Available inEnglish
Supported platformsInferno:
ARM, RISC-V, x86
Inferno64: AArch64, x86-64
Historic: AMD 29k, MIPS, PowerPC, SPARC, PA-RISC, SH-4
Kernel typeVirtual machine (Dis)
Influenced byResearch Unix, Plan 9
Default
user interface		 Tk based WM[1]
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 in 1995 at Bell Labs,[1] which is now held by Vita Nuova Holdings and maintained by Terzarima Systems.[2][11] 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.

Name

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.[12]

Design principles

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 Technologies, the successor to that arm of AT&T, closed the Bell Labs Computing Sciences Research Center in 2005.[13]

Inferno is a distributed operating system based on three principles:

  • Resources as files: all resources are represented as files within a hierarchical file system[14]
  • 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;[15] derived from Plan 9 namespaces[16]
  • Standard communication protocol: a standard protocol, called Styx, is used to access all resources, both local and remote[17]

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.[18] 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 has built-in modules that provide interfaces of the virtual operating system, such as system calls, graphics, security, and POSIX compliant math modules.[14][21]

Inferno Paper introducing the original Inferno release

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: Inferno currently runs on Intel, Sun SPARC, ARM, SGI MIPS, HP PA-RISC, IBM PowerPC, and AMD 29k 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.[22]

Features

Application development and APIs

To ensure memory safety, applications are written in the Limbo programming language, which provides static typing, garbage collection, and built-in concurrency features, this allows the operating system to safely run without a hardware MMU; only kernel modules and internal parts of the Dis virtual machine itself can be written in C with a key example being the system sys module which contains the majority of the system calls.[23] 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.[1][24] Low level operating system functions such as process creation and inter-process communication are implemented within the Dis virtual machine itself; This means applications cannot access memory outside their allocated range[25] and all resources such as file descriptors, network connections, and window manager objects are connected to the garbage collector;[24] the garbage collector uses the very concurrent garbage collection algorithm.[20] In hosted mode, kernel threads are handled by the host operating system.[26]

Resource management

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.[1][17] Hardware is also accessed through user mode file servers that present resources to the user-mode API from the native kernel. When Inferno is hosted, all of the hardware resources are managed by the host operating system and accessed through a namespace which binds to the specific exposed hardware interfaces of the host OS.[27] Inferno64 further manages resources through the Owen labor exchange which also allows for intelligent network discovery and resource sharing, first conceptualised in 2004 for Inferno 4th Edition.[28]

Security features

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.[29] Inferno64 continues this with support for the latest version of the SSH protocol and TLS 1.3.[30] The owner based security model ensures that each module has a namespace that can only be fully controlled by an administrator, the default user owner is known as Eve in both hosted and native mode.[31]

Filesystems

All provided filesystems are provided by file servers in a similar fashion to Plan 9 and file servers are written in Limbo.[32] The native provided filesystem is kfs as used in the first and second edition of Plan 9.[16] File servers can be implemented as a kernel module or as a user-mode application; files are manipulated using functions which translate to Styx messages.[33]

Integrated development environment

The Inferno operating system is compiled with a modified variant of the Plan 9 compiler suite including mk[34] that has been rewritten in ANSI C with POSIX extensions.[35] This modified suite has served as a basis for the modern Plan 9 compiler suite of the 2020s.[36]

Inferno provides a full development environment that includes a compiler, graphical debugger, scripting tools, and libraries for networking and user interfaces.[37] The majority of the development tools operating on Inferno are Plan 9 tools rewritten in Limbo.[35] It supports dynamic module loading and can operate with low resource requirements, such as systems with 1 MB of memory.[1]

Inferno64 includes built-in AI coding agents and provides 64-bit JIT compilers.[12]

Supported device platforms

Previous versions of Inferno could run either as a native operating system on historically supported architectures such as MIPS, PowerPC, SH-4, and SPARC[35] or as a hosted application on historic operating systems, including 2.x versions of Linux, Unixware 2.x, Windows 2000, Plan 9 3rd Edition, FreeBSD, Solaris 7, Mac OS X Tiger, and IRIX.[38]

The current development branch version of Inferno 4th Edition maintains support for AArch32 and IA-32 while the hosted ports are better suited for Linux and 9front.[3] Inferno64 which abandons previous 32-bit processing platforms, supports x86-64 and AArch64.[12]

History

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

Connection to Plan 9

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.[39]

Lucent origins

In the mid-1990s, Plan 9 development was set aside in favor of Inferno.[40] The new system's existence was leaked by Dennis Ritchie in early 1996, after less than a year of development, 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.[41] The Inferno business unit was founded by Lucent Technologies after the AT&T spin-off and staffed with a team of 20 personnel.[42]

In March–April 1997, IEEE Internet Computing included an advertisement[43] 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,[44] and the Lucent Pathstar phone switch.[45] They initially offered 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.[18] Lucent licensed Java from Sun, stating that all Inferno devices would be made to run Java. A Java byte code to Dis byte code translator was written to facilitate that.[46] However, Inferno still did not find customers; Lucent also held a Limbo programming contest in 1998 in an attempt to attract student developers.[47]

The Inferno business unit ceased operations in 2000 within three years of its founding, and Lucent sold Inferno to Vita Nuova Holdings based in York, England.[48]

Vita Nuova, renewed development

In 1996, Vita Nuova Limited was founded in York, England with the goal of commercializing both Plan 9 and Inferno. Lucent soon contracted Vita Nuova to produce a PowerPC port of Plan 9 for the BeBox.[49] In 1997, Lucent created a new ventures group to exploit the commercial possibilities of everything produced at Bell Labs.[50] It was through this ventures group that Vita Nuova became Vita Nuova Holdings and obtained the Inferno operating system.[51] Vita Nuova would also offer a boxed edition of Plan 9.[52]

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 became effectively defunct after 2022 but remains actively registered for historic copyright reasons.[49]

Inferno64

In 2022, Inferno was forked into the active Inferno64[53] project which added 64-bit capabilities, although this made applications written for the original 4th edition 32-bit Dis virtual machine incompatible with the newer 64-bit version of Dis. As of 2026, Inferno64 development remains active.[54] The previous official formal Dis Virtual Machine specification had been last published and revised in 2003.[55]

30 years of Inferno and planned future development

As of 2026, 32-bit Inferno 4th Edition is maintained with occasional developments added by Charles Forsyth of Terzarima Systems[11] and is held on the appropriate GitHub repository.[3] A port of 32-bit Inferno OS to RISC-V has been discussed by Forsyth alongside an updated formal specification of the Dis virtual machine.[56] A near complete RISC-V port had been previously developed at the Norwegian University of Science and Technology in 2021.[57] Preliminary planning of the future 5th Edition Inferno release has begun but the features are yet to be fully decided.[49]

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
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 Latest development branch of Inferno 4th Edition; maintained by Terzarima Systems; unused architectures dropped; Inferno 5th Edition to be planned

Ports

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 before XP, Linux, FreeBSD, Plan 9, Mac OS X, Solaris, IRIX, UnixWare.

Inferno could also be hosted by a plug-in to Internet Explorer.[58] Vita Nuova director Michael Jeffrey stated that a Netscape plug-in was planned for 2002 but it was never released.[51] The plug-in code was deleted from the current Inferno-OS branch in 2021.[59]

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

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

A timeline of various device ports

1990s: Acorn Archimedes,[60] BeBox,[49] IBM PC Series, JavaStation,[35] Lucent Appliances,[44] SA-1100 based VoIP phone[61]

2000s: Compaq IPAQ,[62] PowerQUICC II Series,[35] Nintendo DS,[63] NTT MAP-1000,[64] XScale based devices[35]

2010s: Android devices,[65][66] Openmoko,[67] SheevaPlug,[68] Sun SPOT,[69] Raspberry Pi[70]

2020s: Raspberry Pi Pico,[71] RISC-V System Emulator,[57] Sparkfun MicroMod[72]

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

Distribution

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.[73]

See also

Notes

  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"

References

  1. 1 2 3 4 5 6 Dorward, Sean M; Pike, Rob; Presotto, David Leo; Ritchie, Dennis M; Winterbottom, Philip (31 March 1997). "The Inferno Operating System". Bell Labs Technical Journal. 2 (1). Lucent Technologies: 5–18. doi:10.1002/bltj.2028.{{cite journal}}: CS1 maint: date and year (link)
  2. 1 2 3 4 "Inferno Licence Terms". Archived from the original on 27 April 2021. Retrieved 17 June 2021. The bulk of Inferno 4th Edition is provided under the `MIT' licence.
  3. 1 2 3 4 5 6 7 8 "GitHub – inferno-os/inferno-os". GitHub. Retrieved 5 October 2025.
  4. ↑ "Inferno Licence Terms". Archived from the original on 11 August 2005. The Free Software Scheme" and "Commercial Developer Licence
  5. ↑ "Vita Nuova Commercial Developer License – 9 November 2005". Archived from the original on 2 May 2006.
  6. 1 2 3 "Inferno Licence Terms". Archived from the original on 26 October 2003. 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 5 April 2005.
  8. ↑ "Vita Nuova Liberal Source License – 14 May 2003". Archived from the original on 23 February 2004.
  9. ↑ "Vita Nuova Commercial Developer License – 22 April 2003". Archived from the original on 25 June 2004.
  10. ↑ "Vita Nuova Inferno Subscription Licence". Archived from the original on 8 December 2000.
  11. 1 2 "Charles Forsyth (Terzarima Systems)". www.terzarima.net. Retrieved 7 August 2026.
  12. 1 2 3 4 "Inferno64 – Distributed Compute Grid". inferno64.org. Retrieved 7 August 2026.
  13. ↑ "Unix Review > Dept. 1127: going, Going, GONE!". www.unixreview.com. Archived from the original on 27 October 2005. Retrieved 9 August 2026.
  14. 1 2 Sharma, Ravi (1 June 1999). "Distributed application development with Inferno". Proceedings of the 36th annual ACM/IEEE Design Automation Conference. ACM. pp. 146–150. doi:10.1145/309847.309904. ISBN 978-1-58113-109-3.
  15. ↑ Breitstein, Steven R. (26 June 1999). "Inferno Namespaces". Inferno White Papers. Lucent Technologies. Archived from the original on 11 June 1998. Retrieved 10 August 2026.
  16. 1 2 Pike, Rob; Presotto, Dave; Thompson, Ken; Trickey, Howard; Winterbottom, Phil (1 April 1993). "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.
  17. 1 2 Pike, Rob; Ritchie, Dennis M. (30 June 1999). "The Styx® architecture for distributed systems". Bell Labs Technical Journal. 4 (2). Lucent Technologies: 146–152. Bibcode:1999BSTJ....4..146P. doi:10.1002/bltj.2169. ISSN 1538-7305.
  18. 1 2 "Lucent brews Inferno". InfoWorld. 1 October 1996. Retrieved 16 August 2026.
  19. ↑ Winterbottom, Phil; Pike, Rob (26 February 1997). "The design of the Inferno virtual machine". 9p.io. Proceedings, IEEE COMPCON 97 : San Jose, California, 23–26 February 1997. ISBN 978-0818678042. Retrieved 10 August 2026.{{cite web}}: CS1 maint: periodical has ISBN (link)
  20. 1 2 Huelsbergen, Lorenz; Winterbottom, Phil (1998). Very Concurrent Mark and Sweep Garbage Collection without Fine-Grain Synchronization (PDF). 1998 International Symposium on Memory Management.
  21. ↑ Stuart, Brian L (2008). Principles of Operating Systems Design & Applications (1st ed.). Course Technology. p. 40. ISBN 9781418837693.
  22. ↑ "Linux Usage In IoT Devices By Category Statistics 2026". 8 April 2026. Retrieved 8 August 2026.
  23. ↑ Stuart, Brian L. (2008). Principles of Operating Systems: Design & Applications (1st ed.). Course Technology. pp. 52–53, 148. ISBN 9781418837693.
  24. 1 2 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.
  25. ↑ Stuart, Brian L (2008). Principles of Operating Systems: Design & Applications (1st ed.). Course Technology. pp. 253–256. ISBN 9781418837693.
  26. ↑ Stuart, Brian L (2008). Principles of Operating Systems Design & Applications (1st ed.). Course Technology. p. 157. ISBN 9781418837693.
  27. ↑ Stuart, Brian L (2008). Principles of Operating Systems Design & Applications (1st ed.). Course Technology. pp. 345–346.
  28. ↑ Peppé, Roger. "Owen: A Labour Exchange for Computational Grids" (PDF). bitbucket. Vita Nuova. Retrieved 7 August 2026.
  29. ↑ Presotto, David Leo (23 February 1997). "Inferno security". Proceedings IEEE COMPCON 97. Digest of Papers. IEEE Comput. Soc. Press. pp. 251–253. Bibcode:1997cmpc.conf...43P. doi:10.1109/CMPCON.1997.584721. ISBN 978-0-8186-7804-2.
  30. ↑ "caerwy (@caerwy) on X". X (formerly Twitter). 7 April 2026. Retrieved 7 August 2026.
  31. ↑ Stuart, Brian L (2008). Principles of Operating Systems: Design & Applications (1st ed.). Course Technology. p. 44. ISBN 9781418837693.
  32. ↑ Stuart, Brian L (2008). Principles of Operating Systems Design & Applications (1st ed.). Course Technology. pp. 38, 437. ISBN 9781418837693.
  33. ↑ Stuart, Brian L (2008). Principles of Operating Systems Design & Applications (1st ed.). Course Technology. pp. 437–38, 450–51.
  34. ↑ Hume, Andrew G; Flandrena, Bob (2000). "Maintaining Files on Plan 9 with Mk" (PDF). 9p.io. Lucent Technologies, AT&T Labs. Retrieved 23 August 2026.
  35. 1 2 3 4 5 6 "Inferno Ports: Hosted and Native". doc.cat-v.org. Vita Nuova. Retrieved 9 August 2026.
  36. ↑ Padioleau, Yoann (7 May 2026). "Goken: The Plan 9 Toolchain Reborn" (PDF). 12th International Workshop on Plan 9, Works in Progress.
  37. ↑ Deshmukh, Shubhangi; Shete, V. V. (1 March 2012). "Developing ARM based PDA using Inferno OS". 2012 International Conference on Computer Communication and Informatics. Coimbatore, India. pp. 1–4. Bibcode:2012cinf.conf..147D. doi:10.1109/ICCCI.2012.6158886. ISBN 978-1-4577-1583-9.{{cite book}}: CS1 maint: location missing publisher (link)
  38. ↑ Dorward, Sean; Pike, Rob; Presotto, David Leo; Ritchie, Dennis M.; Trickey, Howard; Winterbottom, Phil (2000). "Vita Nuova: The Inferno Operating System" (PDF). inferno-os. Vita Nuova. Retrieved 21 August 2026.
  39. ↑ Peppé, Roger (2006). "Program Development under Inferno" (PDF). Vita Nuova. Retrieved 2 September 2026.
  40. ↑ Pontin, Jason (19 February 1996). "AT&T reveals plans for Java competitor". InfoWorld. p. 3.
  41. ↑ Hayes, Frank (19 February 1996). "Bell Lab's Inferno aims to rival Java". Computerworld. p. 6.
  42. ↑ "Lucent wants to burn Java with Inferno – CNET". CNET News Staff. 6 May 1996. Retrieved 9 August 2026.
  43. ↑ "IEEE Internet Computing". IEEE Internet Computing. 1 (2). 30 April 1997. ISSN 1089-7801.
  44. 1 2 Coles, Delitha Morrow; Cunningham, Donna (9 December 1997). "Lucent Technologies Announces the Next Generation in Internet Security | Newswise". www.newswise.com. Retrieved 11 August 2026.
  45. ↑ Fossaceca, John M.; Sandoz, James D.; Winterbottom, Philip (31 December 1998). "The PathStar access server: Facilitating carrier-scale packet telephony". Bell Labs Technical Journal. 3 (4). Lucent Technologies: 86–102. Bibcode:1998BSTJ....3...86F. doi:10.1002/bltj.2130. ISSN 1538-7305.
  46. ↑ Yurkoski, C. F.; Rau, L. R.; Ellis, B. K. (1998). "Using Inferno™ to execute Java™ on small devices". In Mueller, Frank; Bestavros, Azer (eds.). Languages, Compilers, and Tools for Embedded Systems. Lecture Notes in Computer Science. Vol. 1474. Berlin, Heidelberg: Springer. pp. 108–118. doi:10.1007/BFb0057784. ISBN 978-3-540-49673-1.
  47. ↑ "Inferno Limbo Championship". www.lucent-inferno.com. Archived from the original on 24 April 1999. Retrieved 9 August 2026.
  48. ↑ "York firm hits Internet gold". York Press. 28 June 2000. Retrieved 9 August 2026.
  49. 1 2 3 4 Development, PodBean. "Episode 17 – Plan 9 and Inferno OS | The Living in the Future Podcast". www.livinginthefuture.rocks. Retrieved 10 August 2026.
  50. ↑ Banyi, Monica; Caplan, Dennis; Graham, Roger (4 April 2011). "The short happy life of Celiant Corporation: Did managerialism at Lucent Technologies divert shareholder wealth to private equity investors?". Critical Perspectives on Accounting. 22 (4): 337–350. doi:10.1016/j.cpa.2011.02.003.
  51. 1 2 "Interview with Vita Nuova CEO Michael Jeffrey – OSnews". www.osnews.com. 5 March 2002. Retrieved 15 August 2026.
  52. ↑ "Inferno and Plan 9 Newsletter May 2002". Archived from the original on 9 August 2002.
  53. ↑ "History". www.caerwyn.com. Retrieved 7 August 2026.
  54. ↑ "State of inferno64". groups.google.com. Retrieved 8 August 2026.
  55. ↑ "Dis Virtual Machine Specification" (PDF). Vita Nuova. 2003. Retrieved 26 August 2026.
  56. ↑ "Formal Specification for Dis VM?". groups.google.com. Retrieved 8 August 2026.
  57. 1 2 Stephansen, Sindre Amdal (8 September 2021). The Challenges of porting Inferno to RISC-V. Norwegian University of Science and Technology. hdl:11250/3025707.
  58. ↑ "Supporting code to allow Inferno to act as a plugin in various browsers".
  59. ↑ inferno-os. "remove mention of long obsolete IE plugin · inferno-os/inferno-os@e99c80a". GitHub. Retrieved 11 August 2026.
  60. ↑ "Acorn A7000+ · Wiki · David Boddie / inferno-os · GitLab". GitLab. Retrieved 15 August 2026.
  61. ↑ Intel® StrongARM® SA-1100 WebPhone Reference Design: User's Guide (PDF). Intel Corporation. 8 September 1998.
  62. ↑ "Compaq iPaq plunges into Inferno". ZDNET. 28 June 2001. Retrieved 15 August 2026.
  63. ↑ Lukkien, Mechiel (22 January 2024), mjl-/inferno-ds, retrieved 25 January 2024
  64. ↑ "Development record". Nippon Techno Lab (in Japanese). Retrieved 15 August 2026.
  65. ↑ "Inferno OS Running On Android Phones". Slashdot. 17 September 2011. Retrieved 5 October 2025.
  66. ↑ John Floren (16 September 2011). "Announcing Inferno for Android phones". Retrieved 5 October 2025.
  67. ↑ "inferno-openmoko – inferno for openmoko neo freerunner – Google Project Hosting". Retrieved 4 June 2012.
  68. ↑ Lukkien, Mechiel (3 January 2023), mjl-/inferno-kirkwood, retrieved 15 August 2026
  69. ↑ Stuart, Brian L (14 September 2013). "Inferno in Embedded Space: Porting to the Sun SPOT" (PDF). 8th International Workshop on Plan 9.
  70. ↑ Horne, Michael (24 November 2015). "Porting Inferno OS to the Raspberry Pi". Raspberry Pi Pod. Retrieved 15 August 2026.
  71. ↑ J, Caerwyn (30 March 2026), caerwynj/inferno-pico, retrieved 9 August 2026
  72. ↑ Plan 9 Foundation (16 April 2024). David Boddie - Three More Cortex-M Inferno Ports. Retrieved 3 September 2026 – via YouTube.{{cite AV media}}: CS1 maint: numeric names: authors list (link)
  73. ↑ caerwynj. "inferno64/NOTICE at main · caerwynj/inferno64". GitHub. Retrieved 7 August 2026.


Further reading

  • 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.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Inferno_(operating_system)&oldid=1375569439"
⚖️ Report / DMCA