Fedora 25 Networking Guide

Total Page:16

File Type:pdf, Size:1020Kb

Fedora 25 Networking Guide Fedora 25 Networking Guide Configuration and Administration of Networking for Fedora 25 Stephen Wadeley Networking Guide Draft Fedora 25 Networking Guide Configuration and Administration of Networking for Fedora 25 Edition 1 Author Stephen Wadeley [email protected] Copyright © 2016 Red Hat, Inc. and others. 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/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. 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, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. 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. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners. The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 25. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book. Draft Draft Preface vii 1. Target Audience ............................................................................................................ vii 2. About This Book ............................................................................................................ vii 3. How to Read this Book .................................................................................................. vii 4. Document Conventions ................................................................................................. viii 4.1. Typographic Conventions ..................................................................................... ix 4.2. Pull-quote Conventions ......................................................................................... x 4.3. Notes and Warnings ............................................................................................ xi 5. Feedback ....................................................................................................................... xi 6. Acknowledgments .......................................................................................................... xii I. Networking 1 1. Introduction to Fedora Networking 3 1.1. How this Book is Structured .................................................................................. 3 1.2. Introduction to NetworkManager ............................................................................ 3 1.3. Installing NetworkManager .................................................................................... 4 1.3.1. The NetworkManager Daemon ................................................................... 4 1.3.2. Interacting with NetworkManager ................................................................ 4 1.4. Network Configuration Using the Command Line Interface (CLI) .............................. 5 1.5. Network Configuration Using NetworkManager's CLI (nmcli) .................................... 5 1.6. NetworkManager and the Network Scripts ............................................................. 6 1.7. Network Configuration Using sysconfig Files .......................................................... 7 1.8. Additional Resources ............................................................................................ 8 1.8.1. Installed Documentation ............................................................................. 8 2. Configure Networking 9 2.1. Static and Dynamic Interface Settings ................................................................... 9 2.1.1. When to Use Static Network Interface Settings ............................................ 9 2.1.2. When to Use Dynamic Interface Settings .................................................... 9 2.1.3. Selecting Network Configuration Methods ................................................. 10 2.2. Using NetworkManager with the GNOME Graphical User Interface ........................ 10 2.2.1. Connecting to a Network Using a GUI ...................................................... 10 2.2.2. Configuring New and Editing Existing Connections ..................................... 10 2.2.3. Connecting to a Network Automatically ..................................................... 11 2.2.4. System-wide and Private Connection Profiles ............................................ 12 2.2.5. Configuring a Wired (Ethernet) Connection ................................................ 13 2.2.6. Configuring a Wi-Fi Connection ................................................................ 14 2.2.7. Establishing a VPN Connection ................................................................ 16 2.2.8. Establishing a Mobile Broadband Connection ............................................ 19 2.2.9. Establishing a DSL Connection ................................................................ 22 2.2.10. Configuring Connection Settings ............................................................. 23 2.3. Using the Command Line Interface (CLI) ............................................................. 30 2.3.1. Configuring a Network Interface Using ifcfg Files ....................................... 30 2.3.2. Configuring a Network Interface Using ip Commands ................................. 31 2.3.3. Static Routes and the Default Gateway ..................................................... 32 2.3.4. Configuring Static Routes in ifcfg files ....................................................... 33 2.3.5. Configuring IPv6 Tokenized Interface Identifiers ......................................... 35 2.4. Using the NetworkManager Command Line Tool, nmcli ......................................... 36 2.4.1. Understanding the nmcli Options .............................................................. 39 2.4.2. Connecting to a Network Using nmcli ........................................................ 39 2.4.3. Configuring Static Routes Using nmcli ....................................................... 45 2.5. Additional Resources .......................................................................................... 45 2.5.1. Installed Documentation ........................................................................... 45 iii Networking Guide Draft 2.5.2. Online Documentation .............................................................................. 46 3. Configure Host Names 47 3.1. Understanding Host Names ................................................................................ 47 3.1.1. Recommended Naming Practices ............................................................. 47 3.2. Configuring Host Names Using hostnamectl ......................................................... 47 3.2.1. View All the Host Names ......................................................................... 47 3.2.2. Set All the Host Names ........................................................................... 48 3.2.3. Set a Particular Host Name ...................................................................... 48 3.2.4. Clear a Particular Host Name ................................................................... 48 3.2.5. Changing Host Names Remotely .............................................................. 48 3.3. Configuring Host Names Using nmcli ................................................................... 48 3.4. Additional Resources .......................................................................................... 49 3.4.1. Installed Documentation ........................................................................... 49 3.4.2. Online Documentation .............................................................................. 49 4. Configure Network Bonding 51 4.1. Understanding the Default Behavior of Master and Slave Interfaces ....................... 51 4.2. Creating a Bond Connection Using a GUI ............................................................ 51 4.2.1. Establishing a Bond Connection ............................................................... 52 4.3. Using the Command Line Interface (CLI) ............................................................. 55 4.3.1. Check if Bonding Kernel Module is Installed .............................................. 55 4.3.2. Create a Channel Bonding Interface ......................................................... 55
Recommended publications
  • Desktop Migration and Administration Guide
    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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, the Red Hat 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. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Red Hat Enterprise Linux 7 Technical Overview
    RED HAT ENTERPRISE LINUX 7 TECHNICAL OVERVIEW Ingo Börnig Senior Solutions Architect, Red Hat 2014-07-08 1 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 AGENDA 1 RED HAT ENTERPRISE LINUX 7 INTRODUCTION 2 LIGHTWEIGHT APPLICATION ISOLATION 3 WINDOWS INTEROPERABILITY 4 FILE SYSTEMS AND STORAGE 5 OPTIMAL PERFORMANCE MANAGEMENT 6 INSTALLATION AND DEPLOYMENT 2 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 AGENDA (cont.) 7 SYSTEM MANAGEMENT AND FEATURES 8 VIRTUALIZATION 9 DESKTOP AND DEVELOPER FEATURES 10 SUMMARY 3 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 RED HAT ENTERPRISE LINUX 7 INTRODUCTION 4 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 RED HAT ENTERPRISE LINUX 7 REDEFINING THE ENTERPRISE OS FLEXIBILITY to STABILITY to efficiently CERTAINTY of quickly adapt to meet challenges of mission-critical demands for datacenter virtualization reliability and business agility and cloud military-grade security 90% OF FORTUNE 500 COMPANIES TRUST RED HAT ENTERPRISE LINUX FOR THEIR CRITICAL BUSINESS INFRASTRUCTURE. 5 RED HAT CONFIDENTIAL | PLATFORM PRODUCT MARKETING RED HAT ENTERPRISE LINUX 7 BASICS ● Based on Fedora 19, the upstream kernel version 3.10 and over 4000 patches (additional features, bugfixes, security errata) ● Supported hardware architectures: ● Intel/AMD 64-bit (x86_64) ● IBM POWER ● IBM System z ● Support for 32-bit applications enabled via inclusion of 32-bit libraries (multilib). 6 RED HAT ENTERPRISE LINUX 7HIGHLIGHTS RED HAT 7 STABLE AND FLEXIBLE EFFICIENT CERTAINTY OF MISSION-CRITICAL RELIABILITY AND MILITARY-GRADE SECURITY MILITARY-GRADE AND RELIABILITY
    [Show full text]
  • 1. D-Bus a D-Bus FAQ Szerint D-Bus Egy Interprocessz-Kommunikációs Protokoll, És Annak Referenciamegvalósítása
    Az Udev / D-Bus rendszer - a modern asztali Linuxok alapja A D-Bus rendszer minden modern Linux disztribúcióban jelen van, sőt mára már a Linux, és más UNIX jellegű, sőt nem UNIX rendszerek (különösen a desktopon futó változatok) egyik legalapvetőbb technológiája, és az ismerete a rendszergazdák számára lehetővé tesz néhány rendkívül hasznos trükköt, az alkalmazásfejlesztőknek pedig egyszerűen KÖTELEZŐ ismerniük. Miért ilyen fontos a D-Bus? Mit csinál? D-Bus alapú technológiát teszik lehetővé többek között azt, hogy közönséges felhasználóként a kedvenc asztali környezetünkbe bejelentkezve olyan feladatokat hajtsunk végre, amiket a kernel csak a root felasználónak engedne meg. Felmountolunk egy USB meghajtót? NetworkManagerrel konfiguráljuk a WiFi-t, a 3G internetet vagy bármilyen más hálózati csatolót, és kapcsolódunk egy hálózathoz? Figyelmeztetést kapunk a rendszertől, hogy új szoftverfrissítések érkeztek, majd telepítjük ezeket? Hibernáljuk, felfüggesztjük a gépet? A legtöbb esetben ma már D-Bus alapú technológiát használunk ilyen esetben. A D-Bus lehetővé teszi, hogy egymástól függetlenül, jellemzően más UID alatt indított szoftverösszetevők szabványos és biztonságos módon igénybe vegyék egymás szolgáltatásait. Ha valaha lesz a Linuxhoz professzionális desktop tűzfal vagy vírusirtó megoldás, a dolgok jelenlegi állasa szerint annak is D- Bus technológiát kell használnia. A D-Bus technológia legfontosabb ihletője a KDE DCOP rendszere volt, és mára a D-Bus leváltotta a DCOP-ot, csakúgy, mint a Gnome Bonobo technológiáját. 1. D-Bus A D-Bus FAQ szerint D-Bus egy interprocessz-kommunikációs protokoll, és annak referenciamegvalósítása. Ezen referenciamegvalósítás egyik összetevője, a libdbus könyvtár a D- Bus szabványnak megfelelő kommunikáció megvalósítását segíti. Egy másik összetevő, a dbus- daemon a D-Bus üzenetek routolásáért, szórásáért felelős.
    [Show full text]
  • Configure. Manage. Monitor
    OpenLMI Configure. Manage. Monitor. March 2013 Linux System Management Today Is this you? 2 Storage ●Done with local commands: ●parted ●pvcreate, lvcreate, vgcreate ●mdraid ●vgextend, resize2fs 3 Networking ●Edited /etc/sysconfig/networking scripts ●nmcli command line tool 4 Notice anything? 5 Notice anything? ●Both methods require a local shell ●The methods had an entirely unrelated user experience 6 Training Costs ●There is a completely isolated path to learning administration of either approach ●Learning either task does not help you learn the other 7 Training Costs ●System services ●Installing software and patches ●Firewall ●Performance tuning ●... 8 Research ●“The difficulty of managing these components is directly impacting our customers' ability to consume more Linux” -- 2011 Red Hat Customer Survey Results (paraphrased) 9 OpenLMI ●Provide a complete system for System Management ●Local and network-facing API ●Common interface for all subsystems ●Built on industry-standard protocols 10 Blivet ●Split from the Anaconda installer project ●Python library for manipulating storage at all levels 11 NetworkManager ●D-BUS API ●Consistency guarantees on changes 12 systemd ●D-BUS API for monitoring system services ●Journald API for log monitoring 13 DMTF-CIM ●Industry-standard model for system management ●Comprehensive object-oriented design addressing most aspects of system capabilities 14 What about simplicity? ●CIM is a complex model that many find intimidating 15 LMIShell ●Python-based scripting environment for OpenLMI/CIM ●Simplifies the
    [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]
  • Configuration and Administration of Networking for Fedora 23
    Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Stephen Wadeley Networking Guide Draft Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Edition 1.0 Author Stephen Wadeley [email protected] Copyright © 2015 Red Hat, Inc. and others. 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/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. 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, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. 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. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
    [Show full text]
  • A Brief History of GNOME
    A Brief History of GNOME Jonathan Blandford <[email protected]> July 29, 2017 MANCHESTER, UK 2 A Brief History of GNOME 2 Setting the Stage 1984 - 1997 A Brief History of GNOME 3 Setting the stage ● 1984 — X Windows created at MIT ● ● 1985 — GNU Manifesto Early graphics system for ● 1991 — GNU General Public License v2.0 Unix systems ● 1991 — Initial Linux release ● Created by MIT ● 1991 — Era of big projects ● Focused on mechanism, ● 1993 — Distributions appear not policy ● 1995 — Windows 95 released ● Holy Moly! X11 is almost ● 1995 — The GIMP released 35 years old ● 1996 — KDE Announced A Brief History of GNOME 4 twm circa 1995 ● Network Transparency ● Window Managers ● Netscape Navigator ● Toolkits (aw, motif) ● Simple apps ● Virtual Desktops / Workspaces A Brief History of GNOME 5 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto ● Founded by Richard Stallman ● ● 1991 — GNU General Public License v2.0 Our fundamental Freedoms: ○ Freedom to run ● 1991 — Initial Linux release ○ Freedom to study ● 1991 — Era of big projects ○ Freedom to redistribute ○ Freedom to modify and ● 1993 — Distributions appear improve ● 1995 — Windows 95 released ● Also, a set of compilers, ● 1995 — The GIMP released userspace tools, editors, etc. ● 1996 — KDE Announced This was an overtly political movement and act A Brief History of GNOME 6 Setting the stage ● 1984 — X Windows created at MIT “The licenses for most software are ● 1985 — GNU Manifesto designed to take away your freedom to ● 1991 — GNU General Public License share and change it. By contrast, the v2.0 GNU General Public License is intended to guarantee your freedom to share and ● 1991 — Initial Linux release change free software--to make sure the ● 1991 — Era of big projects software is free for all its users.
    [Show full text]
  • Russell Doty Technology Product Manager, Red Hat Stephen Gallagher System Architect, Red Hat Mid Level Sysadmin
    Administer Production Servers Effectively with OpenLMI Russell Doty Technology Product Manager, Red Hat Stephen Gallagher System Architect, Red Hat Mid Level Sysadmin Routine, day to day tasks Experienced with Microsoft & VMware New to Linux Experienced Linux SysAdmin Big Bag 'O Scripts & ssh Powered by nmcli lvcreate HELP!mkfs.xfs yum parted systemctl Need to Automate! Prerequisite for the automated factory: Robots In other words: An infrastructure and foundation for automation. Client Python CLI Scripting Java C/C++ Remote Communications Abstraction API nmcli yum lvcreate Mkfs.xfs Parted systemctl We Can Build This! Why OpenLMI? Previous Open Source Remote Management Tools Lacked a Strong Foundation – A Management API What is OpenLMI? •A set of Management Agents • That can change the system •A Standardized Remote API •A Standard Communications Infrastructure • Built on XML over https •A Client Environment • Scripting built on Python • CLI • Other languages OpenLMI Providers - Heavy Lifting •Perform management operations •Provide standard API • Low level, functional API • Remote/Local API •Built on existing Linux tools and utilities (e.g. parted, lvcreate, Network Manager) Object Broker - OpenPegasus •Manages Providers • Commands – attributes & methods • Navigation & query • Events (Indications) •Manages Communications • WBEM – CIM/XML over https •Manages Authentication & Access Events - OpenLMI Indications •Notification of Asynchronous Events • e.g. job completion, drive failure, NIC changed state, password changed •Listener registers with CIMOM • Multiple Listeners per event •All registered Listeners notified when event occurs •Powerful tool for monitoring Client Interfaces •OpenLMI API • Low level functional API • Full coverage •LMIShell Modules (EPEL) • Task oriented Python modules • Subset of full API •LMI CLI (EPEL) • Task oriented, user friendly CLI • BASH shell friendly • Least coverage Sounds Interesting..
    [Show full text]
  • Configure, Manage, Monitor Linux Systems Russell Doty [email protected] Red Hat
    Server Management Configure, Manage, Monitor Linux Systems Russell Doty [email protected] Red Hat 1 Copyright © 2014 Red Hat Mid Level Sysadmin Routine, day to day tasks Experienced with Microsoft & VMware New to Linux 2 Copyright © 2014 Red Hat lvcreate nmcli mkfs.xfs HELP!yum parted systemctl 3 Copyright © 2014 Red Hat Experienced Linux Sysadmin Big Bag 'O Scripts & ssh Powered by 4 Copyright © 2014 Red Hat OpenLMI Project Goals ● Improve manageability of Linux systems ● Configuration of remote servers ● Main Initial Focus: configure storage, networks, and authentication ● Broader management support planned ● Reduce learning curve for new SysAdmins to perform common Linux administration tasks ● Provide a foundation for advanced automation and interfaces ● Build on open industry standards ● Open and extensible ● Including 3rd parties and customers 5 Copyright © 2014 Red Hat What Can You Do With OpenLMI? ● Example: Storage ● Determine what storage devices are connected to the system ● Friendly device names & persistent device names ● Partition, format, encrypt, create RAID sets, create logical volumes and volume groups, mount filesystems ● Local & remote block devices ● From programs, scripts or CLI ● CLI example: “lmi> storage raid create –name R1 5 sdb sdc sdd sde sdf” (creates 5 disk RAID 5 set called R1) ● More power and flexibility from LMIShell and OpenLMI API ● Query, configure, monitor and change storage 6 Copyright © 2014 Red Hat What is OpenLMI? ● A set of Management Agents ● That query, modify & monitor systems ● A Standardized
    [Show full text]
  • SUSE Linux Enterprise Server 15 SP2 Security and Hardening Guide Security and Hardening Guide SUSE Linux Enterprise Server 15 SP2
    SUSE Linux Enterprise Server 15 SP2 Security and Hardening Guide Security and Hardening Guide SUSE Linux Enterprise Server 15 SP2 Introduces basic concepts of system security, covering both local and network security aspects. Shows how to use the product inherent security software like AppArmor, SELinux, or the auditing system that reliably collects information about any security-relevant events. Supports the administrator with security-related choices and decisions in installing and setting up a secure SUSE Linux Enterprise Server and additional processes to further secure and harden that installation. 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
    [Show full text]
  • Oracle® Linux 7 Release Notes for Oracle Linux 7
    Oracle® Linux 7 Release Notes for Oracle Linux 7 E53499-20 March 2021 Oracle Legal Notices Copyright © 2011,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]
  • Red Hat Enterprise Linux Server for ARM 7.1 Release Notes
    Red Hat Enterprise Linux Server for ARM 7.1 Release Notes Release Notes for Red Hat Enterprise Linux Server for ARM Red Hat Customer Content Services Red Hat Enterprise Linux Server for ARM 7.1 Release Notes Release Notes for Red Hat Enterprise Linux Server for ARM Red Hat Customer Content Services Legal Notice Copyright © 2015 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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, MetaMatrix, 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. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]