DOCSLIB.ORG

Sudo Subscription-Manager Repos \ --Enable Rhel-7-Server-Rpms

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sudo Subscription-Manager Repos \ --Enable Rhel-7-Server-Rpms Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 50 yum repository details in /etc/yum.repos.d • Under /etc/yum.repos.d are the files which define the repositories to be used; for the CentOS 8 distribution these include: ♦ CentOS-Base.repo - contains the BaseOS repository details. ♦ CentOS-AppStream.repo - used to install AppStream packages from the distribution. • For our own in-house courses, the above repo files have been edited on the training systems so that the machine looks only to the training server vespa on the local network when installing or updating packages; this can be seen as follows: $ yum -v repolist • There should be three main repositories: Repo-id : AppStream-FA Repo-name : CentOS-8 - AppStream from FA server Repo-revision : 8.3.2011 Repo-distro-tags : [cpe:/o:centos:centos:8]: , 8, C, O, S, e, n, t Repo-updated : Tue 15 Dec 2020 03:05:32 PM GMT Repo-pkgs : 5,754 Repo-available-pkgs : 5,058 Repo-size : 6.9 G Repo-baseurl : http://192.168.200.41/centos/8/AppStream Repo-expire : 172,800 second(s) (last: Thu 31 Dec 2020 05:34:39 PM GMT) 50 of 617 First Alternative 2021 51 Repo-filename : /etc/yum.repos.d/CentOS-AppStream.repo Repo-id : BaseOS-FA Repo-name : CentOS-8 - Base on FA local http server Repo-revision : 8.3.2011 Repo-distro-tags : [cpe:/o:centos:centos:8]: , 8, C, O, S, e, n, t Repo-updated : Tue 15 Dec 2020 03:05:26 PM GMT Repo-pkgs : 1,697 Repo-available-pkgs : 1,695 Repo-size : 1.1 G Repo-baseurl : http://192.168.200.41/centos/8/BaseOS Repo-expire : 172,800 second(s) (last: Thu 31 Dec 2020 05:34:41 PM GMT) Repo-filename : /etc/yum.repos.d/CentOS-Base.repo Repo-id : extras-FA Repo-name : CentOS-8 - Extras on FA server Repo-revision : 1605188560 Repo-updated : Thu 12 Nov 2020 01:42:22 PM GMT Repo-pkgs : 30 Repo-available-pkgs : 30 Repo-size : 338 k Repo-baseurl : http://192.168.200.41/centos/8/Extras/ Repo-expire : 172,800 second(s) (last: Thu 31 Dec 2020 05:34:41 PM GMT) Repo-filename : /etc/yum.repos.d/CentOS-Extras.repo Total packages : 7,481 • On a system with the standard .repo files, the output would contain references to the CentOS online repos. 51 of 617 First Alternative 2021 Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 52 yum repository details • yum is able to pick a suitable mirror for downloading by referring to a mirrorlist directive in the CentOS-Base.repo file, which provides a list of download URLs. • Here is an example repo entry from the standard CentOS- Base.repo file: [BaseOS] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&re po=BaseOS&infra=$infra #baseurl=http://mirror.centos.org/$contentdir/$releasever/BaseOS/$basearch/os/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial ♦ Remember the GPG key location? We used it earlier with rpm. ♦ The repo files on the training systems are configured to disable the standard repos. • Some repo entries may also include: enabled=0 • If enabled=0, do not use this repo; if set to 1, repo is enabled. This can be changed by manual editing or by command, which you will see later. • For details of other entries run: $ man yum.conf 52 of 617 First Alternative 2021 53 yum repository details RHEL8 • On a RHEL8 system you will find a single redhat.repo file in /etc/yum.repos.d containing all possible repos, with the relevant entries enabled, according to your subscription. • This file is updated by the subscription-manager command, so there is never a need to edit it manually. • You might sometimes see examples of yum (or dnf) commands where repos are enabled/disabled on the command line. • On a RHEL8 system this is most likely to be done by running subscription-manager, for example: $ sudo subscription-manager repos \ --enable rhel-7-server-rpms ♦ This example you will see when we cover RHEL7 to RHEL8 in-place upgrades later in the course. 53 of 617 First Alternative 2021 54 Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 Creating local yum repositories • Creating a local repository means you can download packages from online repositories to just a single system, then use that system to update others. • The server used on this course has its own repositories, which all the training machines are configured to use. • The /etc/yum.repos.d/CentOS-Base.repo file contains: [BaseOS-FA] name=CentOS-$releasever - Base on FA local http server baseurl=http://192.168.200.41/centos/8/BaseOS gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial ♦ The original entry is still in the file but enabled is set to 0 so it does not get used. • 192.168.200.41 refers to the server vespa. • gpgcheck verifies the authenticity of packages loaded from repos, as we saw earlier. • There are two other enabled repository files in the directory, one for AppStream and the other for Extras. • Important note: There is no updates repository anymore – all updates are pushed directly to the BaseOS and AppStream repos. Keep reading….. 54 of 617 First Alternative 2021 55 Creating local yum CentOS repositories - Choices • There are three types available when it comes to using CentOS 8 repos: ♦ Fixed - Repos which are fixed at a given point release, for example 8.1. Good examples are the BaseOS and AppStream repos contained in the distribution ISO tree. ♦ Updated - Repos which receive package updates. Examples would be the repos which are accessed online using the default /etc/yum.repos.d files supplied with CentOS 8 release. ♦ 8-Stream - a new collaborative repo between CentOS and RHEL, which reflects the RedHat development taking place for the next point release. • Use cases: ♦ Fixed - use for initial installs, either from ISO/DVD or a network source if using Kickstart. ♦ Updated - use to update installed system with the latest bug and security fixes, and new features, including to the next point release. ♦ 8-Stream - for the curious, should not be used in production. See the following notes for more information if you wish to enable 8-Stream. • You may see another repo file CentOS-CR.repo, which is known as the Continuous Release repo, but is disabled by default. 55 of 617 First Alternative 2021 Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 56 • Note that it is updated only occasionally and may be empty, in which case it will be ignored. • It only has content between the RedHat upstream release date and the corresponding CentOS release date, so that you can obtain updated packages before the CentOS release is available. • An example would be that RHEL8.3 is released, with CentOS8.3 a couple of months later, and the updated packages would be available from the CR repo during that 2-month gap. • To enable the repo, you can edit the CentOS-CR.repo file and set enabled=1, or do it from the command line: $ sudo yum config-manager --enable cr • For the full details, have a look here: https://wiki.centos.org/AdditionalResources/Repositories/CR 56 of 617 First Alternative 2021 57 Creating local yum repositories for RedHat • RedHat provide full instructions for creating a local mirror repo of the latest updates, without using a satellite server, here: https://access.redhat.com/solutions/23016 • The article covers RHEL5 through 8. 57 of 617 First Alternative 2021 Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 58 Local CentOS 8 repository server setup using a web server • To set up a system as a local repository server you can provide access via: ♦ Local directory access (e.g. NFS mount) ♦ Web server (HTTP) ♦ FTP (File Transfer Protocol) • We will look first at HTTP, followed by local directory access. • The repos we will create are the updated variety. • 1. Install and enable the Apache web server. $ sudo yum install httpd $ sudo systemctl enable httpd $ sudo systemctl start httpd ♦ Ignore any warning messages. • 2. Create directories on the server for the BaseOS, Appstream and Extras repos within the web site directory space: $ sudo mkdir -p /var/www/html/centos/8/BaseOS $ sudo mkdir /var/www/html/centos/8/AppStream $ sudo mkdir /var/www/html/centos/8/Extras • 3. Ensure internet access is enabled, then create a BaseOS repo as follows: 58 of 617 First Alternative 2021 59 $ sudo rsync -avrt \ rsync://rsync.mirrorservice.org/mirror.centos.org/8\ BaseOS/x86_64/os/ \ /var/www/html/centos/8/BaseOS/ ---------------------------------------------------------------------------- Welcome to the University of Kent's UK Mirror Service. More information can be found at our web site: http://www.mirrorservice.org/ Please send comments or questions to [email protected]. ---------------------------------------------------------------------------- receiving file list ... done ./ .discinfo .treeinfo EULA GPL extra_files.json media.repo EFI/ etc. • Remember that the repos we are copying are the updated versions, so we can run the same rsync commands periodically to keep our local repos up-to-date. • You may consider using the reposync utility which will also download the repositories for you. • reposync is part of the yum-utils package, and the reposync man page has examples of use. ♦ rsync.mirrorservice.org is the rsync server on the internet, 59 of 617 First Alternative 2021 Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 60 which may need to be changed depending on your location.
Load more

Recommended publications
  • Red Hat Enterprise Linux 8 Installing, Managing, and Removing User-Space Components
    Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Last Updated: 2021-06-25 Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Legal Notice Copyright © 2021 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, 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]
  • Using the Mysql Yum Repository Abstract
    Using the MySQL Yum Repository Abstract This document provides some basic instructions for using the MySQL Yum Repository to install and upgrade MySQL. It is excerpted from the MySQL 5.6 Reference Manual. For legal information, see the Legal Notices. For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users. Document generated on: 2021-09-23 (revision: 70881) Table of Contents Preface and Legal Notices ............................................................................................................ v 1 Installing MySQL on Linux Using the MySQL Yum Repository ..................................................... 1 2 Replacing a Third-Party Distribution of MySQL Using the MySQL Yum Repository ........................ 5 3 Upgrading MySQL with the MySQL Yum Repository ................................................................... 9 iii iv Preface and Legal Notices This document provides some basic instructions for using the MySQL Yum Repository to install and upgrade MySQL. It is excerpted from the MySQL 5.6 Reference Manual. Licensing information—MySQL 5.6. This product may include third-party software, used under license. If you are using a Commercial release of MySQL 5.6, see the MySQL 5.6 Commercial Release License Information User Manual for licensing information, including licensing information relating to third-party software that may be included in this Commercial release. If you are using a Community release of MySQL 5.6, see the MySQL 5.6 Community Release License Information User Manual for licensing information, including licensing information relating to third-party software that may be included in this Community release. Licensing information—MySQL NDB Cluster 7.3. This product may include third-party software, used under license. If you are using a Commercial release of NDB Cluster 7.3, see the MySQL NDB Cluster 7.3 Commercial Release License Information User Manual for licensing information relating to third-party software that may be included in this Commercial release.
    [Show full text]
  • Managing Software with Yum
    Fedora Core 4 Managing software with yum Stuart Ellis Edited by Paul W. Frields Copyright © 2005 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. All other trademarks are the property of their respective owners. 1. Introduction ............................................................................................................................. 2 1.1. Purpose ....................................................................................................................... 2 1.2. Audience ....................................................................................................................
    [Show full text]
  • Red Hat Developer Toolset 9 User Guide
    Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Last Updated: 2020-08-07 Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Zuzana Zoubková Red Hat Customer Content Services Olga Tikhomirova Red Hat Customer Content Services [email protected] Supriya Takkhi Red Hat Customer Content Services Jaromír Hradílek Red Hat Customer Content Services Matt Newsome Red Hat Software Engineering Robert Krátký Red Hat Customer Content Services Vladimír Slávik Red Hat Customer Content Services Legal Notice Copyright © 2020 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, 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.
    [Show full text]
  • CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2
    Topics 1. The Problem of Software Installation 2. Package Management Systems CIT 470: Advanced Network and 3. Using RPM System Administration 4. Finding RPMs Package Management 5. Building RPMs CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2 Software Installation What’s the problem? 1. Customization What prerequisites does your software have? Select options like language. What prereqs do your prereq packages have? Select file set. How do you handle conflicts? What if two programs install/modify same file? 2. Install new files in appropriate locations. Does your install work on every type of computer? 3. Modify existing configuration files. How do you handle upgrades? 4. Make software available to user. What if user has customized configuration? Shell configuration (PATH, etc.) What if ownerships/permissions have changed? GUI configuration (menu, icons, etc.) What if user needs old and new versions? How do you uninstall software? CIT 470: Advanced Network and System Administration Slide #3 CIT 470: Advanced Network and System Administration Slide #4 Package Manager Features UNIX Package Management Systems • Build management. deb: Debian system uses dpkg and APT. • Dependency tracking. pkgadd: Solaris packaging system. • Querying. portage: Gentoo uses with emerge. • Reversibility. ports: BSD ports system. • Verification. RPM: Redhat packaging system. • Version control. tgz: Tarballs used by Slackware. CIT 470: Advanced Network and System Administration Slide #5 CIT 470: Advanced Network and System Administration Slide #6 1 RPM RPM Package Names RPM Package Manager <name>-<version>-<release>.<arch>.rpm – Originally stood for Red Hat Package Manager – Came with Red Hat Linux 2.0 in 1995.
    [Show full text]
  • VNC Instruction for GNU/Linux
    VNC Instruction for GNU/Linux 1. Install “ TigerVNC Viewer ”. You can get it with package manager command line as below: • On Ubuntu / Mint / Debian sudo apt-get install vncviewer • On Fedora / CentOS / Scientific Linux sudo yum install tigervnc • On Arch Linux sudo pacman -Syy tigervnc 2. Open “Terminal”, and ssh to “csevnc.cse.csusb.edu” using the following command: ssh -L 5900:localhost:5900 <YourCoyoteID>@csevnc.cse.csusb.edu (Note: Replace “<YourCoyoteID>” with your Coyote ID) 3. If this is the first time you remote access to this server, you may see the following information. When you see that, just type “yes” and hit “Enter”. 4. Type in your Coyote password and hit Enter. 5. Open TigerVNC Viewer. Here are 2 ways to open it: ● From Application: Click on the icon shown in the applications list. ● From command line: Keep the current terminal tab from Step 2 open, and open a new tab or a new terminal window. Then, run command vncviewer in the new tab or window. CSUSB School of CSE 01/19/2018 hn 6. In the pop-up window, type in “localhost”, then hit Enter (or click on “Connect” ). (The pop-up window may vary depending on the distribution of Linux system) 7. Now you should see the GUI of the remote computer. Login with your Coyote ID as Username and Coyote password as Password. 8. Once you have done your work, close the VNC viewer window, and run command exit in the terminal tab from Step 2 to log out from the remote server. CSUSB School of CSE 01/19/2018 hn.
    [Show full text]
  • Gestione Del Software Installazione E Gestione Repository
    Gestione del Software Installazione e gestione repository Niccolò Izzo [email protected] Benvenuti Qui trovate queste slide software.izzo.ovh Fate tante domande! Oggi vedremo come Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Oggi vedremo come Installare il Software Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Oggi vedremo come Installare il Software Gestire i repository Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Compilazione Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Compilazione Pro Codice ottimizzato e personalizzato Possibile il controllo sui sorgenti Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Compilazione Pro Codice ottimizzato e personalizzato Possibile il controllo sui sorgenti Contro Lenta per software complessi Non tiene traccia del software Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Compilazione Pro Codice ottimizzato e personalizzato Possibile il controllo sui sorgenti Contro Lenta per software complessi Non tiene traccia del software Anche se in alcuni casi è l'unica possibilità. Niccolò Izzo Corsi Linux Avanzati 2015 - POuL I pacchetti precompilati Niccolò Izzo Corsi Linux Avanzati 2015 - POuL I pacchetti precompilati Principalmente sono due: .rpm per RHEL, Fedora e le loro derivate .deb per Debian, Ubuntu e le loro derivate Niccolò Izzo Corsi Linux Avanzati 2015 - POuL I pacchetti precompilati Principalmente sono due: .rpm per RHEL, Fedora e le loro derivate .deb per Debian, Ubuntu e le loro derivate Ma esistono anche .tgz per Slackware .pkg.tar.xz per Arch Linux Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Le operazioni base Per installare un pacchetto Debian based # dpkg -i pacchetto.deb RPM based # rpm -i pacchetto.rpm Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Le operazioni base Per rimuovere un pacchetto Debian based # dpkg -r pacchetto RPM based # rpm -r pacchetto Niccolò Izzo Corsi Linux Avanzati 2015 - POuL Manca ancora qualcosa..
    [Show full text]
  • Hortonworks Data Platform Apache Solr Search Installation (May 17, 2018)
    Hortonworks Data Platform Apache Solr Search Installation (May 17, 2018) docs.cloudera.com Hortonworks Data Platform May 17, 2018 Hortonworks Data Platform: Apache Solr Search Installation Copyright © 2012-2018 Hortonworks, Inc. Some rights reserved. The Hortonworks Data Platform, powered by Apache Hadoop, is a massively scalable and 100% open source platform for storing, processing and analyzing large volumes of data. It is designed to deal with data from many sources and formats in a very quick, easy and cost-effective manner. The Hortonworks Data Platform consists of the essential set of Apache Hadoop projects including MapReduce, Hadoop Distributed File System (HDFS), HCatalog, Pig, Hive, HBase, ZooKeeper and Ambari. Hortonworks is the major contributor of code and patches to many of these projects. These projects have been integrated and tested as part of the Hortonworks Data Platform release process and installation and configuration tools have also been included. Unlike other providers of platforms built using Apache Hadoop, Hortonworks contributes 100% of our code back to the Apache Software Foundation. The Hortonworks Data Platform is Apache-licensed and completely open source. We sell only expert technical support, training and partner-enablement services. All of our technology is, and will remain free and open source. Please visit the Hortonworks Data Platform page for more information on Hortonworks technology. For more information on Hortonworks services, please visit either the Support or Training page. Feel free to Contact Us directly to discuss your specific needs. Except where otherwise noted, this document is licensed under Creative Commons Attribution ShareAlike 4.0 License. http://creativecommons.org/licenses/by-sa/4.0/legalcode ii Hortonworks Data Platform May 17, 2018 Table of Contents 1.
    [Show full text]
  • Basic Linux & Package Management
    Basic Linux & Package Management Original slides from GTFO Security outline ● Linux ○ What it is? ○ Commands ○ Filesystem / Shell ○ Package Management Services run on Linux ● mail ● dns ● web ● central authentication ● router ● database ● virtual machines ● voip ● anything Linux ● The core of many computers and devices ○ Android ○ Ubuntu Desktop ○ Red Hat / Fedora ● Linux is a term to describe a set of tools ○ Command line programs ○ Programs such as email and websites ○ Shell scripts ○ Free and Open Source approach ○ Layout of filesystem Linux ● Linux has distributions/variants ○ Debian/RedHat/SUSE ■ Ubuntu - Debian based ■ Mint - Debian based ■ Fedora - RedHat based ■ CentOS - RedHat based ■ Trisquel - Debian based basic commands man top pwd chmod, chown, cd, ls, cp, mv, rm chgrp mkdir ps cat, less netstat vi, nano, emacs who grep, lsof which sudo, su passwd cat $cat filename #write the file to the screen $cat > filename #write input to a file $echo hi | cat #take input from a bash pipe $echo hi | cat | cat grep $cat filename | grep "hello" $cat filename | grep -v "hello" $cat /usr/share/dict/words | grep -B 5 base $cat /usr/share/dict/words | grep -A 5 base grep $head prints out the top of a file $tail prints out the bottom of a file $more shows a file a page at a time $less same as more but lets to scroll up moving files $mv filename1 filename2 same renaming $cp filename1 filename2 two files exist now $cat filename1 > filename2 directories $mkdir directory1 creates a folder $cd directory1 moves into a new folder $cd .. moves out of
    [Show full text]
  • Building Linux Distribution Packages with Docker
    Building Linux distribution packages with Docker Bruno Cornec HPE EMEA EG Presales Strategist WW Linux Community Lead, HPE Open Source Pro ession !"#0 – October 20'( #$#A Custo%ers Solution Inno&ation Center Grenoble Ma)ing the ne+ style o ,T a reality # o » './ years o success, +orld +ide programs, including Cloud Center o Excellence, C Big Data Center o Excellence, Open Source Solutions ,nitiati!e, 0,SC to HP Intel Architecture Migrations, N ! Center o Excellence, EMEA Networking Customer 1isit Center and more » C Complete ,- 23$$/ systems, 4$$$/ net+ork ports, .$$/ -B storage5 o » Port olio o 3$/ ready to demo solutions +it* access to our ecosystem o Partners P » Complete test 6 !alidation en!ironment » Strategic partners*ip +it* Intel, '.7year long standing colla&oration » Strategic partners*ip +it* "ed Hat 87year colla&oration 2OSS,5 o % » e A uni9ue proo point in t*e industry +it* a pro!en ser!ice o:ering d e & i L Mission: Accelerate t*e adoption o new and inno!ati!e solutions &y creating simple and re+arding end7to7end customer experiences t*at &ene it our customers and partners, in a p o compelling and engaging colla&orative en!ironment. h s k …more information available at http://www.hpintelco.net r o ' Introducing m(sel) ● So t+are engineering and <nices since '=>>; – Mostly Con iguration Management Systems 2CMS5, Build systems, 9uality tools, on multiple commercial <nix systems – ?isco!ered Open Source 6 Linux 2OSL5 6 made irst contri&utions in '==4 – @ull time on OSL since '==5, irst as HP reseller t*en AHP ● Currently; –
    [Show full text]
  • A Smart Way to Manage Packages in Yocto Project
    A Smart Way to Manage Packages in Yocto Project Mar 11th, 2016 Fan Xin, Fujitsu Computer Technologies Limited 1378ka02 Copyright 2016 FUJITSU COMPUTER TECHNOLOGIES LIMITED whoami Fan Xin, Fujitsu Computer Technologies Ltd. Embedded Linux Developer In-House Embedded Linux Distributor of Fujitsu Our Distribution includes LTSI Kernel and is built with Yocto Project Our Distribution is used for IVI, Server System Controller, Storage System, Network Equipment, Printer, etc. IVI：In-Vehicle Infotainment 1 Copyright 2016 FUJITSU COMPUTER TECHNOLOGIES LIMITED Fujitsu’s contribution for Yocto Project meta-openembedded.git top contributors by employer (2015-01-01 to 2015-12-31) None 625 (46.1%) Wind River 309 (22.8%) Fujitsu 160 (11.8%) Intel 82 (6.0%) Mentor Graphics 34 (2.5%) O.S. Systems 24 (1.8%) National Instruments 19 (1.4%) MontaVista 16 (1.2%) OpenDreambox 12 (0.9%) Freescale 9 (0.7%) Linaro 8 (0.6%) ENEA AB 5 (0.4%) Leica 5 (0.4%) Aker Security Solutions 4 (0.3%) BMW 3 (0.2%) 2 Copyright 2016 FUJITSU COMPUTER TECHNOLOGIES LIMITED Agenda Package Manager Comparison Package Management Problem Analysis in Yocto Project Introduction of Smart Package Manager Fujitsu’s Contribution and Next Step 3 Copyright 2016 FUJITSU COMPUTER TECHNOLOGIES LIMITED Package Manager Comparison 4 Copyright 2016 FUJITSU COMPUTER TECHNOLOGIES LIMITED Package Manager Package Manager A collection of software tools that automates the process of installing, upgrading, configuring, and removing computer programs Deals with packages, distributions of software
    [Show full text]
  • Package Management Security
    Package Management Security Justin Cappos, Justin Samuel, Scott Baker, John H. Hartman University of Arizona Computer Science Department {justin, jsamuel, bakers, jhh}@cs.arizona.edu Abstract Package management is the task of determining which packages should be installed on a host and then downloading and installing those packages. This paper examines the popular package managers APT and YUM and presents nine feasible attacks on them. There are attacks that install malicious packages, deny users package updates, or cause the host to crash. This work identifies three rules of package management security: don’t trust the repository, the trusted entity with the most information should be the one who signs, and don’t install untrusted packages. The violation of these rules leads to the described vulnerabilities. Unfortunately, many of the flaws are architectural in nature, so repair requires more than patches to APT and YUM. While the rules of package management security argue that the design of existing package managers is insufficient, they do not prescribe how to provide security. This led to the development of three de- sign principles for building a secure package manager: selective trust delegation, customized repository views, and explicitly treating the repository as untrusted. These principles were used to construct a pack- age manager Stork which is not vulnerable to the attacks identified for YUM and APT. Stork has been in use for four years and has managed over half a million clients. 1 Introduction Package managers are a popular way to distribute software (bundled into archives called packages) for modern operating systems [4, 11, 37].
    [Show full text]