DOCSLIB.ORG

Microkernel Construction

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microkernel Construction Microkernel Construction Introduction Hermann Härtig SS2012 Torsten Frenzel TU Dresden Operating Systems Group Microkernel Construction ClassClass GoalsGoals Provide deeper understanding of OS mechanisms Introduce L4 principles and concepts Make you become enthusiastic L4 hackers Propaganda for OS research at TU Dresden Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 2 Microkernel Construction AdministrationAdministration Thursday, 4th DS, 2 SWS Slides: http://www.tudos.org → Teaching → Microkernel Construction Subscribe to our mailing list: http://www.tudos.org/mailman/listinfo/mkc2012 In winter term: – Construction of Microkernel-based Systems (2 SWS) – Various Labs Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 3 Microkernel Construction „„Monolithic“Monolithic“ KernelKernel SystemSystem DesignDesign Application ApplicationApplication Application Unprivileged Mode Privileged File Network Mode Systems Subsystem Memory Process Drivers Management Management Monolithic Kernel Hermann Härtig Torsten Hardware Frenzel TU Dresden Operating Systems Group 4 Microkernel Construction MonolithicMonolithic KernelKernel OSOS (Propaganda)(Propaganda) System components run in privileged mode ➔ No protection between system components – Faulty driver can crash the whole system – More than 2/3 of today's OS code are drivers ➔ No need for good system design – Direct access to data structures – Undocumented and frequently changing interfaces ➔ Big and inflexible – Difficult to replace system components Why something different? Hermann Härtig More and more difficult to manage increasing OS Torsten Frenzel complexity TU Dresden Operating Systems Group 5 Microkernel Construction MicrokernelMicrokernel SystemSystem DesignDesign Application Application Application File Network Systems Stacks Memory Process Management Management Drivers Unprivileged System Services Mode Privileged Tasks Threads IPC Scheduling Mode Hermann Härtig Microkernel Torsten Frenzel Hardware TU Dresden Operating Systems Group 6 Microkernel Construction ExampleExample –– IBMIBM WorkplaceWorkplace OSOS // MachMach OS/2 DOS OS/400 AIX Windows Application Application Application Application Application OS/2 DOS OS/400 Windows AIX Personality Personality Personality Personality Personality File Server Network Service Security Power Management Default Pager Device Support Bootstrap Name Service Hermann Mach Microkernel Härtig Torsten Frenzel ARM PowerPC IA32 MIPS Alpha TU Dresden Operating Systems Group 7 Microkernel Construction ExampleExample –– QNXQNX // NeutrinoNeutrino . Embedded systems Message passing system (IPC) Network transparency Application Application Application Filesystem Device Process Network Manager Manager Manager Manager Unprivileged Mode Privileged Interrupt Network IPC Scheduler Mode Redirector Driver Hermann Härtig Neutrino - Microkernel Torsten Frenzel Hardware TU Dresden Operating Systems Group 8 Microkernel Construction MoreMore InterestingInteresting Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 9 Microkernel Construction Example:Example: VPNVPN Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 10 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 11 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 12 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 13 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 14 Microkernel Construction MoreMore OnOn CriticalCritical ApplicationsApplications Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 15 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 16 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 17 Microkernel Construction VirtualVirtual PrivatePrivate FileFile SystemSystem Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 18 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 19 Microkernel Construction ShoppingShopping Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 20 Microkernel Construction Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 21 Microkernel Construction MicrokernelMicrokernel OSOS -- TheThe VisionVision (1)(1) System components run as user-level servers Protection and isolation between system components – More secure / safe systems – Less error prone – Small Trusted Computing Base „Enforces“ clear system design – Well defined interfaces to system services – No dependencies between system services other than explicitly specified through service interfaces Small and flexible – Small OS kernel Hermann Härtig – Easier to replace system components Torsten Frenzel TU Dresden Operating Systems Group 22 Microkernel Construction VisionsVisions vs.vs. RealityReality Flexibility and Customizable – Monolithic kernels are modular Maintainability and complexity – Monolithic kernel have layered architecture ✔ Robustness – Microkernels are superior due to isolated system components – Trusted code size (i386) • Fiasco kernel: about 15.000 loc • Linux kernel: about 300.000 loc (without drivers) Performance Hermann ✗ Härtig Torsten – Application performance degraded Frenzel – Communication overhead (see next slides) TU Dresden Operating Systems Group 23 Microkernel Construction RobustnessRobustness vs.vs. PerformancePerformance (1)(1) System calls – Monolithic kernel: 2 kernel entries/exits – Microkernel: 4 kernel entries/exits + 2 context switches Application Application 1 4 Driver Driver 2 3 Microkernel Monolithic kernel Hermann Härtig Torsten Frenzel HardwareHardware Hardware TU Dresden Operating Systems Group 24 Microkernel Construction RobustnessRobustness vs.vs. PerformancePerformance (2)(2) Calls between system services – Monolithic kernel: 1 function call – Microkernel: 4 kernel entries/exits + 2 context switches Network Network Driver Driver Subsystem Subsystem 1 4 2 3 Microkernel Monolithic kernel Hermann Härtig Torsten Hardware Hardware Frenzel TU Dresden Operating Systems Group 25 Microkernel Construction ChallengesChallenges Build functional powerful and fast microkernels – Provide abstractions and mechanisms – Fast communication primitive (IPC) – Fast context switches and kernel entries/exits ➔ Subject of this lecture Build efficient OS services – Memory Management – Synchronization – Device Drivers – File Systems Hermann – Communication Interfaces Härtig Torsten ➔ Frenzel Subject of lecture “Construction of Microkernel-based systems” (in winter term) TU Dresden Operating Systems Group 26 Microkernel Construction L4L4 MicrokernelMicrokernel FamilyFamily Originally developed by Jochen Liedtke (GMD / IBM Research) Current development: – Uni Karlsruhe: Pistachio – UNSW/NICTA/OKLABS: OKL4, SEL4, L4Verified – TU Dresden: Fiasco.OC, Nova Support for hardware architectures: – X86, ARM, ... Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 27 Microkernel Construction MoreMore MicrokernelsMicrokernels (Incomplete(Incomplete list)list) Commercial kernels – Singularity @ Microsoft Research – K42 @ IBM Research – velOSity/INTEGRITY @ Green Hills Software – Chorus/ChorusOS @ Sun Microsystems – PikeOS @ SYSGO AG – OKL4 Research kernels – EROS/CoyotOS @ John Hopkins University – Minix @ FU Amsterdam – Amoeba @ FU Amsterdam Hermann Härtig – Pebble @ Bell Labs Torsten Frenzel – Grasshopper @ University of Sterling – Flux/Fluke @ University of Utah TU Dresden Operating Systems Group 28 Microkernel Construction L4L4 -- ConceptsConcepts Jochen Liedtke: “A microkernel does no real work” – Kernel provides only inevitable mechanisms – No policies implemented in the kernel Abstractions – Tasks with address spaces – Threads executing programs/code Mechanisms – Resource access control – Scheduling – Communication (IPC) Hermann Härtig Torsten Frenzel TU Dresden Operating Systems Group 29 Microkernel Construction ThreadsThreads andand TasksTasks Task A Task B User User Code Code Thread2 User User User Stack Stack Stack Kernel Code Thread1 Thread3 Hermann Kernel Kernel Kernel Härtig Torsten Stack Stack Stack Frenzel Microkernel TU Dresden Operating Systems Group 30 Microkernel Construction ThreadsThreads (1)(1) Represent unit of execution – Execute user code (application) – Execute kernel code (system calls, page faults, interrupts, exceptions) Subject to scheduling – Quasi-parallel execution on one CPU – Parallel execution on multiple CPUs – Voluntarily switch to another thread possible – Preemptive scheduling by the kernel according to certain parameters Associated with an address space Hermann – Executes code in one task at one point in time Härtig Torsten • Migration allows threads move to another task Frenzel – Several threads can execute in one task TU Dresden Operating Systems Group 31 Microkernel Construction TasksTasks (1)(1) Represent domain of protection and isolation Container for code, data and resources Address space: capabilities + memory pages Three management operations: – Map: share page with other address space – Grant: give page to other address space – Unmap: revoke previously mapped page X X X grant unmap Hermann map Härtig Torsten Frenzel X X X TU Dresden Operating Systems Group 32 Microkernel Construction RecursiveRecursive AddressAddress SpacesSpaces Application 1 Application 2 Pager 3 Pager 1 Pager 2 Initial Pager Hermann Härtig
Load more

Recommended publications
  • A Programmable Microkernel for Real-Time Systems∗
    A Programmable Microkernel for Real-Time Systems∗ Christoph M. Kirsch Marco A.A. Sanvido Thomas A. Henzinger University of Salzburg VMWare Inc. EPFL and UC Berkeley [email protected] tah@epfl.ch ABSTRACT Categories and Subject Descriptors We present a new software system architecture for the im- D.4.7 [Operating Systems]: Organization and Design— plementation of hard real-time applications. The core of the Real-time systems and embedded systems system is a microkernel whose reactivity (interrupt handling as in synchronous reactive programs) and proactivity (task General Terms scheduling as in traditional RTOSs) are fully programma- Languages ble. The microkernel, which we implemented on a Strong- ARM processor, consists of two interacting domain-specific Keywords virtual machines, a reactive E (Embedded) machine and a proactive S (Scheduling) machine. The microkernel code (or Real Time, Operating System, Virtual Machine microcode) that runs on the microkernel is partitioned into E and S code. E code manages the interaction of the system 1. INTRODUCTION with the physical environment: the execution of E code is In [9], we advocated the E (Embedded) machine as a triggered by environment interrupts, which signal external portable target for compiling hard real-time code, and in- events such as the arrival of a message or sensor value, and it troduced, in [11], the S (Scheduling) machine as a universal releases application tasks to the S machine. S code manages target for generating schedules according to arbitrary and the interaction of the system with the processor: the exe- possibly non-trivial strategies such as nonpreemptive and cution of S code is triggered by hardware interrupts, which multiprocessor scheduling.
    [Show full text]
  • The Design of the EMPS Multiprocessor Executive for Distributed Computing
    The design of the EMPS multiprocessor executive for distributed computing Citation for published version (APA): van Dijk, G. J. W. (1993). The design of the EMPS multiprocessor executive for distributed computing. Technische Universiteit Eindhoven. https://doi.org/10.6100/IR393185 DOI: 10.6100/IR393185 Document status and date: Published: 01/01/1993 Document Version: Publisher’s PDF, also known as Version of Record (includes final page, issue and volume numbers) Please check the document version of this publication: • A submitted manuscript is the version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the publisher's website. • The final author version and the galley proof are versions of the publication after peer review. • The final published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal.
    [Show full text]
  • Ebook - Informations About Operating Systems Version: August 15, 2006 | Download
    eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org AIX Internet: AIX AmigaOS Internet: AmigaOS AtheOS Internet: AtheOS BeIA Internet: BeIA BeOS Internet: BeOS BSDi Internet: BSDi CP/M Internet: CP/M Darwin Internet: Darwin EPOC Internet: EPOC FreeBSD Internet: FreeBSD HP-UX Internet: HP-UX Hurd Internet: Hurd Inferno Internet: Inferno IRIX Internet: IRIX JavaOS Internet: JavaOS LFS Internet: LFS Linspire Internet: Linspire Linux Internet: Linux MacOS Internet: MacOS Minix Internet: Minix MorphOS Internet: MorphOS MS-DOS Internet: MS-DOS MVS Internet: MVS NetBSD Internet: NetBSD NetWare Internet: NetWare Newdeal Internet: Newdeal NEXTSTEP Internet: NEXTSTEP OpenBSD Internet: OpenBSD OS/2 Internet: OS/2 Further operating systems Internet: Further operating systems PalmOS Internet: PalmOS Plan9 Internet: Plan9 QNX Internet: QNX RiscOS Internet: RiscOS Solaris Internet: Solaris SuSE Linux Internet: SuSE Linux Unicos Internet: Unicos Unix Internet: Unix Unixware Internet: Unixware Windows 2000 Internet: Windows 2000 Windows 3.11 Internet: Windows 3.11 Windows 95 Internet: Windows 95 Windows 98 Internet: Windows 98 Windows CE Internet: Windows CE Windows Family Internet: Windows Family Windows ME Internet: Windows ME Seite 1 von 138 eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org Windows NT 3.1 Internet: Windows NT 3.1 Windows NT 4.0 Internet: Windows NT 4.0 Windows Server 2003 Internet: Windows Server 2003 Windows Vista Internet: Windows Vista Windows XP Internet: Windows XP Apple - Company Internet: Apple - Company AT&T - Company Internet: AT&T - Company Be Inc. - Company Internet: Be Inc. - Company BSD Family Internet: BSD Family Cray Inc.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Occupational Health and Safety Risks in the Healthcare Sector
    Occupational health and safety risks in the healthcare sector Guide to prevention and good practice This publication is supported by the European Union Programme for Employment and Social Solidarity - PROGRESS (2007-2013). This programme is implemented by the European Commission. It was established to financially support the implementation of the objectives of the European Union in the employment, social affairs and equal oppor- tunities area, and thereby contribute to the achievement of the Europe 2020 Strategy goals in these fields. The seven-year Programme targets all stakeholders who can help shape the development of appropriate and effective employment and social legislation and policies, across the EU-27, EFTA-EEA and EU candidate and pre-candidate countries. For more information see: http://ec.europa.eu/progress Occupational health and safety risks in the healthcare sector European Commission Directorate-General for Employment, Social Affairs and Inclusion Unit B.3 Manuscript completed in December 2010 Neither the European Commission nor any person acting on behalf of the Commission may be held responsible for the use that may be made of the information contained in this publication. © Cover photos: iStock For any use or reproduction of photos which are not under European Union copyright, permission must be sought directly from the copyright holder(s). This guide has been produced by the Bundesanstalt für Arbeitsschutz und Arbeitsmedizin (BAuA), Berufsgenossenschaft für Gesundheitsdienst und Wohlfahrtspflege (BGW), contec Gesellschaft für Organisationsentwicklung mbH, Deutsches Netz Gesundheitsfördernder Krankenhäuser (DNGfK) and BAD/ Team Prevent GmbH. Europe Direct is a service to help you find answers to your questions about the European Union Freephone number (*): 00 800 6 7 8 9 10 11 (*) Certain mobile telephone operators do not allow access to 00 800 numbers or these calls may be billed.
    [Show full text]
  • Rights Reserved. Permission to Make Digital Or Hard Copies of All Or Part Of
    Copyright © 1994, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 MICROSOFT WINDOWS NT AND THE COMPETITION FOR DESKTOP COMPUTING by Brad Peters, William R. Bush, and A. Richard Newton Memorandum No. UCB/ERL M94/3 31 January 1994 ELECTRONICS RESEARCH LABORATORY College ofEngineering University ofCalifornia, Berkeley 94720 Microsoft Windows NT And The Competition for Desktop Computing January 1994 Department ofElectrical Engineering and Computer Sciences University ofCalifornia Berkeley, California 94720 Abstract This report contains two papers, An Introduction to Microsoft Windows NT And Its Competitors, and The Status ofWindows NT and Its Competitors At The End of1993. The first paper, written in April 1993,presents an overview of the technology of Windows NT, and analyzes the competitors and competitive factors in the desktop operating system race.
    [Show full text]
  • Research Purpose Operating Systems – a Wide Survey
    GESJ: Computer Science and Telecommunications 2010|No.3(26) ISSN 1512-1232 RESEARCH PURPOSE OPERATING SYSTEMS – A WIDE SURVEY Pinaki Chakraborty School of Computer and Systems Sciences, Jawaharlal Nehru University, New Delhi – 110067, India. E-mail: [email protected] Abstract Operating systems constitute a class of vital software. A plethora of operating systems, of different types and developed by different manufacturers over the years, are available now. This paper concentrates on research purpose operating systems because many of them have high technological significance and they have been vividly documented in the research literature. Thirty-four academic and research purpose operating systems have been briefly reviewed in this paper. It was observed that the microkernel based architecture is being used widely to design research purpose operating systems. It was also noticed that object oriented operating systems are emerging as a promising option. Hence, the paper concludes by suggesting a study of the scope of microkernel based object oriented operating systems. Keywords: Operating system, research purpose operating system, object oriented operating system, microkernel 1. Introduction An operating system is a software that manages all the resources of a computer, both hardware and software, and provides an environment in which a user can execute programs in a convenient and efficient manner [1]. However, the principles and concepts used in the operating systems were not standardized in a day. In fact, operating systems have been evolving through the years [2]. There were no operating systems in the early computers. In those systems, every program required full hardware specification to execute correctly and perform each trivial task, and its own drivers for peripheral devices like card readers and line printers.
    [Show full text]
  • All Computer Applications Need to Store and Retrieve Information
    MyFS: An Enhanced File System for MINIX A Dissertation Submitted in partial fulfillment of the requirement for the award of the degree of MASTER OF ENGINEERING ( COMPUTER TECHNOLOGY & APPLICATIONS ) By ASHISH BHAWSAR College Roll No. 05/CTA/03 Delhi University Roll No. 3005 Under the guidance of Prof. Asok De Department Of Computer Engineering Delhi College Of Engineering, New Delhi-110042 (University of Delhi) July-2005 1 CERTIFICATE This is to certify that the dissertation entitled “MyFS: An Enhanced File System for MINIX” submitted by Ashish Bhawsar in the partial fulfillment of the requirement for the award of degree of Master of Engineering in Computer Technology and Application, Delhi College of Engineering is an account of his work carried out under my guidance and supervision. Professor D. Roy Choudhury Professor Asok De Head of Department Head of Department Department of Computer Engineering Department of Information Technology Delhi College of Engineering Delhi College of Engineering Delhi Delhi 2 ACKNOWLEDGEMENT It is a great pleasure to have the opportunity to extent my heartiest felt gratitude to everybody who helped me throughout the course of this project. I would like to express my heartiest felt regards to Dr. Asok De, Head of the Department, Department of Information Technology for the constant motivation and support during the duration of this project. It is my privilege and owner to have worked under the supervision. His invaluable guidance and helpful discussions in every stage of this thesis really helped me in materializing this project. It is indeed difficult to put his contribution in few words. I would also like to take this opportunity to present my most sincere regards to Dr.
    [Show full text]
  • Microkernel Construction Introduction
    Microkernel Construction Introduction Nils Asmussen 04/09/2020 1 / 32 Normal Organization Thursday, 4th DS, 2 SWS Slides: www.tudos.org ! Studies ! Lectures ! MKC Subscribe to our mailing list: www.tudos.org/mailman/listinfo/mkc2020 In winter term: Microkernel-based operating systems (MOS) Various labs 2 / 32 Organization due to COVID-19 Slides and video recordings of lectures will be published Questions can be asked on the mailing list Subscribe to the mailing list! Practical exercises are planed for the end of the semester Depending on how COVID-19 continues, exercises are in person or we use some video-conferencing tool 3 / 32 Goals 1 Provide deeper understanding of OS mechanisms 2 Look at the implementation details of microkernels 3 Make you become enthusiastic microkernel hackers 4 Propaganda for OS research done at TU Dresden and Barkhausen Institut 4 / 32 Outline Organization Monolithic vs. Microkernel Kernel design comparison Examples for microkernel-based systems Vision vs. Reality Challenges Overview About L4/NOVA 5 / 32 Monolithic Kernel System Design u s Application Application Application e r k Kernel e r File Network n e Systems Stacks l m Memory Process o Drivers Management Management d e Hardware 6 / 32 Monolithic Kernel OS (Propaganda) System components run in privileged mode No protection between system components Faulty driver can crash the whole system Malicious app could exploit bug in faulty driver More than 2=3 of today's OS code are drivers No need for good system design Direct access to data structures Undocumented
    [Show full text]
  • Integrated Report 2019
    Integrated Report 2019 JP TOWER, 2-7-2 Marunouchi, Chiyoda-ku, Tokyo 100-7015, Japan Phone: +81-3-6250-2111 https://konicaminolta.com CONTENTS On the Release of Integrated Report 2019 1 On the Release of Integrated Report 2019 2 CONTENTS Konica Minolta’s Strengths 03 Since fiscal 2015, Konica Minolta has released annual reports (the name of these reports was changed to the and Value Creation 3 Konica Minolta Philosophy integrated report in 2017) that provide a comprehensive look at the Company's activities and philosophies. 7 Value Creation Process The fifth report is now available. We made this integrated report to be a communication tool to better 9 Konica Minolta's Strengths 1. Customer base familiarize stakeholders, including shareholders and investors, with Konica Minolta by systematically 11 Konica Minolta’s Strengths 2. Technical expertise organizing both financial and non-financial information. 13 Konica Minolta’s Strengths 3. Business Model The 2018 integrated report was externally well-received, winning recognition and awards that included Growth Strategy 15 the Special Award in the Nikkei Annual Report Awards conducted by Nikkei Inc., and the Excellence in 15 Medium Term Business Plan Integrated Reporting Prize at the 6th WICI Japan Awards for Excellence in Integrated Reporting. 17 Message from the CEO Integrated Report 2019 clarifies the Konica Minolta Group's strengths and value creation processes 25 Message from the CFO 29 while explaining the Group's medium- to long-term business strategy and pathway to value creation with a Special Topics Building High Value-Added Businesses focus on SHINKA 2019, the new Medium Term Business Plan formulated in 2017.
    [Show full text]
  • This Is a Fairy Tale •.• NOT! a Primer on Moving SAS® Applications
    This is a Fairy Tale•.• NOT! A Primer on Moving SAS® Applications Across Graphical Operating Systems James Hefner, Entergy Corporation, Beaumont, TX lineup. The PowerPC's PowerOpen operating system should be ABSTRACT able to run Windows, Windows NT, OS/2, Macintosh, and UNIX applications unmodified (using SoftPC to run Windows & OS/2 Currently, most SAS Software application developers have on~ apps). Current plans are to offer these new machines at prices one or two graphical operating systems (such as Microsoft that are highly competitive with the current top-of-the-!ine WindowsTN, or OSFlMoti~ to support. However, the pending offerings by IBM PC manufacturerS and Apple, nol 10 mention release of the SAS System for the Apple® Macintosh®I and the UNIX workstations. This could mean a change in the platform you introduction of new hardware and software such as the PowerPC are currently using, as well as the ability (or need) to be able to and Wabi, means that application developers may have to use and write applications using any of the five operating support two or more graphical operating systems. systems. This paper is intended to assist application developers, both in New Graphical Operating Systems the teaching of the fundamentals of graphical operating systems, and in Ihe moving of SAS/Af® and SAS/EIS® applicalions from In addition to the platforms mentioned above, Apple and IBM are one operating system to another. currently working on the Taligent operating system, which will have an object-oriented, graphical front end. IBM is also INTRODUCTION discussing porling its object·orienled 0512 2.x Workplace Shell 10 a new ver.sion of PC DOS® and AIX®, IBM's version of UNIX (to If you are a SAS' application developer, you may currently be be called Workplace OS).
    [Show full text]
  • Linux on the OSF Mach3 Microkernel
    Linux on top of the OSF Mach3 Microkernel Linux on top of the OSF Mach3 Microkernel Linux on top of OSF MK The Mach3.0 Microkernel: Design • microkernel abstractions François Barbou des Places ([email protected]) • task, thread, port, message, memory object Nick Stephen ([email protected]) • resources and services represented as ports OSF Research Institute - Grenoble • interfaces implemented via RPC to an object port Task Message • Objectives: • widen the audience for the free OSF micro-kernel Ports • provide a complete and free platform to develop new Threads servers, applications or kernel extensions • provide Apple with a freely redistributable microkernel-based operating system for the Memory Apple/PowerMac platform Object Freely Redistributable Software Conference - 5 Feb 1996 - Cambridge 1/17 Freely Redistributable Software Conference - 5 Feb 1996 - Cambridge 2/17 Linux on top of the OSF Mach3 Microkernel Linux on top of the OSF Mach3 Microkernel The Mach3.0 microkernel: Benefits OSF MK Improvements • portability (modular design) • performance • symmetric multi-processing support • kernel-loaded servers (collocation) • thread migration • scalability (from desktop PCs to high-end multi-computers) • short-circuited RPC • extensibility • real-time • OS-neutrality • preemptable kernel • support for OS personalities running as user tasks • real-time RPC, priority inheritance • pageable, preemptable • distributed system (clusters and multi-computers) • more portable: isolated from hardware • DIPC: transparent Distributed IPC • simpler:
    [Show full text]