Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Inferno (operating system)

From Wikipedia, the free encyclopedia
Distributed operating system
icon
This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Inferno" operating system – news ·newspapers ·books ·scholar ·JSTOR
(April 2010) (Learn how and when to remove this message)
Operating system
Inferno
Inferno 4th Edition
DeveloperBell Labs, Vita Nuova Holdings
Written inC,[1]Limbo
Working stateDiscontinued
Source modelOpen-source
Initial release1996; 30 years ago (1996)
Latest release4th Edition / March 28, 2015; 10 years ago (2015-03-28)
Repository
Available inEnglish
Supported platformsARM,PA-RISC,MIPS,PowerPC,SPARC,x86
Kernel typeVirtual machine (Dis)
License2021:MIT[2][3]
2005: Dual[a][4][5]
2003: Dual[b][6][7][8][9]
2000: Inferno[c][10]
Original:Proprietary
Preceded byPlan 9
Official websitewww.inferno-os.org

Inferno is adistributed operating system started atBell Labs and now developed and maintained byVita Nuova Holdings asfree software under theMIT License.[2][3] Inferno was based on the experience gained withPlan 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 the current company, were inspired byDante Alighieri'sDivine Comedy. In Italian,Inferno means "hell", of which there are nine circles in Dante'sDivine Comedy.

Design principles

[edit]

Inferno was created in 1995 by members ofBell Labs' Computer Science Research division to bring ideas derived from their previous operating system,Plan 9 from Bell Labs, to a wider range of devices and networks. Inferno is adistributed operating system based on three basic principles:

  • Resources as files: allresources are represented as files within ahierarchical file system
  • Namespaces: a program's view of the network is a single, coherentnamespace that appears as a hierarchical file system but may represent physically separated (locally or remotely) resources
  • Standard communication protocol: a standard protocol, calledStyx, is used to access all resources, both local and remote

To handle the diversity of network environments it was intended to be used in, the designers decided avirtual machine (VM) was a necessary component of the system. This is the same conclusion of the Oak project that becameJava, but arrived at independently. TheDis virtual machine is aregister machine intended to closely match the architecture it runs on, in contrast to thestack machine of theJava virtual machine. An advantage of this approach is the relative simplicity of creating ajust-in-time compiler for new architectures.

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. Itsgarbage collector is a hybrid of reference counting and a real-time coloring collector that gathers cyclic data.[11]

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.

The Bell Labs Technical Journal paper introducing Inferno listed several dimensions of portability and versatility provided by the OS:[1]

  • Portability across processors: it currently runs onARM, SGIMIPS,HPPA-RISC, IBMPowerPC, SunSPARC, and Intelx86 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 BellPlan 9, MSWindows NT,Windows 95, andUnix (SGIIrix,SunSolaris,FreeBSD,AppleMac OS X,Linux,IBMAIX,HP-UX, DigitalTru64). 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 requirememory-mapping hardware.
  • Portable programs: Inferno programs are written in thetype-safe languageLimbo and compiled toDis 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 free content and service providers from concern of the details of diverse hardware, software, and networks over which their content is delivered.

Features

[edit]
[icon]
This sectionneeds expansion. You can help byadding missing information.(April 2019)

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

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 likeopen,read,write, andclose. Inferno uses the Styx protocol, equivalent to Plan 9's 9P2000, to interact with both local and remote resources in a uniform manner.[12][13]

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

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

See also:List of Inferno applications

History

[edit]
Lucent advertisement for Inferno inIEEE Internet Computing, Volume 1, Number 2, March–April 1997

Inferno is a descendant ofPlan 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 theUnix philosophy. Many of the command line tools in Inferno were Plan 9 tools that were translated to Limbo.

In the mid-1990s, Plan 9 development was set aside in favor of Inferno.[14]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 companyAT&T licensed Java technology fromSun Microsystems.[15]

In March–April 1997IEEE Internet Computing included an advertisement 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,–aPlayStation 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, and the Lucent Pathstar phone switch. 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 timeSun Microsystems was heavily marketing its ownJava programming language, which was targeting a similar market, with analogous technology, that worked inweb browsers and also filled the demand forobject-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. However, Inferno still did not find customers.

The Inferno Business Unit closed after three years, and was sold to Vita Nuova Holdings. Vita Nuova continued development and offered commercial licenses to the complete system, and free downloads and licenses (notGPL compatible) for all of the system except the kernel and VM. They ported the software to new hardware and focused on distributed applications. Eventually, Vita Nuova released the 4th edition under more commonfree software licenses, and in 2021 they relicensed all editions under mainly theMIT License.[6][2][3]

Release timeline
DateReleaseComment
1996Inferno BetaReleased by Bell Labs
May 1997Inferno Release 1.0Winter 1997 Bell Labs Technical Journal Article
July 1999Inferno 2nd EditionReleased by Lucent's Inferno Business Unit
June 2001Inferno 3rd EditionReleased by Vita Nuova
2004Inferno 4th EditionOpen Source release; changes to many interfaces (incompatible with earlier editions); includes support for 9P2000.

Ports

[edit]

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 include these architectures:x86,MIPS,ARM,PowerPC,SPARC.

Hosted or virtual OS ports include:Microsoft Windows,Linux,FreeBSD,Plan 9,Mac OS X,Solaris,IRIX,UnixWare.

Inferno can also be hosted by aplugin toInternet Explorer.[16] Vita Nuova said that plugins for other browsers were under development, but they were never released.[17]

Inferno has also been ported toOpenmoko,[18]Nintendo DS,[19]SheevaPlug,[20] andAndroid.[21][22]

Distribution

[edit]

Inferno 4th edition was released in early 2005 asfree software. Specifically, it wasdual-licensed under two structures.[6] Users could either obtain it under a set offree 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 theGNU General Public License, theGNU Lesser General Public License, theLucent Public License, and theMIT License, excluding the fonts, which are sub-licensed from Bigelow and Holmes.

In March 2021, all editions were relicensed under mainly theMIT License.[2][3]

See also

[edit]

Notes

[edit]
  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

[edit]
  1. ^abDorward, Sean; Pike, Rob; Presotto, David Leo; Ritchie, Dennis M.; Trickey, Howard; Winterbottom, Phil (1997)."The Inferno Operating System".Inferno Documentation. Vita Nuova. Retrieved2014-05-02.
  2. ^abcd"Inferno Licence Terms". Archived fromthe original on 2021-04-27. Retrieved2021-06-17.The bulk of Inferno 4th Edition is provided under the `MIT' licence.
  3. ^abcd"GitHub - inferno-os/inferno-os". Retrieved2025-10-05.
  4. ^"Inferno Licence Terms". Archived fromthe original on 2005-08-11.The Free Software Scheme" and "Commercial Developer Licence
  5. ^"Vita Nuova Commercial Developer License - 9 November 2005". Archived fromthe original on 2006-05-02.
  6. ^abc"Inferno Licence Terms". Archived fromthe 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 fromthe original on 2005-04-05.
  8. ^"Vita Nuova Liberal Source License - 14 May 2003". Archived fromthe original on 2004-02-23.
  9. ^"Vita Nuova Commercial Developer License - 22 April 2003". Archived fromthe original on 2004-06-25.
  10. ^"Vita Nuova Inferno Subscription Licence". Archived fromthe original on 2000-12-08.
  11. ^Huelsbergen, Lorenz; Winterbottom, Phil (1998).Very Concurrent Mark and Sweep Garbage Collection without Fine-Grain Synchronization(PDF). 1998 International Symposium on Memory Management.
  12. ^abcdeDorward, Steven; Fioravanti, Alan; Nehab, Marcelo; Pike, Rob; Trickey, Howard; Winterbottom, Phil (1997). "The Inferno Operating System".Bell Labs Technical Journal.2 (1):5–18.
  13. ^abcd"Inferno". Retrieved2025-08-03.
  14. ^Pontin, Jason (19 February 1996)."AT&T reveals plans for Java competitor".InfoWorld. p. 3.
  15. ^Hayes, Frank (19 February 1996)."Bell Lab's Inferno aims to rival Java".Computerworld. p. 6.
  16. ^"Supporting code to allow Inferno to act as a plugin in various browsers".
  17. ^"Inferno - Plug-in".Vita Nuova. Archived fromthe original on 2021-05-08.
  18. ^"inferno-openmoko - inferno for openmoko neo freerunner - Google Project Hosting". Retrieved2012-06-04.
  19. ^Lukkien, Mechiel (2024-01-22),mjl-/inferno-ds, retrieved2024-01-25
  20. ^"inferno-kirkwood - Inferno for the Marvell Kirkwood/Sheevaplug - Google Project Hosting". Retrieved2012-06-04.
  21. ^"Inferno OS Running On Android Phones". Slashdot. 2011-09-17. Retrieved2025-10-05.
  22. ^John Floren (2011-09-16)."Announcing Inferno for Android phones". Retrieved2025-10-05.

Further reading

[edit]
  • 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 versatilecommand 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.

External links

[edit]
Wikimedia Commons has media related toInferno (operating system).
Operating systems
Programming languages
Software
Publications
Other
Current
Historic
Projects
General
Software
packages
Community
Organisations
Licenses
Types and
standards
Challenges
Related
topics
Retrieved from "https://en.wikipedia.org/w/index.php?title=Inferno_(operating_system)&oldid=1336470934"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp