About site: Software/Operating Systems/Realtime/EROS - Extremely Reliable Operating System

About site: http://en.wikipedia.org/wiki/Extremely_Reliable_Operating_System

Title: Software/Operating Systems/Realtime/EROS - Extremely Reliable Operating System Growing article, with links to many related topics. Wikipedia.

KeyKOS Persistent, pure capability, microkernel OS. EROS's famous predecessor.

Verifying_Operating_System_Security A confined program is one unable to leak information to an unauthorized party or modify unauthorized resources, an essential feature of any secure component based system. A proof of correctness of ERO

EROS__A_Principle-Driven_Operating_System_from_the_Ground_Up Abstract of article by Jonathan S. Shapiro, Norm Hardy; published by IEEE Computer Society. [IEEE Software] (February, 2002)

The_EROS_Alternative Shapiro interview in 'Open-Source Security' issue. Of open source OSs, most people think only Linux and OpenBSD. But another open-source OS's architecture may be more secure than either of them. [Info

DR-DOS Growing article, with links to many related topics. Wikipedia.

DRDOS,_Inc_ Makes: DR-DOS, compact, Y2K safe, good for embedded or thin-client systems, source code available, development kits, older and localized versions; and DRLX embedded Linux, load and run Linux programs

Alexa statistic for http://en.wikipedia.org/wiki/Extremely_Reliable_Operating_System

Please visit: http://en.wikipedia.org/wiki/Extremely_Reliable_Operating_System

Related sites for http://en.wikipedia.org/wiki/Extremely_Reliable_Operating_System

DR-DOS_Wiki Information of many types on DR-DOS, Enhanced DR-DOS, OpenDOS, NovellDOS.

The_DR-DOS/OpenDOS_Enhancement_Project Goal: continue development, enhance abilities of, add support for new standards to, extend life of this DOS under open source license. Descriptions, downloads of latest versions: source code, binaries

OpenDOS Growing article, with links to many related topics. Wikipedia.

OpenDOS_Stuff News, FAQ and mail archives.

OpenDOS_Unofficial_Page Descriptions, Q&A, downloads, mail lists, programming information. Not up-to-date, but has useful information, some of historical interest.

Unofficial_DR-DOS_Resources Links, install and use tips, FAQ; mail lists, newsgroups, fora; downloads: images, source code; tools.

Bug_reports_for_the_GNU_Hurd_Archives Archived discussions and reports of bugs for Hurd project. May be searched by user.

Debian Download site for Debian Hurd CDs. Offers software downloads, support, documentation and news.

Debian_GNU_Hurd Free distribution of the original GNU operating system under name of Debian, maintained and updated by many users who volunteer their knowledge, time and effort. The Hurd is a set of servers running o

The_Easy_Guide_to_Installing_Hurd_on_a_Linux_Box A step-by-step guide to installing Hurd on a linux box, assuming no prior knowledge.

Edrx\'s_Hurd_Page Many useful GNU Hurd related links, not well structured.

The_GNU_Hurd The GNU project's replacement for the Unix kernel. The Hurd is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other fea

GNU_Hurd_0_2_Kernel_Source_Tour Browseable Web interface to full Hurd source tree, with a fully functioning Function Search function.

GNU_Hurd_Hardware_Compatibility_Guide A list of hardware that is known to be supported by the GNU Mach microkernel.

GNU_Hurd_Mailing_List Mailing list archives.

GNU_India Gateway focusing on developing, distributing, and testing the GNU OS. Includes links to documentation, projects and also offers a mailing list and contact information.

Gnufans___Hurd___WebHome Gnufans host of the Hurd webpage. It contains many new updates.

Gnu/Hurd Comprehensive collection of GNU Hurd links.

Hurd A basic introduction to the Hurd project.

The_Hurd_Development_and_Information_Links Offers a large good collection of Hurd links.

Hurd_hacking_guide Offers guidelines on design and implementation of GNU Hurd.

The_Hurd_on_L4 Porting the Hurd to the L4 microkernel. News, plans, pointers to mailing lists and websites.

Okuji_-_enbug_org Information on free software, GNU Hurd, GNU GRUB, GNU Mach, and microkernels.

Toronto_Hurd_Group An area group willing to help new users to run GNU/Hurd and to develope software for GNU/Hurd. Offers links to related files, support, mailing lists, bug documentation, current tasks and news.

Towards_a_New_Strategy_of_OS_Design A technical article on the Hurd.

Arch_Rock_Corp_ Systems and software firm; builds innovative products and technology for wireless sensor network, to bridge the physical and digital worlds. San Francisco, California, USA.

Berkeley_WEbS__Wireless_Embedded_Systems Berkeley resources for DARPA Project: Secure Language-Based Adaptive Platform for Network Embedded Systems.

Brainy_Buildings_Conserve_Energy Discusses saving energy in buildings by distributed sensor networks featuring TinyOS.

Crossbow_Technology,_Inc_ Makes scalable product set of: hardware and software development platforms, full product designs, production and professional services, to help OEMs and system integrators bring end-to-end wireless se

David_Culler\'s_Page Leader in worldwide TinyOS community, Professor, University of California, Berkeley, teaches wireless embedded networking, deeply embedded network systems; also works at Arch Rock Corp.

An_Empirical_Evaluation_of_TinyOS_RF_Networking,_and_Beyond Context, particularly location, is an important source of information for human-computer interaction. In our project, we examine hardware, networking, and systems issues for a location sensing infrast

Large_Scale_Deeply_Embedded_Networks Graduate seminar on dense collections of smart sensors, processors, and actuators, networked to form self-configuring teams. Provides basis for new computing paradigm that challenges many classical ap

Maxfor_Technology,_Inc_ Makes sensor network parts: processor radio platforms, interface and sensor boards. Seongnam-City, Gyeonggi-Do, Korea.

Moteiv_Corp_ Makes Tmote wireless products for sensor network applications, Boomerang TinyOS distribution. San Francisco, California, USA.

SourceForge__TinyOS Project summary, downloads, administrator contacts. Because size DOES matter.

System_Architecture_Directions_for_Networked_Sensors Brief technical description with a useful photograph and diagram. [PDF]

TinyECC__Elliptic_Curve_Cryptography_on_TinyOS Software package, supports all elliptic curve operations over Fp (point addition/doubling, scalar point multiplication); ECDSA operations over Fp (signature generation, verification). To add other ECC

TinyOS Growing article, with links to many related topics. Wikipedia.

TinyOS__An_Operating_System_for_Networked_Sensors Project page of project participant Jason Hill. Explanations and diagrams: mote active messages and ad hoc routing, CompGlue graphical system to graphically connect and include components via VHDL har

Get_Out_the_Mote Article describes basics of sensor motes and TinyOS simply. PC Magazine. (July 13, 2004)

This is now2007.com cache of m/ as retrieved on 2008.11.22 now2007.com's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.

EROS (microkernel) - Wikipedia, the free encyclopedia /**/ /**/ if (wgNotice != '') document.writeln(wgNotice);

EROS (microkernel)

From Wikipedia, the free encyclopedia (Redirected from Extremely Reliable Operating System) Jump to: navigation, search EROS (The Extremely Reliable Operating System) is an operating system developed by The EROS Group, LLC., the Johns Hopkins University, and the University of Pennsylvania. Interesting features include automatic data and process persistence, some preliminary real-time support, and capability-based security. EROS is purely a research operating system, and was never deployed in real world use. As of 2005[update], development has stopped in favor of two successor systems, CapROS and Coyotos.

1 Key concepts2 History3 Status4 See also5 References5.1 Journals6 External links//

[edit] Key concepts

The overriding goal of the EROS system (and its relatives) is to provide strong support at the operating system level for the efficient restructuring of critical applications into small communicating components. Each component can communicate with the others only through protected interfaces, and is isolated from the rest of the system. A "protected interface", in this context, is one that is enforced by the lowest level part of the operating system (the kernel). The kernel is the only portion of the system that can move information from one process to another. It also has complete control of the machine and (if properly constructed) cannot be bypassed. In EROS, the kernel-provided mechanism by which one component names and invokes the services of another is capabilities using inter-process communication (IPC). By enforcing capability-protected interfaces, the kernel ensures that all communications to a process arrive via an intentionally exported interface. It also ensures that no invocation is possible unless the invoking component holds a valid capability to the invokee. Protection in capability systems is achieved by restricting the propagation of capabilities from one component to another, often through a security policy known as confinement.Capability systems naturally promote component-based software structure. This organizational approach is similar to the programming language concept of object-oriented programming, but occurs at larger granularity and does not include the concept of inheritance. When software is restructured in this way, several benefits emerge:The individual components are most naturally structured as event loops. Examples of systems that are commonly structured this way include flight control systems (see also DO-178B Software Considerations in Airborne Systems and Equipment Certification), and telephone switching systems (see 5ESS switch). Event-driven programming is chosen for these systems primarily because of simplicity and robustness, which are essential attributes in life-critical and mission-critical systems.Components become smaller and individually testable, which helps the implementor to more readily identify flaws and bugs.The isolation of each component from the others limits the scope of the damage that may occur when something goes wrong or the software misbehaves.Collectively, these benefits lead to measurably more robust and secure systems. The SDS Sigma 7 was a hardware-based capability system originally designed for use in telephony switches. A capability-based design was chosen specifically for reasons of robustness.In contrast to many earlier systems, capabilities are the only mechanism for naming and using resources in EROS. Such a system is sometimes referred to as a pure capability system. The IBM AS/400 is an example of a commercially successful capability system, but it is not a pure capability system.Pure capability architectures are supported by well-tested and mature mathematical security models. These have been used to formally demonstrate that capability-based systems can be made secure if implemented correctly. The so-called "safety property" has been shown to be decidable for pure capability systems (see Lipton). Confinement, which is the fundamental building block of isolation, has been formally verified to be enforceable by pure capability systems,[1] and is reduced to practical implementation by the EROS "constructor" and the KeyKOS "factory". No comparable verification exists for any other primitive protection mechanism. There is a fundamental result in the literature showing that "safety" is mathematically undecidable in the general case (see HRU, but note that it is of course provable for an unbounded set of restricted cases[2]). Of greater practical importance, safety has been shown to be false for all of the primitive protection mechanisms shipping in current commodity operating systems (see HRU). Safety is a necessary precondition to successful enforcement of any security policy. In practical terms, this result means that it is not possible in principle to secure current commodity systems, but it is potentially possible to secure capability-based systems provided they are implemented with sufficient care. Neither system has ever been successfully penetrated, and their isolation mechanisms have never been successfully defeated by any inside attacker, but it is not known whether the EROS or KeyKOS implementations was careful enough. One goal of the Coyotos project is to demonstrate that component isolation and security has been definitively achieved by apply software verification techniques.The L4.sec system, which is a successor to the L4 microkernel family, is a capability-based system, and has been significantly influenced by the results of the EROS project. The influence is mutual, since the EROS work on high-performance invocation was motivated strongly by Jochen Liedtke's successes with the L4 microkernel family.

[edit] History

The primary developer of EROS was Jonathan S. Shapiro. He is also the driving force behind Coyotos, which is a "evolutionary step"[3] beyond the EROS operating system.The EROS project started in 1991 as a clean-room reconstruction of an earlier system, KeyKOS. KeyKOS was an operating system developed by Key Logic, Inc., and was a direct continuation of work on the earlier GNOSIS (Great New Operating System In the Sky) system created by Tymshare, Inc. The KeyKOS system offered a degree of security and reliability that remains unduplicated today (2006).[citation needed] The circumstances surrounding Key Logic's unfortunate demise in 1991 made licensing KeyKOS impractical. Since KeyKOS did not run on popular commodity processors in any case, the decision was made to reconstruct it from the publicly available documentation.By late 1992, it had become clear that processor architecture had changed significantly since the introduction of the capability idea, and it was no longer obvious that component-structured systems were practical. Microkernel-based systems, which similarly favor large numbers of processes and IPC, were facing severe performance challenges, and it was uncertain if these could be successfully resolved. The x86 architecture was clearly emerging as the dominant architecture but the expensive user/supervisor transition latency on the 386 and 486 presented serious challenges for process-based isolation. The EROS project was turning into a research effort, and moved to the University of Pennsylvania to become the focus of Shapiro's dissertation research. By 1999, a high performance implementation for the Pentium processor had been demonstrated that was directly performance competitive with the L4 microkernel family, which is known for its exceptional speed in IPC. The EROS confinement mechanism had been formally verified, in the process creating a general formal model for secure capability systems.In 2000, Shapiro joined the faculty of Computer Science at Johns Hopkins University. At Hopkins, the goal was to show how to use the facilities provided by the EROS kernel to construct secure and defensible servers at application level. Funded by the Defense Advanced Research Projects Agency and the Air Force Research Laboratory, EROS was used as the basis for a trusted window system,[4] a high-performance, defensible network stack,[5] and the beginnings of a secure web browser. It was also used to explore the effectiveness of lightweight static checking.[6] In 2003, some very challenging security issues were discovered[7] that are intrinsic to any system architecture based on synchronous IPC primitives (notably including EROS and L4). Work on EROS halted in favor of Coyotos, which resolves these issues.As of 2006[update], EROS and its successors are the only widely available capability systems that run on commodity hardware.

[edit] Status

Work on EROS by the original group has halted, but there are two successor systems. The CapROS system is building directly from the EROS code base, while the Coyotos system is a successor system that addresses some of the architectural deficiencies of EROS, and is exploring (as research) the possibility of a fully verified operating system. Both CapROS and Coyotos are expected to be released in various commercial deployments.

[edit] See also

Nanokernel

[edit] References

^ Verifying the EROS Confinement Mechanism^ Peter Lee: Proof-Carrying Code^ Differences Between Coyotos and EROS — A Quick Summary^ http://www.eros-os.org/papers/usenix-sec2004.ps^ http://www.eros-os.org/papers/usenix-net-2004.ps^ http://www.eros-os.org/papers/ccs04.pdf^ http://www.eros-os.org/papers/IPC-Assurance.ps[edit] JournalsR. J. Lipton and L. Snyder. "A Linear Time Algorithm for Deciding Subject Security." Journal of the ACM, 24'(3):455--464, 1977.M. A. Harrison, W. L. Ruzzo and J. D. Ullman. "Protection in Operating Systems". Communications of ACM. 19(8):461--471, August 1976.

[edit] External links

Coyotos home pageEROS home pageKeyKOS home pageJonathan Shapiro's homepageCapROSv • d • eReal-time operating systems (RTOS)ChibiOS/RT · Contiki · DNIX · DSOS · eCos · Embedded Linux · EROS · FreeRTOS · LynxOS · MenuetOS · MERT · Nucleus RTOS · Open AT OS · OS-9 · OSE · pSOS · Prex · QNX · RMX · RSX-11 · RT-11 · RTEMS · RTLinux · SINTRAN III · Symbian OS · Talon DSP RTOS · THEOS · TPF · TRON · VRTX · VxWorks · Windows CERetrieved from "http://en.wikipedia.org/wiki/EROS_(microkernel)" Categories: Microkernels | Real-time operating systems | Capability systemsHidden categories: Articles containing potentially dated statements from 2005 | All articles containing potentially dated statements | All articles with unsourced statements | Articles with unsourced statements since February 2007 | Articles containing potentially dated statements from 2006 Views Article Discussion Edit this page History Personal tools Log in / create account if (window.isMSIE55) fixalpha(); Navigation Main page Contents Featured content Current events Random article Search Interaction About Wikipedia Community portal Recent changes Contact Wikipedia Donate to Wikipedia Help Toolbox What links here Related changesUpload fileSpecial pages Printable version Permanent linkCite this page Languages Česky Deutsch Português Русский Powered by MediaWiki

This page was last modified on 21 November 2008, at 20:42. All text is available under the terms of the GNU Free Documentation License. (See Copyrights for details.) Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a U.S. registered 501(c)(3) tax-deductible nonprofit charity. Privacy policy About Wikipedia Disclaimers if (window.runOnloadHook) runOnloadHook();

Growing	article,	with	links
to	many	related	topics.	Wikipedia.

http://en.wikipedia.org/wiki/Extremely_Reliable_Operating_System

Extremely Reliable Operating System 2008 November

dvd rental

dvd

Growing article, with links to many related topics. Wikipedia.

Rules

Recommended Sites: 1. Arts - Business - Computers - Games - Health - Home - Kids and Teens - News - Recreation - Reference - Regional - Science - Shopping - Society - Sports - World Miss Gallery - Top Anime Hentai - DVD rental by mail - Loans Bad Credit - Bad Credit Mortgages - Yugioh - Loans - Debt Help

2008-11-22 00:32:03

Copyright 2005, 2006 by Webmaster
Websites is cool :)