58 Asus with Hardy KNOW$HOW 58

Total Page:16

File Type:pdf, Size:1020Kb

58 Asus with Hardy KNOW$HOW 58 BEFN$?FN Ask Klaus! 8JB BC8LJ suspend mode? I’ll give you a short over- is large enough to hold the content of view on what needs to be done to use your computer’s memory (see Listing 1). suspend to RAM and suspend to disk The example in Listing 1 shows that here. this computer has about 1.2GB RAM, Klaus Knopper is the creator of To use suspend to disk, you need to and 1.9GB of swap, so suspend to disk Knoppix and co-founder of the enable this feature in the kernel. (I as- is possible. sume that this is already done in In your setup, if the available swap LinuxTag expo. He currently Ubuntu.) See Figure 1. space is lower than RAM plus swap in For suspend to disk, the kernel also use, then suspend to disk will just fail works as a teacher, program- needs to know how and where to store and you would have to repartition the mer, and consultant. If you have the content of your notebook’s RAM hard drive for a larger swap partition to while it is in power-off mode. make it work. a configuration problem, or if The “where” part is configured at the As soon as swap and the boot com- kernel boot command line. Mine looks mand line are set up, you can start the you just want to learn more like this: suspend procedure by telling the kernel about how Linux works, send to freeze then store the running system $ cat /proc/cmdline to disk. your questions to: ... resume=/dev/hda3 ... Before this, sending a couple of sync commands is a good idea, just in case klaus@linux-magazine. com With this preset boot option, the kernel that unwritten data gets lost because of a knows that the partition, which possibly failed wake up later. (Sending only one contains a suspended system, is the third might not be sufficient because of its partition on the first IDE hard disk in my asynchronous nature.) You must be root setup. On boot, the kernel will automati- for this procedure: 8jljn`k_?Xi[p cally try to restore a saved session from My Asus M2V-MX-based desk- this partition when this option is pres- # sync; sync; sync top suspends well in Windows ent. To modify the boot kernel command # echo shutdown > /sys/power/disk Vista, but it does not suspend line, you have to change the APPEND # echo disk > /sys/power/state in Ubuntu Hardy. I have changed S3 and line in your bootloader’s setup (/etc/lilo. ACPI versions in the BIOS to see if that conf for LILO, with LILO being called Now the kernel should switch to text works. Although it causes some differ- after a change, or /boot/grub/grub.cfg or console mode and display what it’s ences in behavior, the system still does menu.lst for the grub bootloader). As a doing. In case of failure, you will see an not work in Ubuntu. What should I do? last resort, you can type the option in error message in the output of dmesg. the bootloader’s interactive Some information is missing in mode. Listing 1: Free swap space your description that could help On the swap partition, which 01 $ grep MemTotal /proc/meminfo will also become the “hiber- solve the problem. 02 MemTotal: 1295172 kB Do you mean “suspend to RAM” nate” partition, you need to re- 03 (STR) or “suspend to disk” (S2D)? serve space about the size of 04 $ cat /proc/swaps Is the problem that suspend just does your RAM. 05 Filename Type Size Used Priority not do anything, or is the problem that So, please check to see 06 /dev/hda3 partition 1959920 664036 -1 the notebook does not wake up from whether your free swap space 58 ISSUE 96 NOVEMBER 2008 058-060_ask-klaus.indd 58 11.09.2008 15:09:43 Uhr Ask Klaus! BEFN$?FN Depending on how well ACPI works on your notebook, using # echo platform > 5 /sys/power/disk # echo disk > 5 /sys/power/state instead of the previous suggestion might work even better because the ACPI BIOS might know how to switch peripheral devices to suspend mode in order to wake up correctly later. After freezing processes, the kernel will write the entire system state to the swap partition and power off the system. On next boot, the kernel will search for a hibernate signature on the swap =`^li\(1JZi\\ej_fk]ifdk_\b\ie\cZfe]`^i\^Xi[`e^jljg\e[kf[`jb% partition and load the suspended system from there if at all possible. read from it. For example, if hard disk LJ9N`i\c\jj9ifX[YXe[ Some things that could go wrong controller drivers are not statically I have a three USB wireless when resuming: compiled into the kernel, the kernel broadband Huawei HSDPA 1. Some hardware does not reinitialize might not have a chance to initialize CE0682 modem. I cannot get it properly when being awoken from the resume procedure later if the ini- to work on the Fedora 8. Can you ex- suspend, so your system freezes. This tial ramdisk containing the drivers plain why it is difficult to add any USB result is known to happen with non- does not explicitly do this. modem to the Fedora, Red Hat, and suspendable sound drivers. Again, the boot/ kernel log shown by Ubuntu platforms? To be on the safe side, make sure that dmesg might give a hint about what in your own suspend/ resume script, went wrong. I’m afraid that only the original all drivers known to be unstable after To suspend to RAM (if supported), use hardware manufacturer knows wake up are unloaded. mem instead of disk in the suspend com- why they only provide Windows Example (before suspend): mands above. drivers for their hardware. If the Apparently, you don’t need a suspend “modem” has a DHCP mode in which it fuser -k /dev/dsp 5 partition for this; standby could also be distributes addresses to an Ethernet-net- # Stop sound output an option, which will only reduce power worked computer automatically, you rmmod snd_intel8x0 5 consumption of some devices but not re- should be able to use it without any spe- # Unload onboard sound driver ally suspend the system: cial drivers. For closed, proprietary USB protocols that only the hardware manu- 2. Because of the way the kernel has # echo mem > 5 facturer knows about, it is a very tire- been configured in a specific distribu- /sys/power/state some – and in no way cost-effective – tion, the swap partition might not be task to develop a driver via reverse engi- accessible early enough to be able to or neering. Therefore, almost nobody will do this for free. # echo standby > 5 A company’s strategic decision to sell /sys/power/state hardware that works only for a specific operating system does not have a rea- Instead of using the newer /sys/power/... sonable technical solution. The best ad- interface, you can also try the ACPI sleep vice I could give is to return the appar- states control file: ently defective device as a warranty case (it does not work, does it?) and claim # echo 4 > 5 your money back. /proc/acpi/sleep 5 # Suspend-to-disk GlggpfeG\e;i`m\ I am a university student and an or amateur Linux user. Can you tell me how to install mbr.bin on # echo 3 > 5 my pen drive? I want to boot a version of /proc/acpi/sleep 5 Pendrivelinux from this device. Is it pos- # Suspend-to-ram sible to install from Puppy 3.10? It never NOVEMBER 2008 ISSUE 96 59 058-060_ask-klaus.indd 59 11.09.2008 15:09:45 Uhr BEFN$?FN Ask Klaus! works when I try to find it with the Listing 2: Pen drive example instruction: 01 # fdisk -l /dev/sdc 02 Disk /dev/sdc: 8021 MB, 8021606400 bytes locate mbr.bin 03 16 heads, 32 sectors/track, 30600 cylinders Also, I would like to know whether it is 04 Units = cylinders of 512 * 512 = 262144 bytes possible to install SysLinux with the 05 Disk identifier: 0x10d72c95 following command: 06 07 Device Boot Start End Blocks Id System 08 /dev/sdc1 * 16 30600 7829568 c W95 FAT32 (LBA) syslinux -s /dev/sda1 I have already visited pendrivelinux. com been flushed to disk or enforce it by call- default linux and followed the instructions, but I al- ing sync or the eject commands below. timeout 10 ways have problems booting from my After this, check to see whether the prompt 1 pen drive. partitioning of the pen drive is still OK. label linux Another problem is that the machines To let the kernel know that partitioning kernel linux I have access to only have 256MB of data has been changed, you might have append initrd=minirt.gz 5 RAM, so I can’t boot into Ubuntu 7.10 to reconnect the drive. The easiest way root=/dev/ram0 or 8.04. If I understand things correctly, to do so is with with these versions of Ubuntu, it is pos- Linux kernel (linux) and initial ramdisk sible to install LILO and SysLinux. # eject /dev/sdc (minirt.gz) must be copied to the same # eject -t /dev/sdc partition containing the bootloader. The Making a FAT16/ FAT32-format- Linux filesystem itself can be located on ted USB pen bootable only takes or you can physically remove and re- a separate partition, formatted with a a few commands.
Recommended publications
  • 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]
  • Linux Boot Loaders Compared
    Linux Boot Loaders Compared L.C. Benschop May 29, 2003 Copyright c 2002, 2003, L.C. Benschop, Eindhoven, The Netherlands. Per- mission is granted to make verbatim copies of this document. This is version 1.1 which has some minor corrections. Contents 1 introduction 2 2 How Boot Loaders Work 3 2.1 What BIOS does for us . 3 2.2 Parts of a boot loader . 6 2.2.1 boot sector program . 6 2.2.2 second stage of boot loader . 7 2.2.3 Boot loader installer . 8 2.3 Loading the operating system . 8 2.3.1 Loading the Linux kernel . 8 2.3.2 Chain loading . 10 2.4 Configuring the boot loader . 10 3 Example Installations 11 3.1 Example root file system and kernel . 11 3.2 Linux Boot Sector . 11 3.3 LILO . 14 3.4 GNU GRUB . 15 3.5 SYSLINUX . 18 3.6 LOADLIN . 19 3.7 Where Can Boot Loaders Live . 21 1 4 RAM Disks 22 4.1 Living without a RAM disk . 22 4.2 RAM disk devices . 23 4.3 Loading a RAM disk at boot time . 24 4.4 The initial RAM disk . 24 5 Making Diskette Images without Diskettes 25 6 Hard Disk Installation 26 7 CD-ROM Installation 29 8 Conclusions 31 1 introduction If you use Linux on a production system, you will only see it a few times a year. If you are a hobbyist who compiles many kernels or who uses many operating systems, you may see it several times per day.
    [Show full text]
  • Dell EMC Poweredge Systems Running Red Hat Enterprise Linux 7 Release Notes Notes, Cautions, and Warnings
    Dell EMC PowerEdge Systems Running Red Hat Enterprise Linux 7 Release Notes Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2014 - 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. 2019 - 03 Rev. A15 Contents 1 Overview........................................................................................................................................................6 System configuration requirements................................................................................................................................. 6 Memory......................................................................................................................................................................... 6 Installation and upgrade instructions............................................................................................................................... 6 2 Known issues—To be fixed in future releases.................................................................................................7 Unable to create or modify namespace for NVDIMM..................................................................................................
    [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]
  • Creating Custom Debian Live for USB FD with Encrypted Persistence
    Creating Custom Debian Live for USB FD with Encrypted Persistence INTRO Debian is a free operating system (OS) for your computer. An operating system is the set of basic programs and utilities that make your computer run. Debian provides more than a pure OS: it comes with over 43000 packages, precompiled software bundled up in a nice format for easy installation on your machine. PRE-REQ * Debian distro installed * Free Disk Space (Depends on you) Recommended Free Space >20GB * Internet Connection Fast * USB Flash Drive atleast 4GB Installing Required Softwares on your distro: Open Root Terminal or use sudo: $ sudo apt-get install debootstrap syslinux squashfs-tools genisoimage memtest86+ rsync apt-cacher-ng live-build live-config live-boot live-boot-doc live-config-doc live-manual live-tools live-manual-pdf qemu-kvm qemu-utils virtualbox virtualbox-qt virtualbox-dkms p7zip-full gparted mbr dosfstools parted Configuring APT Proxy Server (to save bandwidth) Start apt-cacher-ng service if not running # service apt-cacher-ng start Edit /etc/apt/sources.list with your favorite text editor. Terminal # nano /etc/apt/sources.list Output: (depends on your APT Mirror configuration) deb http://security.debian.org/ jessie/updates main contrib non-free deb http://http.debian.org/debian jessie main contrib non-free deb http://ftp.debian.org/debian jessie main contrib non-free Add “localhost:3142” : deb http://localhost:3142/security.debian.org/ jessie/updates main contrib non-free deb http://localhost:3142/http.debian.org/debian jessie main contrib non-free deb http://localhost:3142/ftp.debian.org/debian jessie main contrib non-free Press Ctrl + X and Y to save changes Terminal # apt-get update # apt-get upgrade NOTE: BUG in Debian Live.
    [Show full text]
  • SUSE Linux Enterprise Server 15 SP2 Autoyast Guide Autoyast Guide SUSE Linux Enterprise Server 15 SP2
    SUSE Linux Enterprise Server 15 SP2 AutoYaST Guide AutoYaST Guide SUSE Linux Enterprise Server 15 SP2 AutoYaST is a system for unattended mass deployment of SUSE Linux Enterprise Server systems. AutoYaST installations are performed using an AutoYaST control le (also called a “prole”) with your customized installation and conguration data. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents 1 Introduction to AutoYaST 1 1.1 Motivation 1 1.2 Overview and Concept 1 I UNDERSTANDING AND CREATING THE AUTOYAST CONTROL FILE 4 2 The AutoYaST Control
    [Show full text]
  • Implantación De Linux Sobre Microcontroladores
    Embedded Linux system development Embedded Linux system development DSI Embedded Linux Free Electrons Developers © Copyright 2004-2018, Free Electrons. Creative Commons BY-SA 3.0 license. Latest update: March 14, 2018. Document updates and sources: http://free-electrons.com/doc/training/embedded-linux Corrections, suggestions, contributions and translations are welcome! DSI - FCEIA http://dsi.fceia.unr.edu.ar 1/263 Derechos de copia © Copyright 2018, Luciano Diamand Licencia: Creative Commons Attribution - Share Alike 3.0 http://creativecommons.org/licenses/by-sa/3.0/legalcode Ud es libre de: I copiar, distribuir, mostrar y realizar el trabajo I hacer trabajos derivados I hacer uso comercial del trabajo Bajo las siguientes condiciones: I Atribuci´on. Debes darle el cr´editoal autor original. I Compartir por igual. Si altera, transforma o construye sobre este trabajo, usted puede distribuir el trabajo resultante solamente bajo una licencia id´enticaa ´esta. I Para cualquier reutilizaci´ono distribuci´on,debe dejar claro a otros los t´erminos de la licencia de este trabajo. I Se puede renunciar a cualquiera de estas condiciones si usted consigue el permiso del titular de los derechos de autor. El uso justo y otros derechos no se ven afectados por lo anterior. DSI - FCEIA http://dsi.fceia.unr.edu.ar 2/263 Hiperv´ınculosen el documento Hay muchos hiperv´ınculosen el documento I Hiperv´ıncluosregulares: http://kernel.org/ I Enlaces a la documentaci´ondel Kernel: Documentation/kmemcheck.txt I Enlaces a los archivos fuente y directorios del kernel: drivers/input include/linux/fb.h I Enlaces a declaraciones, definiciones e instancias de los simbolos del kernel (funciones, tipos, datos, estructuras): platform_get_irq() GFP_KERNEL struct file_operations DSI - FCEIA http://dsi.fceia.unr.edu.ar 3/263 Introducci´ona Linux Embebido Introducci´ona DSI Linux Embebido Embedded Linux Developers Free Electrons © Copyright 2004-2018, Free Electrons.
    [Show full text]
  • Guía De Instalación De Debian GNU/Linux Guía De Instalación De Debian GNU/Linux Copyright © 2004 – 2013 El Equipo Del Instalador De Debian
    Guía de instalación de Debian GNU/Linux Guía de instalación de Debian GNU/Linux Copyright © 2004 – 2013 el equipo del instalador de Debian Este documento contiene las instrucciones de instalación del sistema Debian GNU/Linux 7.0 (nombre en clave “wheezy”), para la arquitectura S/390 (“s390”). Además, contiene enlaces a otras fuentes de información, así como información de cómo obtener lo mejor de su nuevo sistema Debian. Aviso Esta guía de instalación está basada en un manual escrito con anterioridad para el antiguo sistema de instalación de Debian (los “boot-floppies”), y ha sido actualizado para documentar el nuevo instalador de Debian. Sin embar- go, el manual no ha sido actualizado y revisado para adecuarse al nuevo instalador para s390. Aún hay partes del manual incompletas, que están desactualizadas o que documentan el instalador «boot-floppies». Puede en- contrar una nueva versión de este manual, que posiblemente documente mejor su arquitectura, en Internet en la página principal de debian-installer (http://www.debian.org/devel/debian-installer/). También podrá encontrar más traducciones de este manual allí. Si ud. puede ayudar con la revisión de esta traducción, por favor, póngase en contacto con la lista de traductores de Debian al español (<[email protected]>). Este manual es software libre, puede redistribuirlo y/o modificarlo bajo los términos de la licencia general pública GNU. Por favor, consulte la licencia en el Apéndice F para más información. Tabla de contenidos Instalar Debian GNU/Linux 7.0 en s390..........................................................................................ix 1. Bienvenido a Debian .......................................................................................................................1 1.1. ¿Qué es Debian?...................................................................................................................1 1.2.
    [Show full text]
  • Debian GNU/Linux Installation Guide
    Debian GNU/Linux Installation Guide July 31, 2021 Debian GNU/Linux Installation Guide Copyright © 2004 – 2021 the Debian Installer team 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. Build version of this manual: 20210730. i Contents 1 Welcome to Debian 1 1.1 What is Debian? . 1 1.2 What is GNU/Linux? . 1 1.3 What is Debian GNU/Linux? . 2 1.4 What is the Debian Installer? . 3 1.5 Getting Debian . 3 1.6 Getting the Newest Version of This Document . 3 1.7 Organization of This Document . 3 1.8 About Copyrights and Software Licenses . 4 2 System Requirements 5 2.1 Supported Hardware . 5 2.1.1 Supported Architectures . 5 2.1.2 Three different ARM ports . 6 2.1.3 Variations in ARM CPU designs and support complexity . 6 2.1.4 Platforms supported by Debian/armhf . 6 2.1.5 Platforms no longer supported by Debian/armhf . 8 2.1.6 Multiple Processors . 8 2.1.7 Graphics Hardware Support . 8 2.1.8 Network Connectivity Hardware . 8 2.1.9 Peripherals and Other Hardware . 8 2.2 Devices Requiring Firmware . 8 2.3 Purchasing Hardware Specifically for GNU/Linux . 9 2.3.1 Avoid Proprietary or Closed Hardware . 9 2.4 Installation Media . 9 2.4.1 CD-ROM/DVD-ROM/BD-ROM . 9 2.4.2 Network . 10 2.4.3 Hard Disk . 10 2.4.4 Un*x or GNU system .
    [Show full text]
  • Linux Booting Procedure How Linux Boot?
    Linux Booting Procedure How Linux boot? 2 What is “boot”? • boot (n.) [1] http://en.wikipedia.org/wiki/Boot 4 Brief etymology[2] • Phrase “pull oneself up by one’s bootstraps” • Misattributed (at latest in 1901!) to “The Surprising Adventures of Baron Munchausen” (1781, Rudolf Erich Raspe) : The baron pulls himself out of a swamp by his hair (pigtail). • The use of this phrase is found in 1834 in the U.S. • “[S]omeone is attempting or has claimed some ludicrously far-fetched or impossible task” • In the 20th century, the “possible bootstrap[3] task” meaning has appeared • “To begin an enterprise or recover from a setback without any outside help; to succeed only on one's own effort or abilities” 5 [2] http://en.wiktionary.org/wiki/pull_oneself_up_by_one%27s_bootstraps [3] http://en.wikipedia.org/wiki/Bootstrapping Bootstrapping (in Computer) • The process of loading the basic software (typically, operating systems) into the main memory from persistent memory (HDD, flash ROM, etc.) • “Boot” is an abbreviation for “bootstrap(ping)” Boostrapping Code 6 System startup Booting sequence 1. Tern on 2. CPU jump to address of BIOS (0xFFFF0) 3. BIOS runs POST (Power-On Self Test) 4. Find bootale devices 5. Loads and execute boot sector form MBR 6. Load OS 5 BIOS (Basic Input/Output System) BIOS refers to the software code run by a computer when first powered on The primary function of BIOS is code program embedded on a chip that recognises and controls various devices that make up the computer. BIOS on board BIOS on screen 6 How computer startup? Booting is a bootstrapping process that starts operating systems when the user turns on a computer system A boot sequence is the set of operations the computer performs when it is switched on that load an operating system 4 Boot loader MBR (Master Boot Record) OS is booted from a hard disk, where the Master Boot Record (MBR) contains the primary boot loader The MBR is a 512-byte sector, located in the first sector on the disk (sector 1 of cylinder 0, head 0) After the MBR is loaded into RAM, the BIOS yields control to it.
    [Show full text]
  • Red Hat Enterprise Linux 7 Kernel Administration Guide
    Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Last Updated: 2018-05-21 Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Marie Dolezelova Red Hat Customer Content Services [email protected] Mark Flitter Red Hat Customer Content Services Douglas Silas Red Hat Customer Content Services Eliska Slobodova Red Hat Customer Content Services Jaromir Hradilek Red Hat Customer Content Services Maxim Svistunov Red Hat Customer Content Services Robert Krátký Red Hat Customer Content Services Stephen Wadeley Red Hat Customer Content Services Florian Nadge Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates.
    [Show full text]
  • Cold Boot Attacks on Encryption Keys
    Lest We Remember: Cold Boot Attacks on Encryption Keys † ‡ J. Alex Halderman∗, Seth D. Schoen , Nadia Heninger∗, William Clarkson∗, William Paul , Joseph A. Calandrino∗, Ariel J. Feldman∗, Jacob Appelbaum, and Edward W. Felten∗ † ‡ ∗ Princeton University Electronic Frontier Foundation Wind River Systems jhalderm, nadiah, wclarkso, jcalandr, ajfeldma, felten @cs.princeton.edu { } [email protected], [email protected], [email protected] Abstract memory. They pose a particular threat to laptop users who rely on disk encryption products, since an adversary who Contrary to popular assumption, DRAMs used in most steals a laptop while an encrypted disk is mounted could modern computers retain their contents for several sec- employ our attacks to access the contents, even if the com- onds after power is lost, even at room temperature and puter is screen-locked or suspended. We demonstrate this even if removed from a motherboard. Although DRAMs risk by defeating several popular disk encryption systems, become less reliable when they are not refreshed, they including BitLocker, TrueCrypt, and FileVault, and we are not immediately erased, and their contents persist expect many similar products are also vulnerable. sufficiently for malicious (or forensic) acquisition of us- able full-system memory images. We show that this phe- While our principal focus is disk encryption, any sen- nomenon limits the ability of an operating system to pro- sitive data present in memory when an attacker gains tect cryptographic key material from an attacker with physical access to the system could be subject to attack. physical access. We use cold reboots to mount successful Many other security systems are probably vulnerable.
    [Show full text]