Proceedings of the Linux Symposium Volume

Total Page:16

File Type:pdf, Size:1020Kb

Proceedings of the Linux Symposium Volume Proceedings of the Linux Symposium Volume Two July 19th–22nd, 2006 Ottawa, Ontario Canada Contents Evolution in Kernel Debugging using Hardware Virtualization With Xen 1 Nitin A. Kamble Improving Linux Startup Time Using Software Resume (and other techniques) 17 Hiroki Kaminaga Automated Regression Hunting 27 A. Bowen, P. Fox, J. Kenefick, A. Romney, J. Ruesch, J. Wilde, & J. Wilson Hacking the Linux Automounter—Current Limitations and Future Directions 37 Ian Maxwell Kent & Jeff Moyer Why NFS Sucks 51 Olaf Kirch Efficient Use of the Page Cache with 64 KB Pages 65 Dave Kleikamp and Badari Pulavarty Startup Time in the 21st Century: Filesystem Hacks and Assorted Tweaks 71 Benjamin C.R. LaHaise Using Hugetlbfs for Mapping Application Text Regions 75 H.J. Lu, K. Doshi, R. Seth, & J. Tran Towards a Better SCM: Revlog and Mercurial 83 Matt Mackall Roadmap to a GL-based composited desktop for Linux 91 K.E. Martin and K. Packard Probing the Guts of Kprobes 101 A. Mavinakayanahalli, P. Panchamukhi, J. Keniston, A. Keshavamurthy, & M. Hiramatsu Shared Page Tables Redux 117 Dave McCracken Extending RCU for Realtime and Embedded Workloads 123 Paul E. McKenney OSTRA: Experiments With on-the-fly Source Patching 139 Arnaldo Carvalho de Melo Design and Implementation to Support Multiple Key Exchange Protocols for IPsec 143 K. Miyazawa, S. Sakane, K. Kamada, M. Kanda, & A. Fukumoto The State of Linux Power Management 2006 151 Patrick Mochel I/O Workload Fingerprinting in the Genetic-Library 165 Jake Moilanen X86-64 XenLinux: Architecture, Implementation, and Optimizations 173 Jun Nakajima, Asit Mallick GCC—An Architectural Overview, Current Status, and Future Directions 185 Diego Novillo Shared-Subtree Concept, Implementation, and Applications in Linux 201 Al Viro & Ram Pai The Ondemand Governor 215 Venkatesh Pallipadi & Alexey Starikovskiy Linux Bootup Time Reduction for Digital Still Camera 231 Chan-Ju Park A Lockless Pagecache in Linux—Introduction, Progress, Performance 241 Nick Piggin The Ongoing Evolution of Xen 255 I. Pratt, D. Magenheimer, H. Blanchard, J. Xenidis, J. Nakajima, & A. Liguori NFSv4 Test Project 267 Tony Reix Measuring Resource Demand on Linux 287 Rik van Riel Improving the Approach to Linux Performance Analysis 295 Jose Santos & Guanglei Li Resizing Memory With Balloons and Hotplug 305 J.H. Schopp, K. Fraser, & M.J. Silbermann Collaborative Memory Management in Hosted Linux Environments 313 M. Schwidefsky, H. Franke, R. Mansell, H. Raj, D. Osisek, & J.H. Choi Chip Multi Processing aware Linux Kernel Scheduler 329 Siddha, Pallipadi and Mallick Dynamic Device Handling on the Modern Desktop 341 K. Sievers & D. Zeuthen Unionfs: User- and Community-Oriented Development of a Unification File System 349 D. Quigley, J. Sipek, C.P. Wright, & E. Zadok VMI: An Interface for Paravirtualization 363 Z. Amsden, D. Arai, D. Hecht, A. Holler, & P. Subrahmanyam HTTP-FUSE Xenoppix 379 K. Suzaki, T. Yagi, K. Iijima, K. Kitagawa, S. Tashiro Virtual Scalability: Charting the Performance of Linux in a Virtual World 393 A. Theurer, K. Rister, O. Krieger, R. Harper, & S. Dobbelstein Automatic System for Linux Kernel Performance Testing 403 A. Ufimtsev & L. Murphy MD RAID Acceleration 409 Dan J. Williams Catalyzing Hardware Driver Development 415 D.J. Wong, A. Bruemmer, D. Fry, & M. Salyzyn Conference Organizers Andrew J. Hutton, Steamballoon, Inc. C. Craig Ross, Linux Symposium Review Committee Jeff Garzik, Red Hat Software Gerrit Huizenga, IBM Dave Jones, Red Hat Software Ben LaHaise, Intel Corporation Matt Mackall, Selenic Consulting Patrick Mochel, Intel Corporation C. Craig Ross, Linux Symposium Andrew Hutton, Steamballoon, Inc. Proceedings Formatting Team John W. Lockhart, Red Hat, Inc. David M. Fellows, Fellows and Carr, Inc. Kyle McMartin Authors retain copyright to all submitted papers, but have granted unlimited redistribution rights to all as a condition of submission. Evolution in Kernel Debugging using Hardware Virtualization With Xen Nitin A. Kamble [email protected] Jun Nakajima [email protected] Asit K. Mallick [email protected] Open Source Technology Center, Intel Corporation Abstract guests. This Xen capability to run unmodified Linux OS or any other unmodified OS also pro- vides a new opportunity to debug an unmodi- Xen’s ability to run unmodified guests with the fied OS using the Xen VMM. virtualization available in hardware opens new doors of possibilities in the kernel debugging. Now it’s possible to debug the Linux kernel or any other PC operating system similar to de- bugging a user process in Linux. Since hard- ware virtualization in-processor enables Xen to implement full virtualization of a guest OS, With this guest debug capability, it is possible there is no need to change the kernel in any way to trap into an unmodified guest such as any to debug it. Linux, Windows, DOS, or any other PC OS; and check the register state, modify registers, This paper demonstrates the new evolutionary set debug breakpoints anywhere including in debug techniques using examples. It also ex- the kernel, read and write memory, or inspect or plains how the new technique actually works. modify the code currently being executed. This new method uses gdb[3] as the front end for debugging. With gdb also comes the source- 1 Introduction level debugging of an unmodified Linux kernel. There are some advantages of using this debug approach compared to other kernel debug op- The Xen[1] open source virtual machine moni- tions, such as the Linux kernel stays unmodi- tor initially started with software virtualization fied, and ability of setting of breakpoints any- by modifying the guest OS kernel. Since Xen where in the code. In fact it is also possible to 3.0, it also supports the Intel R Virtualization set breakpoints in the boot loader such as grub Technology R [2] to create and run unmodified [4] or inside the guest BIOS code. 2 • Evolution in Kernel Debugging using Hardware Virtualization With Xen 2 The Architecture and Design of Guest 0 Guest 1 debugging of an unmodified guest VM Exit VM Entry VM Entry VM Exit The virtualization technology in the processor, and Xen’s ability to take advantage of it, let an VMXON VM Monitor VMXOFF unmodified OS run inside a virtual machine. The following sections first briefly describe the Figure 1: Interaction of Virtual-Machine Mon- virtualization technology in the Intel IA32 pro- itor and Guests cessors, and how Xen[5] hypervisor utilizes this hardware virtualization to create virtual machines (domain) for unmodified guests. its. Figure 1 depicts the interactions between the VMX root and VMX nonroot operations. 2.1 Intel Virtualization Technology for Processor behavior in VMX root operation is IA32 Architecture very much as it is outside VMX operation or without the VT feature in the processor. The Virtualiztion Techinology in the Intel proces- principal differences are that a set of new in- sors augment the IA32 architecture by pro- structions (the VMX instructions) is available viding new processor operation modes called and that the values that can be loaded into cer- VMX operations. And the Virtual-Machine tain control registers are limited. Processor be- Control Structure controls the operation of the havior in VMX non-root operation is restricted virtual machine running in the VMX operation. and modified to facilitate virtualization. Instead of their ordinary operation, certain instructions The following subsections introduce the VMX (including the new VMCALL instruction) and Operation and the Virtual-Machine Control events cause VM exits to the VMM. Because Structure briefly. these VM exits replace ordinary behavior, the functionality of software in VMX non-root op- eration is limited. It is this limitation that al- 2.1.1 Introduction to VMX operation lows the VMM to retain control of processor resources. VT processor support for virtualization is pro- Because VMX operation places these restric- vided by a new form of processor operation tions even on software running with current called VMX operation. There are two kinds privilege level (CPL) 0, guest software can run of VMX operations: VMX root operation and at the privilege level for which it was originally VMX nonroot operation. The Xen VMM runs designed. in VMX root operation and guest software runs in VMX non-root operation. Transitions be- tween VMX root operation and VMX non-root operation are called VMX transitions. There 2.1.2 Virtual-Machine Control Structure are two kinds of VMX transitions. Transitions into VMX non-root operation are called VM en- VMX non-root operation and VMX transitions tries. Transitions from VMX non-root opera- are controlled by a data structure called a vir- tion to VMX root operation are called VM ex- tual machine control structure (VMCS). Ac- 2006 Linux Symposium, Volume Two • 3 cess to the VMCS is managed through a com- 2.3 Internals of debugging an unmodified ponent of processor state called the VMCS guest on Xen pointer (one per logical processor). The value of the VMCS pointer is the 64-bit ad- dress of the VMCS. The VMCS pointer can Figure 3 shows the interactions happening in be read and written using the instructions various Xen components when an unmodi- gdb VMPTRST and VMPTRLD. The VMM con- fied guest is being debugged. Both gdbserver-xen figures a VMCS using other instructions: VM- and are processes running READ, VMWRITE, and VMCLEAR. in the Xen-paravirtualized service OS, also known as domain-0. gdb is totally unmodi- fied. gdbserver is a gdb tool used for re- Please refer to the latest IA-32 SDM[6] for mote debug. gdbserver-xen is a modified more details on the Virtual Machine Extensions gdbserver for utilizing Xen hyper call based in- (VMX) in the Intel Processor. terfaces available in domain-0. The following sections describe interactions 2.2 Xen support for unmodified Guest us- and implementation details for the the Xen ing the Hardware Virtualization components exercised while debugging a un- modified guest OS.
Recommended publications
  • Shorten Device Boot Time for Automotive IVI and Navigation Systems
    Shorten Device Boot Time for Automotive IVI and Navigation Systems Jim Huang ( 黃敬群 ) <[email protected]> Dr. Shi-wu Lo <[email protected]> May 28, 2013 / Automotive Linux Summit (Spring) Rights to copy © Copyright 2013 0xlab http://0xlab.org/ [email protected] Attribution – ShareAlike 3.0 Corrections, suggestions, contributions and translations You are free are welcome! to copy, distribute, display, and perform the work to make derivative works Latest update: May 28, 2013 to make commercial use of the work Under the following conditions Attribution. You must give the original author credit. Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/3.0/legalcode Goal of This Presentation • Propose a practical approach of the mixture of ARM hibernation (suspend to disk) and Linux user-space checkpointing – to shorten device boot time • An intrusive technique for Android/Linux – minimal init script and root file system changes are required • Boot time is one of the key factors for Automotive IVI – mentioned by “Linux Powered Clusters” and “Silver Bullet of Virtualization (Pitfalls, Challenges and Concerns) Continued” at ALS 2013 – highlighted by “Boot Time Optimizations” at ALS 2012 About this presentation • joint development efforts of the following entities – 0xlab team - http://0xlab.org/ – OSLab, National Chung Cheng University of Taiwan, led by Dr.
    [Show full text]
  • Study of File System Evolution
    Study of File System Evolution Swaminathan Sundararaman, Sriram Subramanian Department of Computer Science University of Wisconsin {swami, srirams} @cs.wisc.edu Abstract File systems have traditionally been a major area of file systems are typically developed and maintained by research and development. This is evident from the several programmer across the globe. At any point in existence of over 50 file systems of varying popularity time, for a file system, there are three to six active in the current version of the Linux kernel. They developers, ten to fifteen patch contributors but a single represent a complex subsystem of the kernel, with each maintainer. These people communicate through file system employing different strategies for tackling individual file system mailing lists [14, 16, 18] various issues. Although there are many file systems in submitting proposals for new features, enhancements, Linux, there has been no prior work (to the best of our reporting bugs, submitting and reviewing patches for knowledge) on understanding how file systems evolve. known bugs. The problems with the open source We believe that such information would be useful to the development approach is that all communication is file system community allowing developers to learn buried in the mailing list archives and aren’t easily from previous experiences. accessible to others. As a result when new file systems are developed they do not leverage past experience and This paper looks at six file systems (Ext2, Ext3, Ext4, could end up re-inventing the wheel. To make things JFS, ReiserFS, and XFS) from a historical perspective worse, people could typically end up doing the same (between kernel versions 1.0 to 2.6) to get an insight on mistakes as done in other file systems.
    [Show full text]
  • ECE 598 – Advanced Operating Systems Lecture 19
    ECE 598 { Advanced Operating Systems Lecture 19 Vince Weaver http://web.eece.maine.edu/~vweaver [email protected] 7 April 2016 Announcements • Homework #7 was due • Homework #8 will be posted 1 Why use FAT over ext2? • FAT simpler, easy to code • FAT supported on all major OSes • ext2 faster, more robust filename and permissions 2 btrfs • B-tree fs (similar to a binary tree, but with pages full of leaves) • overwrite filesystem (overwite on modify) vs CoW • Copy on write. When write to a file, old data not overwritten. Since old data not over-written, crash recovery better Eventually old data garbage collected • Data in extents 3 • Copy-on-write • Forest of trees: { sub-volumes { extent-allocation { checksum tree { chunk device { reloc • On-line defragmentation • On-line volume growth 4 • Built-in RAID • Transparent compression • Snapshots • Checksums on data and meta-data • De-duplication • Cloning { can make an exact snapshot of file, copy-on- write different than link, different inodles but same blocks 5 Embedded • Designed to be small, simple, read-only? • romfs { 32 byte header (magic, size, checksum,name) { Repeating files (pointer to next [0 if none]), info, size, checksum, file name, file data • cramfs 6 ZFS Advanced OS from Sun/Oracle. Similar in idea to btrfs indirect still, not extent based? 7 ReFS Resilient FS, Microsoft's answer to brtfs and zfs 8 Networked File Systems • Allow a centralized file server to export a filesystem to multiple clients. • Provide file level access, not just raw blocks (NBD) • Clustered filesystems also exist, where multiple servers work in conjunction.
    [Show full text]
  • Solaris 10 End of Life
    Solaris 10 end of life Continue Oracle Solaris 10 has had an amazing OS update, including ground features such as zones (Solaris containers), FSS, Services, Dynamic Tracking (against live production operating systems without impact), and logical domains. These features have been imitated in the market (imitation is the best form of flattery!) like all good things, they have to come to an end. Sun Microsystems was acquired by Oracle and eventually, the largest OS known to the industry, needs to be updated. Oracle has set a retirement date of January 2021. Oracle indicated that Solaris 10 systems would need to raise support costs. Oracle has never provided migratory tools to facilitate migration from Solaris 10 to Solaris 11, so migration to Solaris has been slow. In September 2019, Oracle decided that extended support for Solaris 10 without an additional financial penalty would be delayed until 2024! Well its March 1 is just a reminder that Oracle Solaris 10 is getting the end of life regarding support if you accept extended support from Oracle. Combined with the fact gdpR should take effect on May 25, 2018 you want to make sure that you are either upgraded to Solaris 11.3 or have taken extended support to obtain any patches for security issues. For more information on tanningix releases and support dates of old and new follow this link ×Sestive to abort the Unix Error Operating System originally developed by Sun Microsystems SolarisDeveloperSun Microsystems (acquired by Oracle Corporation in 2009)Written inC, C'OSUnixWorking StateCurrentSource ModelMixedInitial release1992; 28 years ago (1992-06)Last release11.4 / August 28, 2018; 2 years ago (2018-08-28)Marketing targetServer, PlatformsCurrent: SPARC, x86-64 Former: IA-32, PowerPCKernel typeMonolithic with dynamically downloadable modulesDefault user interface GNOME-2-LicenseVariousOfficial websitewww.oracle.com/solaris Solaris is the own operating system Of Unix, originally developed by Sunsystems.
    [Show full text]
  • Support for Mobile Augmented and Synthesized Worlds
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Illinois Digital Environment for Access to Learning and Scholarship Repository Support for Mobile Augmented and Synthesized Worlds December 17, 2007 Won J. Jeon and Roy H. Campbell {wonjeon, rhc}@uiuc.edu Department of Computer Science University of Illinois at Urbana-Champaign Abstract Virtual worlds provide 3D-immersive experiences to users and some of them already have already launched commercial service to users. As computing environment becomes more heterogeneous, more mobile users are anticipated to access the virtual world with their mobile devices. However, still there are challenges and problems to be addressed for mobile users. In this report, state-of-art virtual world platforms are presented and their key features are compared. We compare possible approaches to tackle these problems to support virtual worlds for mobile devices. Transcoding scheme at the proxy is presented and evaluated for a given computing and networking environment. 1. Introduction A virtual world is a computer-simulated or synthesized environment where multiple users inhabit and interact to each other via avatars. The world mimics the real world via simulated real world physics and the persistence of the world comes from maintaining and updating the state of the world around the clock. Historically this concept is rooted from distributed interactive simulation (DIS) and massively multiplayer online role- playing game (MMORPG). DIS is used mainly by military organizations whereas MMORPG has gained huge popularity among general users or gamers. The world is typically represented as 2D or 3D graphics to multiple users.
    [Show full text]
  • Hardware-Driven Evolution in Storage Software by Zev Weiss A
    Hardware-Driven Evolution in Storage Software by Zev Weiss A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy (Computer Sciences) at the UNIVERSITY OF WISCONSIN–MADISON 2018 Date of final oral examination: June 8, 2018 ii The dissertation is approved by the following members of the Final Oral Committee: Andrea C. Arpaci-Dusseau, Professor, Computer Sciences Remzi H. Arpaci-Dusseau, Professor, Computer Sciences Michael M. Swift, Professor, Computer Sciences Karthikeyan Sankaralingam, Professor, Computer Sciences Johannes Wallmann, Associate Professor, Mead Witter School of Music i © Copyright by Zev Weiss 2018 All Rights Reserved ii To my parents, for their endless support, and my cousin Charlie, one of the kindest people I’ve ever known. iii Acknowledgments I have taken what might be politely called a “scenic route” of sorts through grad school. While Ph.D. students more focused on a rapid graduation turnaround time might find this regrettable, I am glad to have done so, in part because it has afforded me the opportunities to meet and work with so many excellent people along the way. I owe debts of gratitude to a large cast of characters: To my advisors, Andrea and Remzi Arpaci-Dusseau. It is one of the most common pieces of wisdom imparted on incoming grad students that one’s relationship with one’s advisor (or advisors) is perhaps the single most important factor in whether these years of your life will be pleasant or unpleasant, and I feel exceptionally fortunate to have ended up iv with the advisors that I’ve had.
    [Show full text]
  • Oracle® Linux 7 Managing File Systems
    Oracle® Linux 7 Managing File Systems F32760-07 August 2021 Oracle Legal Notices Copyright © 2020, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Changing Java Applications
    Menu Topics Archives Downloads Subscribe The code underpinning the Brazilian CODING healthcare system—and other world- changing Java applications The code underpinning the Brazilian Thanks for the memories healthcare system—and other world- Developer software for the win changing Java applications Banking on financial software Games and visualization Your reactions to the list of the 25 greatest Efficient communication Java apps ever written Science and AI applications by Alexa Morales August 28, 2020 It was with a smidge of trepidation that I offered my list of the 25 greatest Java applications, frameworks, platforms, and libraries ever written. After all, developers are a demanding audience. But the article received hundreds of comments on Reddit, Slashdot, Hacker News, and Twitter, and it inspired many letters to the editor. The piece even received happy social media posts from those who made the list, including the US National Security Agency and a.i. solutions. The US National Security Agency was secretly pleased we noticed its Ghidra binary decompilation tool. The team from a.i. solutions was happy its DSTE trajectory design tool made the list. The tenor of conversation was both positive and polite. That speaks volumes about the excellent character of Java developers, don’t you think? But, developers being who they are, opinions on what should have made the list abounded. The good news is, Java has transformed the world. The bad news is, my list didn’t represent enough of the world beyond the United States. For example, there’s the Java code written to manage the Brazilian Healthcare Information System and the Brazilian tax system (Duke’s Choice Award winner in 2005).
    [Show full text]
  • Enterprise Filesystems
    Enterprise Filesystems Eric Sandeen Principal Software Engineer, Red Hat Feb 21, 2013 1 ERIC SANDEEN What We'll Cover ● Local “Enterprise-ready” Linux filesystems ● Ext3 ● Ext4 ● XFS ● BTRFS ● Use cases, features, pros & cons of each ● Recent & future work ● Features ● Scalability ● Benchmarks 2 ERIC SANDEEN Local Filesystems in RHEL6 ● We ship what customers need and can rely on ● We ship what we test and support ● Major on-disk local filesystems ● Ext3, Ext4, XFS, BTRFS* ● Others are available for special purposes ● fat, vfat, msdos, udf, cramfs, squashfs... ● We'll cover the “big four” today 3 ERIC SANDEEN The Ext3 filesystem ● Ext3 is was the most common file system in Linux ● Most distributions historically used it as their default ● Applications tuned to its specific behaviors (fsync...) ● Familiar to most system administrators ● Ext3 challenges ● File system repair (fsck) time can be extremely long ● Limited scalability - maximum file system size of 16TB ● Can be significantly slower than other local file systems ● direct/indirect, bitmaps, no delalloc ... 4 ERIC SANDEEN The Ext4 filesystem ● Ext4 has many compelling new features ● Extent based allocation ● Faster fsck time (up to 10x over ext3) ● Delayed allocation, preallocation ● Higher bandwidth ● Should be relatively familiar for existing ext3 users ● Ext4 challenges ● Large device support not polished in its user space tools ● Limits supported maximum file system size to 16TB* ● Has different behavior over system failure 5 ERIC SANDEEN The XFS filesystem ● XFS is very robust
    [Show full text]
  • Managing File Systems in Oracle® Solaris 11.4
    ® Managing File Systems in Oracle Solaris 11.4 Part No: E61016 November 2020 Managing File Systems in Oracle Solaris 11.4 Part No: E61016 Copyright © 2004, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial
    [Show full text]
  • CIS Ubuntu Linux 18.04 LTS Benchmark
    CIS Ubuntu Linux 18.04 LTS Benchmark v1.0.0 - 08-13-2018 Terms of Use Please see the below link for our current terms of use: https://www.cisecurity.org/cis-securesuite/cis-securesuite-membership-terms-of-use/ 1 | P a g e Table of Contents Terms of Use ........................................................................................................................................................... 1 Overview ............................................................................................................................................................... 12 Intended Audience ........................................................................................................................................ 12 Consensus Guidance ..................................................................................................................................... 13 Typographical Conventions ...................................................................................................................... 14 Scoring Information ..................................................................................................................................... 14 Profile Definitions ......................................................................................................................................... 15 Acknowledgements ...................................................................................................................................... 17 Recommendations ............................................................................................................................................
    [Show full text]
  • NFS-HOWTO.Pdf
    Linux NFS−HOWTO Tavis Barr tavis dot barr at liu dot edu Nicolai Langfeldt janl at linpro dot no Seth Vidal skvidal at phy dot duke dot edu Tom McNeal trmcneal at attbi dot com 2002−08−25 Revision History Revision v3.1 2002−08−25 Revised by: tavis Typo in firewalling section in 3.0 Revision v3.0 2002−07−16 Revised by: tavis Updates plus additions to performance, security Linux NFS−HOWTO Table of Contents 1. Preamble..........................................................................................................................................................1 1.1. Legal stuff.........................................................................................................................................1 1.2. Disclaimer.........................................................................................................................................1 1.3. Feedback...........................................................................................................................................1 1.4. Translation........................................................................................................................................1 1.5. Dedication.........................................................................................................................................1 2. Introduction.....................................................................................................................................................2 2.1. What is NFS?....................................................................................................................................2
    [Show full text]