DOCSLIB.ORG

Ubuntu Installation Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ubuntu Installation Guide Ubuntu Installation Guide Ubuntu Installation Guide Copyright © 2004 – 2020 the Debian Installer team Copyright © 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2015, 2018 Canonical Ltd. This document contains installation instructions for the Ubuntu 20.04 system (codename “‘Focal Fossa’”), for the PowerPC (“powerpc”) architecture. It also contains pointers to more information and information on how to make the most of your new Ubuntu system. This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in Appendix F. Table of Contents Installing Ubuntu 20.04 “Focal Fossa” For powerpc.......................................................................x 1. Welcome to Ubuntu ........................................................................................................................1 1.1. What is Ubuntu?...................................................................................................................1 1.1.1. Sponsorship by Canonical .......................................................................................1 1.2. What is Debian? ...................................................................................................................1 1.2.1. Ubuntu and Debian..................................................................................................2 1.2.1.1. Package selection........................................................................................2 1.2.1.2. Releases.......................................................................................................3 1.2.1.3. Development community............................................................................3 1.2.1.4. Freedom and Philosophy.............................................................................3 1.2.1.5. Ubuntu and other Debian derivatives..........................................................4 1.3. What is GNU/Linux? ...........................................................................................................4 1.4. Getting Ubuntu.....................................................................................................................5 1.5. Getting the Newest Version of This Document....................................................................5 1.6. Organization of This Document...........................................................................................5 1.7. Your Documentation Help is Welcome................................................................................6 1.8. About Copyrights and Software Licenses............................................................................6 2. System Requirements .....................................................................................................................8 2.1. Supported Hardware.............................................................................................................8 2.1.1. Supported Architectures ..........................................................................................8 2.1.2. CPU, Main Boards, and Video Support...................................................................8 2.1.2.1. Kernel Flavours...........................................................................................8 2.1.2.2. Power Macintosh (pmac) subarchitecture...................................................9 2.1.2.3. PReP subarchitecture ................................................................................11 2.1.2.4. CHRP subarchitecture...............................................................................11 2.1.2.5. APUS subarchitecture (unsupported) .......................................................11 2.1.2.6. Nubus PowerMac subarchitecture (unsupported) .....................................11 2.1.2.7. Non-PowerPC Macs..................................................................................12 2.1.3. Multiple Processors ...............................................................................................12 2.1.4. Graphics Hardware Support ..................................................................................12 2.1.5. Network Connectivity Hardware...........................................................................12 2.1.5.1. Wireless Network Cards ...........................................................................13 2.1.6. Braille Displays .....................................................................................................13 2.1.7. Peripherals and Other Hardware ...........................................................................13 2.2. Devices Requiring Firmware .............................................................................................13 2.3. Purchasing Hardware Specifically for GNU/Linux ...........................................................14 2.3.1. Avoid Proprietary or Closed Hardware .................................................................14 2.4. Installation Media ..............................................................................................................15 2.4.1. CD-ROM/DVD-ROM/BD-ROM ..........................................................................15 2.4.2. Network .................................................................................................................15 2.4.3. Hard Disk...............................................................................................................15 2.4.4. Un*x or GNU system ............................................................................................16 2.4.5. Supported Storage Systems ...................................................................................16 2.5. Memory and Disk Space Requirements.............................................................................16 iii 3. Before Installing Ubuntu..............................................................................................................17 3.1. Overview of the Installation Process..................................................................................17 3.2. Back Up Your Existing Data!.............................................................................................18 3.3. Point release and HWE kernel ...........................................................................................18 3.4. Information You Will Need................................................................................................18 3.4.1. Documentation ......................................................................................................18 3.4.1.1. Installation Manual ...................................................................................18 3.4.1.2. Hardware documentation..........................................................................19 3.4.2. Finding Sources of Hardware Information............................................................19 3.4.3. Hardware Compatibility ........................................................................................19 3.4.3.1. Testing hardware compatibility with a Live-System ................................21 3.4.4. Network Settings ...................................................................................................21 3.5. Meeting Minimum Hardware Requirements .....................................................................22 3.6. Pre-Partitioning for Multi-Boot Systems ...........................................................................22 3.6.1. Mac OS X Partitioning ..........................................................................................23 3.7. Pre-Installation Hardware and Operating System Setup....................................................24 3.7.1. Invoking OpenFirmware........................................................................................24 3.7.2. How to update bare metal ppc64el firmware.........................................................24 3.7.3. Updating KVM guest firmware (SLOF)................................................................26 3.7.4. Hardware Issues to Watch Out For........................................................................26 4. Obtaining System Installation Media .........................................................................................27 4.1. Official Ubuntu CD-ROMs ................................................................................................27 4.2. Downloading Files from Ubuntu Mirrors ..........................................................................27 4.2.1. Where to Find Installation Images ........................................................................27 4.3. Preparing Files for Hard Disk Booting ..............................................................................27 4.3.1. Hard Disk Installer Booting for NewWorld Macs.................................................28 4.4. Preparing Files for TFTP Net Booting...............................................................................28 4.4.1. Setting up a DHCP server......................................................................................29 4.4.2. Setting up a BOOTP server ...................................................................................29 4.4.3. Enabling the TFTP Server .....................................................................................30 4.4.4. Move TFTP Images Into Place..............................................................................30
Load more

Recommended publications
  • DKB Kwikstart II Installation and User's Guide
    KwikStart II™ Kickstart Rom Expansion Board for the Amiga® 1000 Installation and User's Guide by DKB Software COPYRIGHT This manual is the Copyright © of DKB Software, Inc. All Rights Reserved. This document may not, in whole or in part, be copied, photocopied, reproduced, translated,or reduced to any electron­ ic medium or machine readable form, without prior consent, in writing, of DKB Software, Inc. MegAChip 2000, MultiStart II, BattDisk, SecureKey, KwikStart, KwikStart II, Insider, and Insider II are trademarks of DKB Software. Amiga is a registered trademark of Commodore-Amiga, Inc. AmigaDos, Kickstart, and Workbench are trademarks of Commodore-Amiga, Inc. Table of Contents 1. Introduction 1 2. Configuring the KwikStart II TM 2 Selecting the power up mode 2 3. Installation 3 Disassembling your Amiga • 3 Removing the PAL 4 Removing the disk drive 5 Removing the 68000 6 Installing the K wikStart II TM 6 Testing your system 8 Reassembling your Amiga• 9 4. Operation of the KwikStart II TM 10 5. Troubleshooting 11 PN: 00300801-01 1. Introduction. Congratulations on the purchase of your new KwikStart II™ ROM board for the Amiga® 1000 by DKB Software.The KwikStartII™ ROM board will pr ovide you with many benefits. KwikStart II™ is an add on board that puts thelatest Amiga® KickStart™ permanentlyin ROM (ReadOnly Memory) like in the A500,A2000 and A3000. This latest version of the KwikStart II™ provides you with the ability to install Kickstart™V2.0 as well as Vl.3 or Vl.2 in your Amiga® 1000. This is the easiest way for A 1000 owners to upgrade to 2.0.
    [Show full text]
  • Ubuntu Installation Guide
    Ubuntu Installation Guide Ubuntu Installation Guide Copyright © 2004 – 2020 the Debian Installer team Copyright © 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2015, 2018 Canonical Ltd. This document contains installation instructions for the Ubuntu 20.04 system (codename “‘Focal Fossa’”), for the S/390 (“s390x”) architecture. It also contains pointers to more information and information on how to make the most of your new Ubuntu system. This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in Appendix F. Table of Contents Installing Ubuntu 20.04 “Focal Fossa” For s390x...........................................................................ix 1. Welcome to Ubuntu ........................................................................................................................1 1.1. What is Ubuntu?...................................................................................................................1 1.1.1. Sponsorship by Canonical .......................................................................................1 1.2. What is Debian? ...................................................................................................................1 1.2.1. Ubuntu and Debian..................................................................................................2 1.2.1.1. Package selection........................................................................................2 1.2.1.2. Releases.......................................................................................................3
    [Show full text]
  • Report on the 2020 FOSS Contributor Survey
    Report on the 2020 FOSS Contributor Survey The Linux Foundation & The Laboratory for Innovation Science at Harvard Frank Nagle Harvard Business School David A. Wheeler The Linux Foundation Hila Lifshitz-Assaf New York University Haylee Ham Jennifer L. Hoffman Laboratory for Innovation Science at Harvard Acknowledgments This report and the research behind it would not have been possible without the leadership of the Core Infrastructure Initiative’s Advisory Committee, composed of Josh Corman, Steve Lipner, Audris Mockus, Henning Piezunka, and Sam Ransbotham. Frank Nagle would also like to thank his fellow co-directors of the Core Infrastructure Initiative, Jim Zemlin at the Linux Foundation and Karim Lakhani at the Laboratory for Innovation Science at Harvard, for their counsel and direction throughout this project. Gratitude and thanks to Michael Dolan and Kate Stewart at the Linux Foundation for their ongoing commitment to this undertaking. Thank you to James Dana for laying the initial groundwork for this survey. Finally — and perhaps, most importantly — thank you to all the individuals who contribute to FOSS projects. Without their tireless efforts, our core digital infrastructure and the feats enabled by it would not be sustainable. REVISED: This report has been updated since its original release on 8 December 2020. This second version, released on 10 December 2020, corrects errors found in the original text and graphics. Contents Executive Summary 4 Introduction 7 Methodology 9 Overview of Findings 10 Demographics 10 Figure 1: Gender
    [Show full text]
  • CONFIRM: Evaluating Compatibility and Relevance of Control-flow Integrity Protections for Modern Software.” in Proc
    Xiaoyang Xu, Masoud Ghaffarinia, Wenhao Wang, Kevin W. Hamlen, and Zhiqiang Lin. “CONFIRM: Evaluating Compatibility and Relevance of Control-flow Integrity Protections for Modern Software.” In Proc. 28th USENIX Security Symposium, August 2019. CONFIRM: Evaluating Compatibility and Relevance of Control-flow Integrity Protections for Modern Software Xiaoyang Xu Masoud Ghaffarinia∗ Wenhao Wang∗ University of Texas at Dallas University of Texas at Dallas University of Texas at Dallas Kevin W. Hamlen Zhiqiang Lin University of Texas at Dallas Ohio State University Abstract one of the strongest known defenses against modern control- flow hijacking attacks, including return-oriented program- CONFIRM (CONtrol-Flow Integrity Relevance Metrics) is a new evaluation methodology and microbenchmarking suite ming (ROP) [60] and other code-reuse attacks. These attacks for assessing compatibility, applicability, and relevance of trigger dataflow vulnerabilities (e.g., buffer overflows) to ma- control-flow integrity (CFI) protections for preserving the in- nipulate control data (e.g., return addresses) to hijack victim tended semantics of software while protecting it from abuse. software. By restricting program execution to a set of legiti- Although CFI has become a mainstay of protecting certain mate control-flow targets at runtime, CFI can mitigate many classes of software from code-reuse attacks, and continues of these threats. to be improved by ongoing research, its ability to preserve Inspired by the initial CFI work [1], there has been prolific intended program functionalities (semantic transparency) of new research on CFI in recent years, mainly aimed at improv- diverse, mainstream software products has been under-studied ing performance, enforcing richer policies, obtaining higher in the literature.
    [Show full text]
  • Troubleshooting Passwords
    Troubleshooting Passwords The following procedures may be used to troubleshoot password problems: • Performing Password Recovery with an Existing Administrator, page 1 • Performing Password Recovery with No Existing Administrator, page 1 • Performing Password Recovery for the Linux Grapevine User Account, page 2 Performing Password Recovery with an Existing Administrator To perform password recovery for a user (administrator, installer or observer) where there exists at least one controller administrator (ROLE_ADMIN) user account, take the following steps: 1 Contact the existing administrator to set up a temporary password for the user that requires password recovery. Note The administrator can set up a temporary password by deleting the user's account and then recreating it with the lost password. The user can then log back into the controller to regain access and change the password once again to whatever he or she desires. 2 The user then needs to log into the controller with the temporary password and change the password. Note Passwords are changed in the controller GUI using the Change Password window. For information about changing passwords, see Chapter 4, Managing Users and Roles in the Cisco Application Policy Infrastructure Controller Enterprise Module Configuration Guide. Performing Password Recovery with No Existing Administrator The following procedure describes how to perform password recovery where there exists only one controller administrator (ROLE_ADMIN) user account and this account cannot be successfully logged into. Cisco Application Policy Infrastructure Controller Enterprise Module Troubleshooting Guide, Release 1.3.x 1 Troubleshooting Passwords Performing Password Recovery for the Linux Grapevine User Account Note We recommend that you create at least two administrator accounts for your deployment.
    [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]
  • Version 7.8-Systemd
    Linux From Scratch Version 7.8-systemd Created by Gerard Beekmans Edited by Douglas R. Reno Linux From Scratch: Version 7.8-systemd by Created by Gerard Beekmans and Edited by Douglas R. Reno Copyright © 1999-2015 Gerard Beekmans Copyright © 1999-2015, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 7.8-systemd Table of Contents Preface .......................................................................................................................................................................... vii i. Foreword ............................................................................................................................................................. vii ii. Audience ............................................................................................................................................................ vii iii. LFS Target Architectures ................................................................................................................................ viii iv. LFS and Standards ............................................................................................................................................ ix v. Rationale for Packages in the Book .................................................................................................................... x vi. Prerequisites
    [Show full text]
  • Open Source Licensing Information for Cisco IP Phone 8800 Series
    Open Source Used In Cisco IP Phone 8800 Series 12.1(1) Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-163803748 Open Source Used In Cisco IP Phone 8800 Series 12.1(1) 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-163803748 Contents 1.1 bluez 4.101 :MxC-1.1C R4.0 1.1.1 Available under license 1.2 BOOST C++ Library 1.63.0 1.2.1 Available under license 1.3 busybox 1.21.0 1.3.1 Available under license 1.4 Busybox 1.23.1 1.4.1 Available under license 1.5 cjose 0.4.1 1.5.1 Available under license 1.6 cppformat 2.0.0 1.6.1 Available under license 1.7 curl 7.26.0 1.7.1 Available under license 1.8 dbus 1.4.1 :MxC-1.1C R4.0 1.8.1 Available under license 1.9 DirectFB library and utilities 1.4.5 1.9.1 Available under license 1.10 dnsmasq 2.46 1.10.1 Available under license 1.11 flite 2.0.0 1.11.1 Available under license 1.12 glibc 2.13 1.12.1 Available under license 1.13 hostapd 2.0 :MxC-1.1C R4.0 1.13.1 Available under license Open Source Used
    [Show full text]
  • Lightweight Distros on Test
    GROUP TEST LIGHTWEIGHT DISTROS LIGHTWEIGHT DISTROS GROUP TEST Mayank Sharma is on the lookout for distros tailor made to infuse life into his ageing computers. On Test Lightweight distros here has always been a some text editing, and watch some Linux Lite demand for lightweight videos. These users don’t need URL www.linuxliteos.com Talternatives both for the latest multi-core machines VERSION 2.0 individual apps and for complete loaded with several gigabytes of DESKTOP Xfce distributions. But the recent advent RAM or even a dedicated graphics Does the second version of the distro of feature-rich resource-hungry card. However, chances are their does enough to justify its title? software has reinvigorated efforts hardware isn’t supported by the to put those old, otherwise obsolete latest kernel, which keeps dropping WattOS machines to good use. support for older hardware that is URL www.planetwatt.com For a long time the primary no longer in vogue, such as dial-up VERSION R8 migrators to Linux were people modems. Back in 2012, support DESKTOP LXDE, Mate, Openbox who had fallen prey to the easily for the i386 chip was dropped from Has switching the base distro from exploitable nature of proprietary the kernel and some distros, like Ubuntu to Debian made any difference? operating systems. Of late though CentOS, have gone one step ahead we’re getting a whole new set of and dropped support for the 32-bit SparkyLinux users who come along with their architecture entirely. healthy and functional computers URL www.sparkylinux.org that just can’t power the newer VERSION 3.5 New life DESKTOP LXDE, Mate, Xfce and others release of Windows.
    [Show full text]
  • De-Anonymizing Live Cds Through Physical Memory Analysis
    De-Anonymizing Live CDs through Physical Memory Analysis Andrew Case [email protected] Digital Forensics Solutions Abstract Traditional digital forensics encompasses the examination of data from an offline or “dead” source such as a disk image. Since the filesystem is intact on these images, a number of forensics techniques are available for analysis such as file and metadata examination, timelining, deleted file recovery, indexing, and searching. Live CDs present a serious problem for this investigative model, however, since the OS and applications execute in a RAM-only environment and do not save data on non-volatile storage devices such as the local disk. In order to solve this problem, we present a number of techniques that support complete recovery of a live CD’s in-memory filesystem and partial recovery of its deleted contents. We also present memory analysis of the popular Tor application, since it is used by a number of live CDs in an attempt to keep network communications encrypted and anonymous. 1 Introduction Traditional digital forensics encompasses the examination of data from an offline or “dead” source such as a disk image. Under normal circumstances, evidence is obtained by first creating an exact, bit-for-bit copy of the target disk, followed by hashing of both the target disk and the new copy. If these hashes match then it is known that an exact copy has been made, and the hash is recorded to later prove that evidence was not modified during the investigation. Besides satisfying legal requirements, obtaining a bit-for-bit copy of data provides investigators with a wealth of information to examine and makes available a number of forensics techniques.
    [Show full text]
  • Amigaos 3.2 FAQ 47.1 (09.04.2021) English
    $VER: AmigaOS 3.2 FAQ 47.1 (09.04.2021) English Please note: This file contains a list of frequently asked questions along with answers, sorted by topics. Before trying to contact support, please read through this FAQ to determine whether or not it answers your question(s). Whilst this FAQ is focused on AmigaOS 3.2, it contains information regarding previous AmigaOS versions. Index of topics covered in this FAQ: 1. Installation 1.1 * What are the minimum hardware requirements for AmigaOS 3.2? 1.2 * Why won't AmigaOS 3.2 boot with 512 KB of RAM? 1.3 * Ok, I get it; 512 KB is not enough anymore, but can I get my way with less than 2 MB of RAM? 1.4 * How can I verify whether I correctly installed AmigaOS 3.2? 1.5 * Do you have any tips that can help me with 3.2 using my current hardware and software combination? 1.6 * The Help subsystem fails, it seems it is not available anymore. What happened? 1.7 * What are GlowIcons? Should I choose to install them? 1.8 * How can I verify the integrity of my AmigaOS 3.2 CD-ROM? 1.9 * My Greek/Russian/Polish/Turkish fonts are not being properly displayed. How can I fix this? 1.10 * When I boot from my AmigaOS 3.2 CD-ROM, I am being welcomed to the "AmigaOS Preinstallation Environment". What does this mean? 1.11 * What is the optimal ADF images/floppy disk ordering for a full AmigaOS 3.2 installation? 1.12 * LoadModule fails for some unknown reason when trying to update my ROM modules.
    [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]