DOCSLIB.ORG

SUSE Advanced Troubleshooting: the Boot Process Lecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SUSE Advanced Troubleshooting: the Boot Process Lecture SUSE Advanced Troubleshooting: The Boot Process Lecture Novell Training Services www.novell.com SUS21 ATT LIVE 2012 LAS VEGAS Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED. Proprietary Statement Disclaimer Copyright © 2011 Novell, Inc. All rights reserved. Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and Novell, Inc., has intellectual property rights relating to specifically disclaims any express or implied warranties technology embodied in the product that is described in of merchantability or fitness for any particular purpose. this document. In particular, and without limitation, these intellectual property rights may include one or more of Further, Novell, Inc., reserves the right to revise this the U.S. patents listed on the Novell Legal Patents Web publication and to make changes to its content, at any page (http://www.novell.com/company/legal/patents/) time, without obligation to notify any person or entity of and one or more additional patents or pending patent such revisions or changes. Further, Novell, Inc., makes applications in the U.S. and in other countries. no representations or warranties with respect to any software, and specifically disclaims any express or No part of this publication may be reproduced, implied warranties of merchantability or fitness for any photocopied, stored on a retrieval system, or transmitted particular purpose. Further, Novell, Inc., reserves the without the express written consent of the publisher. right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any Novell, Inc. person or entity of such changes. 404 Wyman Street, Suite 500 Waltham, MA 02451 Any products or technical information provided under this U.S.A. Agreement may be www.novell.com subject to U.S. export controls and the trade laws of Novell Trademarks other countries. You agree to comply with all export For Novell trademarks, see the Novell Trademark and control regulations and to obtain any required licenses or Service Mark list classification to export, re-export or import deliverables. (http://www.novell.com/company/legal/trademarks/tmlist. You agree not to export or re-export to entities on the html). current U.S. export exclusion lists or to any embargoed Third-Party Materials or terrorist countries as specified in the U.S. export laws. All third-party trademarks are the property of their You agree to not use deliverables for prohibited nuclear, respective owners. missile, or chemical biological weaponry end uses. See Software Piracy the Novell International Trade Services Web page Throughout the world, unauthorized duplication of (http://www.novell.com/info/exports/) for more software is subject to both information on exporting Novell software. Novell criminal and civil penalties. assumes no responsibility for your failure to obtain any necessary export approvals. If you know of illegal copying of software, contact your local Software Antipiracy Hotline. For the Hotline This Novell Training Manual is published solely to number for your area, access Novell’s World Wide Web instruct students in the use of Novell networking page (http://www.novell.com) and look for the piracy software. Although third-party application software page under “Programs.” packages are used in Novell training courses, this is for Or, contact Novell’s anti-piracy headquarters in the U.S. demonstration purposes only and shall not constitute an at 800-PIRATES (747-2837) or 801-861-7101. endorsement of any of these software applications. Further, Novell, Inc. does not represent itself as having any particular expertise in these application software packages and any use by students of the same shall be done at the student’s own risk. Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED. Proprietary Statement Disclaimer Copyright © 2011 Novell, Inc. All rights reserved. Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, Novell, Inc., has intellectual property rights relating to and specifically disclaims any express or implied technology embodied in the product that is described in warranties of merchantability or fitness for any particular this document. In particular, and without limitation, these purpose. intellectual property rights may include one or more of the U.S. patents listedFront on the Novell Legal Patents Web MatterFurther, Novell, Inc., reserves the right to revise this page (http://www.novell.com/company/legal/patents/) publication and to make changes to its content, at any and one or more additional patents or pending patent time, without obligation to notify any person or entity of applications in the U.S. and in other countries. such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any No part of this publication may be reproduced, software, and specifically disclaims any express or photocopied, stored on a retrieval system, or transmitted implied warranties of merchantability or fitness for any without the express written consent of the publisher. particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell Novell, Inc. software, at any time, without any obligation to notify any 404 Wyman Street, Suite 500 person or entity of such changes. Waltham, MA 02451 U.S.A. Any products or technical information provided under www.novell.com this Agreement may be Novell Trademarks subject to U.S. export controls and the trade laws of For Novell trademarks, see the Novell Trademark and other countries. You agree to comply with all export Service Mark list control regulations and to obtain any required licenses or (http://www.novell.com/company/legal/trademarks/tmlist. classification to export, re-export or import deliverables. html). You agree not to export or re-export to entities on the Third-Party Materials current U.S. export exclusion lists or to any embargoed All third-party trademarks are the property of their or terrorist countries as specified in the U.S. export laws. respective owners. You agree to not use deliverables for prohibited nuclear, Software Piracy missile, or chemical biological weaponry end uses. See Throughout the world, unauthorized duplication of the Novell International Trade Services Web page software is subject to both (http://www.novell.com/info/exports/) for more criminal and civil penalties. information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any If you know of illegal copying of software, contact your necessary export approvals. local Software Antipiracy Hotline. For the Hotline number for your area, access Novell’s World Wide Web This Novell Training Manual is published solely to page (http://www.novell.com) and look for the piracy instruct students in the use of Novell networking page under “Programs.” software. Although third-party application software Or, contact Novell’s anti-piracy headquarters in the U.S. packages are used in Novell training courses, this is for at 800-PIRATES (747-2837) or 801-861-7101. demonstration purposes only and shall not constitute an endorsement of any of these software applications. Further, Novell, Inc. does not represent itself as having any particular expertise in these application software packages and any use by students of the same shall be done at the student’s own risk. Contents SECTION 1: The Boot Process 4 SECTION 2: The Boot Process Overview 6 SECTION 3: Troubleshooting Big Picture 8 SECTION 4: Boot Process Details 10 SECTION 5: Troubleshooting Techniques 39 SECTION 6: Boot Process Labs 49 Copying all or part of this manual, or distributing such copies, is strictly prohibited. To report suspected copying, please call 1-800-PIRATES Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED. Table of Contents SUSE Advanced Troubleshooting: The Boot Process Troubleshooting Section 01: The Boot Process The purpose of this course is to understand the boot process, learn troubleshooting techniques that will help you solve boot related issues, and apply those techniques in the lab. Copying all or part of this manual, or distributing such copies, is strictly prohibited. To report suspected copying, please call 1-800-PIRATES 4 Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED. SUSE Advanced Troubleshooting: The Boot Process Objectives • Boot Process Overview • Troubleshooting Big Picture • Boot Process Details Copying all or part of this manual, or distributing such copies, is strictly prohibited. To report suspected copying, please call 1-800-PIRATES 5 Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED. SUSE Advanced Troubleshooting: The Boot Process The Boot Process Section 02: The Boot Process Overview The purpose of this course is to understand the boot process, learn troubleshooting techniques that will help you solve boot related issues, and apply those techniques in the lab. Copying all or part of this manual, or distributing such copies, is strictly prohibited. To report suspected copying, please call 1-800-PIRATES 6 Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED. SUSE Advanced Troubleshooting: The Boot Process Graphical boot process overview BIOS /etc/init.d/boot.d/S* boot /boot/grub/stage1MBR /etc/init.d/boot.local /boot/grub/stage2 /etc/init.d/rc[prev_run_lvl].d/K* init rc /etc/init.d/rc[cur_run_lvl].d/S* Initial Ramdisk Kernel mingetty init xdm The boot process is linear by nature. Understanding the general process of how a server boots will help to narrow down boot related problems. This graphical overview of the boot process will be used throughout the presentation to indicate which topic will be covered and when. The topic to be covered will be highlighted.
Load more

Recommended publications
  • Booting up and Shutting Down a Primer for Troubleshooting the Boot
    Booting up and Shutting down A primer for troubleshooting In this section, we touch upon the startup and shutdown process on Linux. It is beyond the scope of this course to cover this topic in depth and we highly recommend that you read more about this topic in the official RedHat documentation or the documents listed at the end of this section. There is an abundance of information on this topic available in books and on the web. The Boot Up Process Please refer to the official RedHat documentation for details about the boot up process. http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/ch-boot-init-shutdown.html Bootloaders Two common bootloaders in Linux are Lilo and grub. Bio-Linux currently uses grub. Grub installs a boot loader to the Master Boot Record. By configuring grub, you can put specific instructions in the Master Boot Record that allow you to load menus or command environments such that you could choose to start up different operating systems, pass information to the kernel, etc. The grub configuration file is at /boot/grub/grub.conf. Unless you are really into system work, you will probably not ever have to touch this file. More information on grub can be found at: http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-grub-whatis.html Once grub has done its job, it hands over control of the machine to the operating system. Run levels Run Level Description 0 Halt 1 Single user mode 2 Multiuser, without networking (without NFS) 3 Full multiuser mode, with networking 4 Unused 5 the same as 3, but with X11 started automatically 6 Reboot The first process run after the kernel has loaded is /sbin/init – this runs with pid 1.
    [Show full text]
  • Operating System Boot from Fully Encrypted Device
    Masaryk University Faculty of Informatics Operating system boot from fully encrypted device Bachelor’s Thesis Daniel Chromik Brno, Fall 2016 Replace this page with a copy of the official signed thesis assignment and the copy of the Statement of an Author. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Daniel Chromik Advisor: ing. Milan Brož i Acknowledgement I would like to thank my advisor, Ing. Milan Brož, for his guidance and his patience of a saint. Another round of thanks I would like to send towards my family and friends for their support. ii Abstract The goal of this work is description of existing solutions for boot- ing Linux and Windows from fully encrypted devices with Secure Boot. Before that, though, early boot process and bootloaders are de- scribed. A simple Linux distribution is then set up to boot from a fully encrypted device. And lastly, existing Windows encryption solutions are described. iii Keywords boot process, Linux, Windows, disk encryption, GRUB 2, LUKS iv Contents 1 Introduction ............................1 1.1 Thesis goals ..........................1 1.2 Thesis structure ........................2 2 Boot Process Description ....................3 2.1 Early Boot Process ......................3 2.2 Firmware interfaces ......................4 2.2.1 BIOS – Basic Input/Output System . .4 2.2.2 UEFI – Unified Extended Firmware Interface .5 2.3 Partitioning tables ......................5 2.3.1 MBR – Master Boot Record .
    [Show full text]
  • It's Complicated but It's Probably Already Booting Your Computer
    FAQ SYSTEMD SYSTEMD It’s complicated but it’s probably already booting your computer. dynamically connect to your network, a runlevel of 1 for a single-user mode, GRAHAM MORRISON while syslogd pools all the system runlevel 3 for the same command messages together to create a log of prompt we described earlier, and Surely the ‘d’ in Systemd is everything important. Another daemon, runlevel 5 to launch a graphical a typo? though it lacks the ‘d’, is init – famous environment. Changing this for your No –it’s a form of Unix notation for being the first process that runs on next boot often involved editing the used to signify a daemon. your system. /etc/inittab file, and you’d soon get used to manually starting and stopping You mean like those little Isn’t init used to switch your own services simply by executing devils inhabiting Dante’s between the command-line the scripts you found. underworld? and the graphical desktop? There is a link in that Unix usage For many of us, yes. This was the You seem to be using the past of the term daemon supposedly main way of going from the tense for all this talk about the comes from Greek mythology, where desktop to a command line and back init daemon… daemons invisibly wove their magic again without trying to figure out which That’s because the and benign influence. The word is today processes to kill or start manually. aforementioned Systemd wants more commonly spelt ‘demon’, which Typing init 3 would typically close any to put init in the past.
    [Show full text]
  • White Paper: Indestructible Firewall in a Box V1.0 Nick Mccubbins
    White Paper: Indestructible Firewall In A Box v1.0 Nick McCubbins 1.1 Credits • Nathan Yawn ([email protected]) 1.2 Acknowledgements • Firewall-HOWTO • Linux Router Project • LEM 1.3 Revision History • Version 1.0 First public release 1.4 Feedback • Send all information and/or criticisms to [email protected] 1.5 Distribution Policy 2 Abstract In this document, the procedure for creating an embedded firewall whose root filesystem is loaded from a flash disk and then executed from a RAMdisk will be illustrated. A machine such as this has uses in many environments, from corporate internet access to sharing of a cable modem or xDSL connection among many computers. It has the advantages of being very light and fast, being impervious to filesystem corruption due to power loss, and being largely impervious to malicious crackers. The type of firewall illustrated herein is a simple packet-filtering, masquerading setup. Facilities for this already exist in the Linux kernel, keeping the system's memory footprint small. As such the device lends itself to embedding very well. For a more detailed description of firewall particulars, see the Linux Firewall-HOWTO. 3 Equipment This project has minimal hardware requirements. An excellent configuration consists of: For a 100-baseT network: • SBC-554 Pentium SBC with PISA bus and on-board PCI NIC (http://www.emacinc.com/pc.htm#pentiumsbc), approx. $373 • PISA backplane, chassis, power supply (http://www.emacinc.com/sbcpc_addons/mbpc641.htm), approx. $305 • Second PCI NIC • 32 MB RAM • 4 MB M-Systems Flash Disk (minimum), approx. $45 For a 10-baseT network: • EMAC's Standard Server-in-a-Box product (http://www.emacinc.com/server_in_a_box.htm), approx.
    [Show full text]
  • Chapter 3. Booting Operating Systems
    Chapter 3. Booting Operating Systems Abstract: Chapter 3 provides a complete coverage on operating systems booting. It explains the booting principle and the booting sequence of various kinds of bootable devices. These include booting from floppy disk, hard disk, CDROM and USB drives. Instead of writing a customized booter to boot up only MTX, it shows how to develop booter programs to boot up real operating systems, such as Linux, from a variety of bootable devices. In particular, it shows how to boot up generic Linux bzImage kernels with initial ramdisk support. It is shown that the hard disk and CDROM booters developed in this book are comparable to GRUB and isolinux in performance. In addition, it demonstrates the booter programs by sample systems. 3.1. Booting Booting, which is short for bootstrap, refers to the process of loading an operating system image into computer memory and starting up the operating system. As such, it is the first step to run an operating system. Despite its importance and widespread interests among computer users, the subject of booting is rarely discussed in operating system books. Information on booting are usually scattered and, in most cases, incomplete. A systematic treatment of the booting process has been lacking. The purpose of this chapter is to try to fill this void. In this chapter, we shall discuss the booting principle and show how to write booter programs to boot up real operating systems. As one might expect, the booting process is highly machine dependent. To be more specific, we shall only consider the booting process of Intel x86 based PCs.
    [Show full text]
  • Network Boot and Exotic Root HOWTO
    Network Boot and Exotic Root HOWTO Brieuc Jeunhomme frtest [email protected] Logilab S.A. Revision History Revision 0.3 2002−04−28 Revised by: bej Many feedback inclusions, added links to several projects Revision 0.2.2 2001−12−08 Revised by: dcm Licensed GFDL Revision 0.2.1 2001−05−21 Revised by: logilab Fixed bibliography and artheader Revision 0.2 2001−05−19 Revised by: bej Many improvements and included Ken Yap's feedback. Revision 0.1.1 2001−04−09 Revised by: logilab First public draft. Revision 0.1 2000−12−09 Revised by: bej Initial draft. This document explains how to quickly setup a linux server to provide what diskless linux clients require to get up and running, using an IP network. It includes data and partly rewritten text from the Diskless−HOWTO, the Diskless−root−NFS−HOWTO, the linux kernel documentation, the etherboot project's documentation, the linux terminal server project's homepage, and the author's personal experience, acquired when working for Logilab. Eventually this document may end up deprecating the Diskless−HOWTO and Diskless−root−NFS−HOWTO. Please note that you'll also find useful information in the From−PowerUp−to−bash−prompt−HOWTO and the Thin−Client−HOWTO, and the Claus−Justus Heine's page about NFS swapping. Network Boot and Exotic Root HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. What is this all about?.......................................................................................................................1 1.2. Thanks...............................................................................................................................................1 1.3. Diskless booting advocacy................................................................................................................1 1.3.1. Buying is cheaper than building.......................................................................................1 1.3.2.
    [Show full text]
  • The Linux Startup Process
    The Linux startup process Jerry Feldman <[email protected]> The Linux Expertise Center Hewlett-Packard Company Document produced via OpenOffice.org Overview ● The Linux boot process – GRUB. This is the default for X86/Linux – LILO – Other boot loaders ● The Linux Operating modes – Single-user mode – Multi-user mode. ● Run Levels – What are run levels – What are the Linux standard run levels – How Linux manages run levels 2 The Linux Boot process ● The PC boot process is a 3-stage boot process that begins with the BIOS executing a short program that is stored in the Master Boot Record (MBR) of the first physical drive. Since this stage 1 boot loader needs to fit in the MBR, it is limited to 512 bytes and is normally written in assembly language. There are a number of boot loaders that can load Linux. ● GRUB and LILO are the most commonly used ones on X86 hardware. ® ® ● EFI is used on the Intel Itanium family. 3 The GRand Unified Bootloader The GRand Unified Bootloader (GRUB) is default boot loader on most distributions today. It has the capability to load a number of different operating systems. 1.The stage 1 boot resides in the MBR and contains the sector number of the stage 2 boot that is usually located in the /boot/grub directory on Linux. 2.The stage 2 boot loader presents a boot menu to the user based on /boot/grub/grub.conf or menu.lst. This contains a boot script. It is the stage2 loader actually loads the Linux kernel or 4 other OS.
    [Show full text]
  • Sbadmin for Linux System Recovery Guide Is a Supplement to the Sbadmin User Guide, Providing Details on Reinstalling a Linux System from a Sbadmin System Backup
    Linux System Recovery Guide Version 8.2 Trademarks and Copyrights © Copyright Storix, Inc. 1999-2021 SBAdmin is a registered trademark of Storix, Inc. SBAdmin is a trademark of Storix, Inc in the USA and other countries Intel is a registered trademark of Intel, Inc. Linux is a registered trademark of Linus Torvalds. Intel, Pentium, IA32, Itanium, Celeron and IA64 are registered trademarks of Intel Corporation. AMD, Opteron, and Athlon are registered trademarks of Advanced Micro Devices. HP Integrity servers are registered trademarks of Hewlett-Packard Development Company. Publicly Available Software This product either includes or is developed using source code that is publicly available: AESCrypt* Rijndael and Cipher Block Feedback Copyright 1999, 2000 Enhanced Software Technologies Inc. mode (CFB-128) encryption/decryption http://aescrypt.sourceforge.net/ algorithms BusyBox Single executable containing tiny Copyright 1989, 1991 Free Software Foundation, Inc. versions of common UNIX utilities http://busybox.net/cgi-bin/cvsweb/busybox/ LILO LInux boot Loader Copyright 1999-2003 John Coffman. Copyright 1992-1998 Werner Almesberger. http://freshmeat.net/projects/lilo/ Tcl Open source scripting language Copyright Regents of the University of California, Sun Microsystems, Inc. http://tcl.sourceforge.net Tk Tk graphics toolkit Copyright Regents of the University of California, Sun Microsystems, Inc. http://tcl.sourceforge.net DropBear A Smallish SSH 2 Server and Client Copyright 2002, 2003 Matt Johnston http://www.matt.ucc.asn.au/dropbear/dropbear.html GRUB Grand Unified Bootloader (GNU GRUB) Copyright 1989, 1991 Free Software Foundation, Inc. http://www.gnu.org/software/grub/grub.html Lighttpd Secure, fast, compliant and flexible Copyright 2004 Jan Kneschkle, incremental web-server http://www.lighttpd.net OpenSSL Toolkit implementing Secure Socket Copyright 1998-2008 The OpenSSL Project Layer Copyright 1995-1998 Eric A.
    [Show full text]
  • Step-By-Step Installation
    000.book Page 47 Friday, April 4, 2008 9:22 AM 3 Step-by-Step Installation In This Chapter Chapter3,Chapter3 2 covered planning the installation of Fedora/RHEL: determining the requirements; performing an upgrade versus a Running a Fedora Live Session . 48 clean installation; planning the layout of the hard disk; obtaining Installing from a Live Session . 51 the files you need for the installation, including how to download Installing/Upgrading from the and burn CD/DVD ISO images; and collecting information about Install DVD . 51 the system. This chapter focuses on installing Fedora/RHEL. Fre- The Anaconda Installer. 53 quently the installation is quite simple, especially if you have done a good job of planning. Sometimes you may run into a problem Using Disk Druid to Partition or have a special circumstance; this chapter gives you tools to use the Disk . 66 in these cases. Read as much of this chapter as you need to; once LVs: Logical Volumes . 75 you have installed Fedora/RHEL, continue with Chapter 4, which Setting Up a Dual-Boot System . 79 covers getting started using the Fedora/RHEL desktop. If you The X Window System. 80 install a textual (command line) system, continue with Chapter 5. system-config-display: Configures the Display . 80 47 000.book Page 48 Friday, April 4, 2008 9:22 AM 48 Chapter 3 Step-by-Step Installation Figure 3-1 Live session, automatic boot screen Running a Fedora Live Session As discussed in Chapter 2, a live session is a Linux session that you run on a computer without installing Linux on the computer.
    [Show full text]
  • Linux-Cookbook.Pdf
    LINUX COOKBOOK ™ Other Linux resources from O’Reilly Related titles Linux Device Drivers Exploring the JDS Linux Linux in a Nutshell Desktop Running Linux Learning Red Hat Enterprise Building Embedded Linux Linux and Fedora Systems Linux Pocket Guide Linux Security Cookbook Understanding the Linux Kernel Linux Books linux.oreilly.com is a complete catalog of O’Reilly’s books on Resource Center Linux and Unix and related technologies, including sample chapters and code examples. ONLamp.com is the premier site for the open source web plat- form: Linux, Apache, MySQL, and either Perl, Python, or PHP. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit conferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today with a free trial. LINUX COOKBOOK ™ Carla Schroder Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo Linux Cookbook™ by Carla Schroder Copyright © 2005 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use.
    [Show full text]
  • Bull System Backup / Restore N O V a SC a LE
    Bull System Backup / Restore NOVASCALE User's Guide for NovaScale Universal & Intensive REFERENCE 86 A2 73EV 04 NOVASCALE Bull System Backup / Restore User's Guide for NovaScale Universal & Intensive Software November 2008 BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE REFERENCE 86 A2 73EV 04 The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works. Copyright Bull SAS 2008 Printed in France Suggestions and criticisms concerning the form, content, and presentation of this book are invited. A form is provided at the end of this book for this purpose. To order additional copies of this book or other Bull Technical Publications, you are invited to use the Ordering Form also provided at the end of this book. Trademarks and Acknowledgements We acknowledge the right of proprietors of trademarks mentioned in this book. Intel ® and Itanium ® are registered trademarks of Intel Corporation. Windows ® and Microsoft ® software are registered trademarks of Microsoft Corporation. UNIX ® is a registered trademark in the United States of America and other countries licensed exclusively through the Open Group. Linux ® is a registered trademark of Linus Torvalds. NovaScale ® is a registered trademark of Bull The information in this document is subject to change without notice. Bull will not be liable for errors contained herein, or for incidental or consequential damages in connection with the use of this material.
    [Show full text]
  • Linux and UNIX
    Operating Systems, Fall 2008 2.10.2008 Example: Linux and UNIX 1 UNIX History First version, a strippedstripped--downdown MULTICS by Ken Thompson for a discarded PDP--7PDP 7 minicomputer in assembly language Moved to PDP--11PDP 11 and rewritten using language, C, designed for that purpose Evolved to two different, partially incompatible versions System V (AT&T, original designers) BSD (Berkeley, based on an early UNIX Version 6) Standardization by IEEE created POSIX 1003.1 Intersection (leikkaus) of the features 2 Lecture 10 1 Operating Systems, Fall 2008 2.10.2008 UNIX Popularity based on Portability C code, some device--dependentdevice dependent parts in assembly code Multiprogramming Supported interactive users (at the era of batch systems) Hierarchical file and directory structure Just one file format: sequence of bytes (Universities had the suitable machines in the beginning) UNIX philosophy: small is beautiful Combining small utility programs (called filters) pipe output of one to be an input to another Minimum number of system calls 3 4 Lecture 10 2 Operating Systems, Fall 2008 2.10.2008 UNIX History, continues MINIX (released in 1987) Designed by A. Tanenbaum for educational purpose Microkernel design Today focus also on reliability and dependability issues LINUX (released in 1991) Designed by Linus Torvalds for personal use Model from MINIX, but monolithic kernel Uses special features of gcc Free software based on GPL (Gnu Public License) 5 Linux Joint InternetInternet--basedbased Free Software Foundation & development GNU Public License Experts all over the world Free distribution of the kernel code (C & assembler )) 1991 -->> Free distribution of some HY/TKTL: "Linux was (most) system software invented here“ GNU C, Gnome, KDE, Linus Torvalds studied and Apache, Samba, … worked at the department.
    [Show full text]