DOCSLIB.ORG

Put a Penguin in Your Pocket

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Put a Penguin in Your Pocket Technical Articles Reducing IT Costs Through Open Source Solutions: A Linux® and PowerPC™ Platform Installation Author: Sven Luther and Bill Buck Topic: Platforms Date: September 2004 Revision: 1.0 The objective of the Avalanche Desktop Reference Management Platform (DRMP) project is to investigate and validate the promise of a complete open source software (OSS) solution from kernel to plug-in. Through this project, Avalanche member companies sought to document the value of lower IT costs through collaboration in the implementation of a complete PowerPC™ technology-based OSS solution. Factors considered in the reduction of total cost of ownership (TCO) included: hardware, support and operational costs, and intangible costs, such as staff familiarity with the software stack and the hardware. Finally, as most senior managers, CFOs, CIOs, or COOs, are not aware of the complexity and risks of OSS and application stack version control, it is Avalanche's objective to enumerate and clarify these issues. Success on the desktop was defined by Avalanche and Genesi (which had been selected to support the DRMP project), as follows: o A well-defined application environment with explicit limits on application functionality, but that still met all the member requirements. o Absolute control of the environment from the system level. o A fully defined hardware platform. o A centralized group that tests, validates and stages every version change (security, reliability, upgrade) of the OS and every application in the stack, including verification of all required inter-application integration. The Avalanche infrastructure The complete physical infrastructure used for the Avalanche DMRP project is running on the same operating system, Debian GNU/Linux, and the same hardware, the PegasosPPC (See Figure 1), from thin client to development machine to server in a variety of configurations as follows: o At the Genesi location, a) a server pool for access by the remote clients, b) a pool of development machines, hosting a package autobuilder, which is used for taking packages (in Debian everything is a package — Mozilla is a package, OpenOffice is a package, and so on.) that exist in source form and rebuilding them for the PegasosPPC with some additional infrastructure, and, c) test systems used for testing the different images, and the improvement of them. o At the Avalanche member site, there is one or more of the following units, a) diskless thin clients, b) workstation class machines with local disks, and, c) local server machines for the diskless thin clients. Figure 1: Layout for the PegasosPPC We term an installation to be the specific version of the software stack that runs on the PegasosPPC hardware. These installations are built on the development machines, and then hosted on the servers for upload to the remote client machines. There are two ways of transferring such an installation: using an installation image, which is a copy of the binary installation seen as a block and transferred in a block, through the network or installation media, such as CDs or DVDs, to new hard disks, or, using an installation snapshot that is a copy of all the information needed to regenerate the actual installation. The installation snapshot can be used to duplicate or upgrade an installation remotely using the installed package list and the configuration database taken from the installation together with the package repository. - 2 - The different steps required to install and manage the systems are as follows: o Configuring and installing the PegasosPPC hardware as required. o Generating the installation that will be duplicated to the preinstalled hard disk, CDs, DVDs or other installation media. o Completing the initial software installation — both locally and remotely. o Updating the existing installation. o Transferring and upgrading the images and snapshots to the remote systems. o Performing the remote configuration management and per-client differentiation. The next section details of how this process is handled by the Debian package management system and the Debian infrastructure. The debconf database and the Debian package system Debian is well known for its package management system. There are basically two tools that are used to manage packages, the first is dpkg, which installs packages, and apt, which manages the downloading of packages from one or more package archives and resolves packages interdependencies. The list of installed packages and their status (on hold, to install, to remove, and so on) is held in the dpkg/apt-get databases. The list of all configuration information for the individual packages is held in the debconf database. Not all Debian package have debconf frendly installation scripts, but most do. In the case that non-debconf friendly packages are needed to fulfill the Avalanche specification, they are modified accordingly by the Genesi developer team. Debconf uses various graphical or textual front ends for its configuration. Either a HTML-based front end used together with Web page generated dynamically from a remote installation database, or a Lightweight Directory Access Protocal (ldap) based remote access database, is used. Debconf also support various priority levels for its queries. At level low, all questions get asked, while at level critical none are asked. This mechanism, together with remote pre-seeding of the debconf database to offer pre-answered questions, allow for seamless upgrades of the images and snapshots on a per-package basis, without remote user interaction. Often, packages have both system-global defaults, and per-user configuration options. In order to make the images work "out of the box," all the configuration changes are done on the system global defaults, and thus provide the same defaults to every user of the system. Additionally, it is possible to block the ability of the user to do user-specific modifications at the direction of the member CIO. - 3 - Initial software installation using the debian-installer Initial installation of remote system can be done either with installation images, or using the installation snapshot and the debian-installer. The installation image method is faster, as it does not need to unpack and configure the individual packages, but it allows less flexibility in both initial installation and upgrades, and uses more bandwidth during upgrades as there is no possibility for a partial installation. The installation method transfers the compressed image, and then uses partimage or plain dd together with a libparted based partitioning tool to install the image to disk. The debian-installer method uses an installation snapshot to pre-seed the debconf database and the package list, to allow for fully automated, no-interaction installations. The configuration script of the individual package runs with pre-fed responses to allow for a more controlled customization than an image duplication process would allow. This is the key to successful upgrades or the installation of additional packages remotely on existing images or snapshots. An installation can be either done from the network or using a CD or DVD installation media. A network install is done using a initrd (initial ramdisk) kernel that is booted over the network (netbooted), which can then either perform the Debian-installer installation, or overwrite the disk with a compressed image. Additionally, CDs or DVDs containing images or, package repositories and configurations, can be used to preserve bandwidth. Additionally, another Debian mechanism can be used to perform the installation of groups of software by using tasks, and the tasksel (task select) package. For example, a pre-selected group of tasks are the desktop task and various server tasks (mail, DNS, Web, printer). The tasks to control exactly what software is included for each member and for each task to be addressed are provided from the server level. - 4 - Figure 2. The Avalanche DRMP network configuration - 5 - Upgrading remote machines There are three types of machines to consider: stand-alone workstation class machines, remote diskless machines, and remote diskless machine servers. The first situation to consider is a remote workstation upgraded from a Genesi server at the Genesi facilities. There are two kinds of upgrades to consider, packages upgrades and kernel upgrades. Package upgrades occur in the same way as snapshot installations. The remote box gets the package list and the debconf answers from the remote database and then updates its apt-get database, installs the packages with a priority of critical, using the pre-seeded debconf database to neatly upgrade the packages without user interaction. An alternative to this, where only the debconf answers get changed, but the package does not get upgraded, the database can be changed by calling dpkg-reconfigure to reconfigure the already installed packages. The difference between the kernel upgrade and the normal package upgrade is the need of a reboot for a change to take effect. Every other upgrade can be done remotely without need for a reboot. When a machine is switched off/on every evening/morning, a small OpenFirmware (OF) program upgrades from OF and then installs the kernel. It not only upgrades the kernel, but also the modules included in it. That said, Debian uses an initrd kernel anyway, so by adding a small modification to this upgrade kernel, which loads the initrd and the provided modules, it upgrades the kernel-image package before pivot_root is used and then moved to the real root. This allows an installation with the kernel upgrade at the start of the daily use at switch on, without requiring a second reboot. For remote diskless machines the difference is that the actual system resides on the Genesi server, and is either served over Network File System (NFS) or uploaded to a ramdisk at machine boot time, either directly or via an image server local to the diskless machine (see Figure 2). The images on such a server are upgraded either per image, or using the snapshot method in a chrooted installation, depending on bandwidth considerations.
Load more

Recommended publications
  • Genesi Pegasos II Debian Linux by Maurie Ommerman CPD Applications Freescale Semiconductor, Inc
    Freescale Semiconductor AN2739 Application Note Rev. 1, 03/2005 Genesi Pegasos II Debian Linux by Maurie Ommerman CPD Applications Freescale Semiconductor, Inc. Austin, TX This application note is the fourth in a series describing the Genesi Contents Pegasos II system, which contains a PowerPC™ microprocessor, 1. Introduction . 1 and the various applications of the system. 2. Terminology . 2 3. Starting Debian Linux . 2 4. Logging in as a Normal User . 6 5. Window Managers . 14 1 Introduction 6. Other User Applications . 19 7. Root User . 20 This application note describes the Debian Linux Operating 8. References . 43 System and many of the commands. Linux has a variety of ways 9. Document Revision History . 43 to accomplish most tasks. This document will show only one way to perform the actions described here. There are other ways. Also, there is usually a GUI way to accomplish most tasks, however, this paper presents command line methods for most tasks. GUI are nice, but they hide what is really happening. When the network is set up with a GUI, how the files are actually affected is not seen, but using the line commands allows feedback on exactly what is happening. This is not a complete guide to Debian Linux, but is a collection of useful things to help both the experienced and novice become quickly adept at using Debian Linux. © Freescale Semiconductor, Inc., 2005. All rights reserved. Terminology 2 Terminology The following terms are used in this document. CUPS Common Unix Printing System Architecture Debian One of the versions of Linux IDE A type of hard drive, which allows up to 2 drives on each channel Linux OS Linux operating system SCSI A type of hard drive, which allows up to 8 drives on each channel Shell A software construct to allow separate users and jobs within the same user to have a separate environment to avoid interfering with each other USB Universal serial bus Yellow Dog One of the versions of Linux 3 Starting Debian Linux Use the boot option 2 for the 2.4 kernel and option 3 for the 2.6 kernel, option 4 for the 2.6.8 kernel.
    [Show full text]
  • Computer Architectures an Overview
    Computer Architectures An Overview PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 25 Feb 2012 22:35:32 UTC Contents Articles Microarchitecture 1 x86 7 PowerPC 23 IBM POWER 33 MIPS architecture 39 SPARC 57 ARM architecture 65 DEC Alpha 80 AlphaStation 92 AlphaServer 95 Very long instruction word 103 Instruction-level parallelism 107 Explicitly parallel instruction computing 108 References Article Sources and Contributors 111 Image Sources, Licenses and Contributors 113 Article Licenses License 114 Microarchitecture 1 Microarchitecture In computer engineering, microarchitecture (sometimes abbreviated to µarch or uarch), also called computer organization, is the way a given instruction set architecture (ISA) is implemented on a processor. A given ISA may be implemented with different microarchitectures.[1] Implementations might vary due to different goals of a given design or due to shifts in technology.[2] Computer architecture is the combination of microarchitecture and instruction set design. Relation to instruction set architecture The ISA is roughly the same as the programming model of a processor as seen by an assembly language programmer or compiler writer. The ISA includes the execution model, processor registers, address and data formats among other things. The Intel Core microarchitecture microarchitecture includes the constituent parts of the processor and how these interconnect and interoperate to implement the ISA. The microarchitecture of a machine is usually represented as (more or less detailed) diagrams that describe the interconnections of the various microarchitectural elements of the machine, which may be everything from single gates and registers, to complete arithmetic logic units (ALU)s and even larger elements.
    [Show full text]
  • Efika MX Smarttop Manual
    E N G L I S H E S P A Ñ O L F R A N Ç A I S D E U T S C H Congratulations on purchasing an Efika MX Cloud Computer. S U P P O R T For access to software updates, product news and our development blog, please visit www.efikamx.info For technical discussions, developer support and resources, please visit www.powerdeveloper.org Package Contents Before you set up your computer, please ensure that your product package includes the following items. • Efika MX Cloud Computer (Smarttop) • User Manual • AC Adapter & Power Cord First Use Instructions Before you use your Efika MX Cloud Computer for the first time, please read the safety chapter included in this user manual. Software Information The default username and password on the provided OS installation is as follows. Username: oem Password: oem For additional documentation about your operating system, please visit www.efikamx.info Product Overview Power Button 3G SIM Slot USB Ports SD / MMC Card Slot DC-IN HDMI RJ45 Audio Out Mic In (Display) (Ethernet) Product Specifications Processor Freescale i.MX515, 800MHz Memory DDR2 512MB, up to 200MHz Graphics & Video Embedded 2D / 3D AMD Core Module Hardware Video Codec Full HW accelerated HD720 playback Display Modes HDMI (version 1.2a) 720P Memory Card MMC, SD, push / push type, by esdhc Slot (Enhanced Multi-Media Card Secure Digital Host Controller) Storage Device SSD 8G Connectivity Ethernet support (default) WLAN 802.11 b/g/n support (optional) or 3G / UMTS support (optional) LED Status Booting (Blue) Indicator System on (Green) DISK IO (flickering) Interface 1x RJ 45 (10/100M) 1 x Audio jack : Audio out 1 x Mic - In 1x DC - In 2x USB 2.0 ports 1x HDMI port 1x SIM slot (optional with WWAN SKU) 20 pin connector for debugging (optional) Audio 1x Built-in speaker (1.5 W) Power Max power consumption: 15 watt Management Power off: Press 4 times AC adapter Output: 12V DC, 3A, 36W Input : 100~240V AC, 50 - 60Hz universal Dimensions / Size: 160*115mm Weight Height: 20mm Weight 250g Temperature Working: 0°C~+40°C Step-by-Step Setup 1.
    [Show full text]
  • Open Desktop Workstation – User Manual Genesi - Open Desktop Workstation – User Manual
    Genesi - Open Desktop Workstation – User Manual Genesi - Open Desktop Workstation – User Manual Introduction Welcome to your new Genesi Open Desktop Workstation (ODW). Included in the package you should have; • Open Desktop Workstation (low-profile chassis) • S-Video to Composite Adapter (TV-out) • Composite cable (TV-out) • 4 “vertical standing” feet • US 115V power cord • This manual + initial setup sheet Genesi - Open Desktop Workstation – User Manual Initial Setup Power Supply Voltage & Cabling The ODW ships with a US 3-pin 115V power cord and the power supply set to 115V operation. If your local electricity supply voltage is different to that used in the United States (220V, for instance, in Europe), the power supply must be switched to operate in that mode. Failure to switch the power supply voltage to the correct setting will cause the power supply to overload and fail, which can be very dangerous and produce sparks or flames. Installing the CPU card The CPU card is secured inside the chassis for safety during shipping, and requires installation before the ODW can be used. Remove the chassis lid by unfastening the screw at the rear, and sliding it forward towards the front of the case. The CPU is stored in the smaller, detachable “floppy bay” which can be removed by carefully sliding it in the same direction as the lid. Take care not to put pressure on or use the CPU card packaging as leverage to remove the bay. Carefully remove the CPU from it's protective packaging and insert it into the CPU slot in the middle of the motherboard, pressing firmly on the top of the card to ensure a snug fit.
    [Show full text]
  • Low-Power High Performance Computing
    Low-Power High Performance Computing Panagiotis Kritikakos August 16, 2011 MSc in High Performance Computing The University of Edinburgh Year of Presentation: 2011 Abstract The emerging development of computer systems to be used for HPC require a change in the architecture for processors. New design approaches and technologies need to be embraced by the HPC community for making a case for new approaches in system design for making it possible to be used for Exascale Supercomputers within the next two decades, as well as to reduce the CO2 emissions of supercomputers and scientific clusters, leading to greener computing. Power is listed as one of the most important issues and constraint for future Exascale systems. In this project we build a hybrid cluster, investigating, measuring and evaluating the performance of low-power CPUs, such as Intel Atom and ARM (Marvell 88F6281) against commodity Intel Xeon CPU that can be found within standard HPC and data-center clusters. Three main factors are considered: computational performance and efficiency, power efficiency and porting effort. Contents 1 Introduction 1 1.1 Report organisation . 2 2 Background 3 2.1 RISC versus CISC . 3 2.2 HPC Architectures . 4 2.2.1 System architectures . 4 2.2.2 Memory architectures . 5 2.3 Power issues in modern HPC systems . 9 2.4 Energy and application efficiency . 10 3 Literature review 12 3.1 Green500 . 12 3.2 Supercomputing in Small Spaces (SSS) . 12 3.3 The AppleTV Cluster . 13 3.4 Sony Playstation 3 Cluster . 13 3.5 Microsoft XBox Cluster . 14 3.6 IBM BlueGene/Q .
    [Show full text]
  • Genesi U.S.A., Inc. 200 Patterson Ave
    JUST ENOUGH COMPUTING by Johan DAMS Genesi U.S.A., Inc. 200 Patterson Ave. San Antonio, TX 78209 USA Phone: +1 210 829 5500 Fax: +1 210 829 5426 Email: jd@puv.fi URL: http://www.genesippc.com Acknowledgments I would like to take this opportunity to thank Mr. Bill Buck and Ms. Raquel Velasco for the opportunity they have given me to work on several exciting projects, and to have introduced me to some truly wonderful people whom I can now call my friends. I hope we can continue this co-operation and friendship for a long time to come. I especially want to express my gratitude to my fiance´ for putting up with my work schedule, which sometimes seems to take more time than there are hours in a day. Her encouragement and understanding truly keep me going, and without her I would never be where I am now. Abstract ”Why not use an embedded processor as a general purpose solution if the targeted requirements are met by the capability available. First, unlocking opportunity has everything to do with price. Last, you don’t need a rocket ship to travel to the grocery store.” ”This is not about a processor or a ”desktop” solution, it is about developing an interface that works anywhere for many things and many people. The objective is to help people do what they do already, better and more conveniently for less – that ought to be just enough.” Quotes by Mr. Bill Buck, CEO of Genesi. If we look at the educational landscape, we see that many schools, universities and organisations world wide struggle with finding a budget to equip themselves with the needed infrastructure to allow students to experience things we in the Western world often take for granted: Internet ac- cess, infrastructure for programming courses, laboratories for embedded systems and robotics, etc.
    [Show full text]
  • The Pegasos Book « Le Livre Du Pegasos » Compilation of Articles on the Pegasos Volume 4 : Linux, Macosx and Other Systems
    The Pegasos book « Le livre du Pegasos » Compilation of articles on the Pegasos Volume 4 : Linux, MacOSX and other systems May 2007 edition - By Geoffrey CHARRA (V2.3) Translated from french by Geoffrey CHARRA (December 2007), With the help of Eric WALTER, Thibault JEANSON, Denis HILLIARD (translation) and Fulvio PERUGGI (corrections) Sponsored by The Pegasos book – Volume 4 : Linux, MacOSX and other systems Contents 1 Linux ......................................................................................................................... 4 1.1 Global information ................................................................................................. 4 1.1.1 Linux distributions running on Pegasos ............................................................... 4 1.1.2 General information on Linux usage for beginners ............................................... 5 1.1.3 Hard disk partitioning under Linux on Pegasos .................................................... 5 1.1.4 Multi-boot with bootcreator .............................................................................. 7 1.1.5 Using a Linux System from Another Linux System by Changing root ...................... 8 1.1.6 NFS : Network File System and Remote Compiling .............................................. 8 1.2 Installation of Linux Debian on Pegasos I and II ...................................................... 10 1.2.1 Installation types ........................................................................................... 10 1.2.2 Installation
    [Show full text]
  • PC Hardware Contents
    PC Hardware Contents 1 Computer hardware 1 1.1 Von Neumann architecture ...................................... 1 1.2 Sales .................................................. 1 1.3 Different systems ........................................... 2 1.3.1 Personal computer ...................................... 2 1.3.2 Mainframe computer ..................................... 3 1.3.3 Departmental computing ................................... 4 1.3.4 Supercomputer ........................................ 4 1.4 See also ................................................ 4 1.5 References ............................................... 4 1.6 External links ............................................. 4 2 Central processing unit 5 2.1 History ................................................. 5 2.1.1 Transistor and integrated circuit CPUs ............................ 6 2.1.2 Microprocessors ....................................... 7 2.2 Operation ............................................... 8 2.2.1 Fetch ............................................. 8 2.2.2 Decode ............................................ 8 2.2.3 Execute ............................................ 9 2.3 Design and implementation ...................................... 9 2.3.1 Control unit .......................................... 9 2.3.2 Arithmetic logic unit ..................................... 9 2.3.3 Integer range ......................................... 10 2.3.4 Clock rate ........................................... 10 2.3.5 Parallelism .........................................
    [Show full text]
  • ARM Linux Kernels and Graphics Drivers on Popular "Open" Hardware: Bleeding Edge Vs
    SCaLE 13x – Open Source Hardware ARM Linux Kernels and Graphics Drivers on Popular "Open" Hardware: Bleeding Edge vs. Vendor Blobs and Kernel Forks - How Much is in Mainline, and How Open is Open? Prepared / Presented by Stephen Arnold, Principal Scientist VCT Labs Gentoo Linux / OpenEmbedded Developer What is ARM/Embedded? · Small Single Board Computer (SBC) or System on Chip (SoC) · Very resource-constrained · Zaurus 5000-D – 32 MB RAM, StrongARM SA-1100 (DEC/ARM) · Kurobox HG – 128 MB RAM, 256 MB flash, no display (G3, no altivec) · Modern devices blurring the lines between “embedded” and desktop/server-class hardware · Multicore CPUs – 2/4/8 cores · Per-core FPUs - VFP3/VFP4, NEON · Multicore GPUs – 192-core Cuda on Tegra K1 · Accelerated HD video processing · USB3, 10/100/1000 Ethernet, SATA, HDMI ARM Devices and Graphics Hardware · ARMv7 HardFloat VFP/NEON · Wandboard / udoo / cubox-i - iMX.6 quad core, Vivante GPU · Beaglebone black / white - AM335X single core, OMAP3 / SGX GPU, PRUs · Sunxi MK802-II 1GB TV stick - Allwinner A10 single core, Mali GPU · Samsung Chromebook - Exynos5 dual core, Mali GPU · Acer Chromebook / Jetson TK1 – Tegra K1 quad-core, NVDIA Cuda GPU · Genesi SmartBook - Freescale iMX.5 single core, AMD z430 GPU ARM Graphics Hardware cont. · ARMv7 HardFloat VFP (no NEON) · Trimslice Diskless - NVIDIA Tegra 2 dual core CPU/GPU · ARMv6 HardFloat VFP (no NEON) · Raspberry Pi - Broadcom SoC single core, VideoCore IV GPU The State of ARM Graphics · (mostly) Current Vendor Blobs · Cubox-i4Pro (iMX.6) · RaspberryPi (VideoCore IV) · Allwinner (Mali) · ChromeOS K1 (Tegra124) · TI (OMAP/SGX) · Open Source Graphics · Tegra/Nouveau – opentegra/grate, nouveau w/firmware · Broadcom/VideoCore IV – weston/wayland, fbturbo · Mali – lima, fbturbo · OMAP – omapfb, omap3 · Vivante – etna-viv, fbturbo · Adreno – freedreno (2D/3D, xorg) Vendor Kernel Forks · Typically a single (older) kernel branch with lots of patches · Minimal backporting (maybe none) · Forwardporting to new branch can take a long time..
    [Show full text]
  • Freebsd 10 - Powerful Virtualization Solutions Freebsd 10 - ARM-Ready Freebsd 10 - Modern Hardware Support
    FreeBSD 10 - Powerful Virtualization Solutions FreeBSD 10 - ARM-Ready FreeBSD 10 - Modern Hardware Support FreeBSD pioneered operating system-level virtualization FreeBSD continues to improve its support for the ARM New console driver, vt(4), provides multiple virtual terminals with the Jail facility in 2000. This early innovation in family of processors, including support for ARMv6 and with an extensive feature set. It includes support for UTF-8, virtualization forged a path for similar technologies such ARMv7, SMP, and thread-local storage (TLS). double-wide characters, Asian character sets, graphics-mode as Solaris Zones (2005) and Linux Containers/Docker Supported processors include: consoles, and integration with Kernel Mode Setting (KMS) video (2014). drivers for switching between the X Window System and virtual • CHROMEBOOK (Samsung Exynos 5250) FreeBSD 10 includes several virtualization technologies, terminals.* providing users with greater flexibility for provisioning a • COLIBRI (Freescale Vybrid) virtualized solution that matches their workflow. These FreeBSD 10 adds Unified Extensible Firmware Interface (UEFI) solutions include: • COSMIC (Freescale Vybrid) boot loader support. The root file system may be UFS or ZFS, and the loader supports multiple ZFS boot environments * • The BSD Hypervisor, bhyve(8). This Type-2 hypervisor supports • Genesi Efika MX SmartBook and SmartTop (Freescale a number of guests, including FreeBSD, OpenBSD, NetBSD and i.MX515)* The Open Fabrics Enterprise Distribution (OFED) and OFED Infiniband core version provides parity with Linux, including many Linux® distributions. Combining bhyve and ZFS volumes • IMX53-QSB (Freescale i.MX53) enables powerful capabilities in provisioning, snapshotting and Mellanox drivers for 56Gb Infiniband. rolling back virtual machines. • QUARTZ (Freescale Vybrid) The nvme(4) driver provides NVM Express support.
    [Show full text]
  • Bootstrapping the Debian and Ubuntu ARM64 Ports
    Bootstrapping the Debian and Ubuntu ARM64 Ports Wookey Linaro 2nd February 2013 Bootstrapping the Debian and Ubuntu ARM64 Ports FOSDEM 2013 1 / 40 Who am I Free Software developer since 1990 Unix sysadmin since 1996 Arm Linux developer since 1999 Debian developer since 2000 Ubuntu development since 2010 Some things I had something to do with: Survex, PsiLinux, ArmLinux book, Emdebian, bootfloppies, Therion, apt-cross, dpkg-cross, Debian cross-toolchains, OpenEmbedded, Netbook Project, LART, YAFFS, Balloonboard, xdeb, multiarch, sbuild Currently an ARM secondee to Linaro Bootstrapping the Debian and Ubuntu ARM64 Ports FOSDEM 2013 2 / 40 Outline 1 Some Armlinux History 2 Why Bootstrapping is a pain 3 How it's done 4 First Bootstrap 5 Debian/Ubuntu Bootstrap 6 Current status Bootstrapping the Debian and Ubuntu ARM64 Ports FOSDEM 2013 3 / 40 Outline 1 Some Armlinux History 2 Why Bootstrapping is a pain 3 How it's done 4 First Bootstrap 5 Debian/Ubuntu Bootstrap 6 Current status Some Armlinux History Bootstrapping the Debian and Ubuntu ARM64 Ports FOSDEM 2013 4 / 40 ARM desktops and servers Rebel Netwinder (2000) Acorn Risc PC (1994) Dell/Calxeda server (2012) Solidrun Cubox (2012) Some Armlinux History Bootstrapping the Debian and Ubuntu ARM64 Ports FOSDEM 2013 5 / 40 ARM laptops Psion Netbook Pro (2003) Toshiba AC100 (2010) Genesi Smartbook (2010) Samsung Chromebook (now) Some Armlinux History Bootstrapping the Debian and Ubuntu ARM64 Ports FOSDEM 2013 6 / 40 Debian ports Name Bits ABI ISA Released arm 32 OABI v3 2000:Potato (discontinued
    [Show full text]
  • Download Issue 14
    IssueBiggest Ever! £4.00 Issue 14, Spring 2003 8.00Euro Quake 2 Read our comprehensive review of Hyperions’s latest port. Hollywood Take a seat and enjoy our full review of this exciting new multimedia blockbuster! Contents Features The Show Must Go On! Editorial Welcome to another issue of Candy for SEAL’s Mick Sutton gives us an insight into the production of WoASE. Total Amiga, as you will no-doubt Issue 14 usergroups can afford. To give balance between space for the have noticed this issue is rather ack in the good old days we you an idea a venue capable of punters and giving the exhibitors late, which is a pity as we had Candy Factory is a graphics A built-in character generator had World of Amiga shows holding between 300 and 500 the stand space they require improved our punctuality over OS4 B the last few issues. application designed for allows you to add effects to Spring 2002 put on every year, usually at a people can cost anywhere from (some companies get a real bee high profile site (Wembley) and £500 to £1000 (outside London) in their bonnet about where they Unfortunately the main reason making logos and other text in any font without leaving texture again based on the all well attended. Everybody for a day. are situated). The floorplan goes behind the delay was that the graphics with high quality 3D the program. You can also load Contents wanted to be there and be seen, through many revisions before SCSI controller and PPC on my textured effects quickly and shapes (for example a logo) light source.
    [Show full text]