DOCSLIB.ORG

Tivoli Provisioning Manager for OS Deployment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Tivoli Provisioning Manager for OS Deployment User's Guide Tivoli Provisioning Manager for OS Deployment User's Guide ii Tivoli Provisioning Manager for OS Deployment: User's Guide Contents Chapter 1. Defining targets ......1 Scheduling the application of software modules Adding targets..............2 for Windows operating systems ......64 Detecting targets automatically .......2 Working with hardware configurations .....65 Adding targets to the Target Monitor manually . 3 Setting up your environment .......66 Importing and exporting targets lists .....3 Hardware configuration objects and tasks . 67 Configuring new targets .........5 RAID and Fiber Channel hardware capture. 68 Changing the default administrative group . 5 Creating a hardware environment ......68 Requirements for VMware targets .......6 Creating a hardware configuration object . 75 Injecting drivers on WinPE 3.0 to deploy Windows Creating a hardware capture configuration . 75 XP guests ..............7 Capturing hardware information using templates 76 Booting non x86 and non x86-64 targets .....8 Capturing hardware information once ....77 Booting pSeries targets on the OS deployment Task templates for Windows operating systems . 77 server................8 Customizing a screen layout........78 Booting CellBlades targets on the OS deployment Creating and editing deployment schemes . 79 server................9 Creating media for deployment for Windows Booting SPARC targets on the OS deployment operating systems ............83 server................9 Creating an OS deployment USB drive with the Organizing targets ............11 wizard ...............84 Configuring targets ............12 Creating an OS deployment USB drive with Configuring multiple targets........12 command lines ............85 Configuring targets for fully unattended OS Creating OS deployment CD and DVD ....86 deployments .............12 Deploying Windows operating systems .....89 Setting partition sizes on the targets .....13 The deployment process .........89 Deployment requirements ........90 Chapter 2. Provisioning Windows Starting a one-time deployment ......91 operating systems on x86 and x86-64 Deploying a hardware configuration .....93 Redeploying .............93 targets ...............15 Monitoring deployments ........101 Overview of WinPE deployment engines ....15 Bindings created during deployment ....104 Windows Automated Installation Kit .....16 Creating a WinPE 3.0 deployment engine . 17 Chapter 3. Provisioning Linux Editing the information of a WinPE deployment operating systems on x86 and x86-64 engine ...............19 Adding matching target models to a WinPE targets ..............105 deployment engine ...........19 System profiles for Linux operating systems . 105 Binding drivers to a WinPE deployment engine 20 Creating system profiles .........105 System profiles for Windows operating systems . 24 Organizing and editing system profiles ....108 BitLocker compatibility .........24 Browsing partition files .........109 Creating system profiles .........25 Changing the partition layout in Linux ....109 Organizing and editing system profiles ....33 Updating device mapping ........111 Updating a system profile with a Language Pack OS configurations and fixed common or a HotFix .............34 parameters .............111 Browsing partition files .........34 Software modules for Linux operating systems . 113 Changing the partition layout in Windows . 35 Creating software modules ........114 Updating device mapping ........36 Editing software modules ........117 OS configurations and fixed common parameters 37 Keeping command lines confidential ....117 Binding drivers to a Windows system profile . 39 Keyword substitution..........118 Restoring a system profile manually .....42 Customizing the software page ......120 Software modules for Windows operating systems 43 OS configuration and software bindings . 120 WinPE and its uses ...........43 Scheduling the application of software modules Creating software modules ........45 for Linux operating systems .......123 Editing software modules ........58 Working with hardware configurations .....124 Keeping command lines confidential .....58 Setting up your environment .......125 Keyword substitution ..........59 Hardware configuration objects and tasks . 126 Customizing the software page .......61 RAID and Fiber Channel hardware capture . 127 OS configuration and software bindings ....61 Creating a hardware environment .....127 © Copyright IBM Corp. 2006, 2010 iii Creating a hardware configuration object . 134 Deploying Linux on PowerPC .......211 Creating a hardware capture configuration . 134 Provisioning Solaris on SPARC targets .....216 Capturing hardware information using System profiles for Solaris operating systems 216 templates..............135 Software modules for Solaris operating systems 221 Capturing hardware information once ....135 Task templates for Solaris operating systems 231 Task templates for Linux operating systems . 136 Deploying Solaris ...........237 Customizing a screen layout .......137 Provisioning AIX on PowerPC targets .....243 Creating and editing deployment schemes. 137 System profiles for AIX operating systems. 243 Creating media for deployment for Linux Task templates for AIX operating systems . 246 operating systems ............142 Deploying AIX ............253 Creating an OS deployment USB drive with command lines ............143 Chapter 6. Multiple server architecture 259 Creating an OS deployment USB drive with Server roles ..............259 command lines ............144 OS deployment server replication ......261 Creating OS deployment CD and DVD ....145 Replicating OS deployment servers with a Deploying Linux ............148 schedule ..............264 The deployment process.........148 Replicating an OS deployment server once Deployment requirements ........149 manually ..............264 Starting a one-time deployment ......150 Replicating offline with the web interface Deploying a hardware configuration ....151 extension ..............265 Redeploying.............152 Replicating one time in command line ....267 Monitoring deployments ........159 Server replication status and logs......268 Bindings created during deployment ....163 Switching from an ODBC to a JDBC gateway 269 Removing an OS deployment server from the Chapter 4. Provisioning VMWare ESX hierarchy ...............269 Server on x86 and x86-64 targets . 165 System profiles for VMWare operating systems . 165 Chapter 7. Security .........271 Creating an unattended setup system profile for Security roles and access to the Web interface . 271 VMWare..............166 Creating an HTTP authentication domain . 272 Organizing and editing system profiles ....166 Creating security roles .........272 Browsing partition files .........167 Backups of server files ..........273 Changing the partition layout in VMWare . 167 Importing and exporting RAD files .....273 Updating device mapping ........168 Importing and exporting targets lists ....275 OS configurations and fixed common Exporting and loading configurations ....276 parameters .............169 Fault tolerance .............277 Task templates for VMWare operating systems . 170 Fault tolerance at the DHCP level .....277 Customizing a screen layout .......171 Fault tolerance at the Tivoli Provisioning Creating and editing deployment schemes. 172 Manager for OS Deployment level .....278 Creating media for deployment for VMWare . 176 Network security constraints ........279 Creating an OS deployment USB drive with the Avoiding new security breaches .......280 wizard ..............177 Rogue PXE servers ..........280 Creating an OS deployment USB drive with Unwanted target computers .......281 command lines ............178 Security issues and the web interface .....281 Creating OS deployment CD and DVD ....179 Deploying VMWare ...........182 Chapter 8. Booting targets without The deployment process.........182 using PXE .............283 Deployment requirements ........183 Creating network boot USB drive with the wizard 283 Starting a one-time deployment ......184 Creating a network boot CD or DVD with the Monitoring deployments ........185 wizard ...............284 Bindings created during deployment ....188 Creating an original WinPE 3.0 network boot CD or DVD with the wizard..........285 Chapter 5. Provisioning non x86 and Using a network boot CD ........286 non x86-64 targets .........189 Creating a network boot USB drive with command Provisioning Linux on PowerPC and Cell targets 189 lines ................287 System profiles for Linux operating systems on Creating a network boot CD or DVD with PowerPC ..............189 command lines .............289 Software modules for Linux operating systems Booting on the network when the target is missing on PowerPC.............195 network drivers ............290 Task templates for Linux operating systems on PowerPC ..............205 Chapter 9. Tools ..........293 iv Tivoli Provisioning Manager for OS Deployment: User's Guide Erasing hard disk content .........293 Restoring user settings ..........295 Software snapshots ...........293 Limitation of the technology .......293 Chapter 11. Glossary ........297 Restoring software snapshots .......294 Chapter 12. Notices.........303 Chapter 10. Migrating users .....295 Capturing user settings ..........295 Contents v vi Tivoli Provisioning Manager for OS Deployment: User's Guide Chapter 1. Defining targets Targets are computers known to the OS deployment server. This includes the OS deployment servers themselves, the
Recommended publications
  • Operating System Boot from Fully Encrypted Device

    Operating System Boot from Fully Encrypted Device

    Masaryk University Faculty of Informatics Operating system boot from fully encrypted device Bachelor’s Thesis Daniel Chromik Brno, Fall 2016 Replace this page with a copy of the official signed thesis assignment and the copy of the Statement of an Author. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Daniel Chromik Advisor: ing. Milan Brož i Acknowledgement I would like to thank my advisor, Ing. Milan Brož, for his guidance and his patience of a saint. Another round of thanks I would like to send towards my family and friends for their support. ii Abstract The goal of this work is description of existing solutions for boot- ing Linux and Windows from fully encrypted devices with Secure Boot. Before that, though, early boot process and bootloaders are de- scribed. A simple Linux distribution is then set up to boot from a fully encrypted device. And lastly, existing Windows encryption solutions are described. iii Keywords boot process, Linux, Windows, disk encryption, GRUB 2, LUKS iv Contents 1 Introduction ............................1 1.1 Thesis goals ..........................1 1.2 Thesis structure ........................2 2 Boot Process Description ....................3 2.1 Early Boot Process ......................3 2.2 Firmware interfaces ......................4 2.2.1 BIOS – Basic Input/Output System . .4 2.2.2 UEFI – Unified Extended Firmware Interface .5 2.3 Partitioning tables ......................5 2.3.1 MBR – Master Boot Record .
  • Not for Sale Not for Sale

    Not for Sale Not for Sale

    chapter 3 Installing Fedora Now comes the moment of truth. You’ve done the homework, figured out how you want to install your copy of Fedora, and you’re ready to go. This chapter won’t disappoint you. Its sole goal is to walk you through the installation process using the Anaconda graphical installer. Along the way, you will: ■ Discover how to explore Fedora—without installing it. ■ Choose which option will be best for you, installing Fedora alone or along- side another operating system. ■ Journey step by step through the installation process. ■ Create one or more users for your Fedora machine. Try Before You Buy © Cengage Learning. All rights reserved. No distribution allowed without express authorization. This section may leave you scratching your head and wondering why you just went through all of the preparation in Chapter 2. Be patient, there’s a method to this madness. All spins of Fedora are currently available to users as a LiveCD version. “LiveCD” is the label for operating systems that can be booted and run right from the CD itself—without installing on your computer’s hard drive. 41 Game Developing GWX Not For Sale Not For Sale 42 Chapter 3 ■ Installing Fedora This means that when you insert your Fedora CD into the disc drive and restart your computer, Fedora will automatically begin running on your computer without putting on any new files or touching pre-existing data on your machine. Fedora just starts up and runs. So why, you ask, should I bother installing Fedora at all? I can just run it from the CD.
  • White Paper: Indestructible Firewall in a Box V1.0 Nick Mccubbins

    White Paper: Indestructible Firewall in a Box V1.0 Nick Mccubbins

    White Paper: Indestructible Firewall In A Box v1.0 Nick McCubbins 1.1 Credits • Nathan Yawn ([email protected]) 1.2 Acknowledgements • Firewall-HOWTO • Linux Router Project • LEM 1.3 Revision History • Version 1.0 First public release 1.4 Feedback • Send all information and/or criticisms to [email protected] 1.5 Distribution Policy 2 Abstract In this document, the procedure for creating an embedded firewall whose root filesystem is loaded from a flash disk and then executed from a RAMdisk will be illustrated. A machine such as this has uses in many environments, from corporate internet access to sharing of a cable modem or xDSL connection among many computers. It has the advantages of being very light and fast, being impervious to filesystem corruption due to power loss, and being largely impervious to malicious crackers. The type of firewall illustrated herein is a simple packet-filtering, masquerading setup. Facilities for this already exist in the Linux kernel, keeping the system's memory footprint small. As such the device lends itself to embedding very well. For a more detailed description of firewall particulars, see the Linux Firewall-HOWTO. 3 Equipment This project has minimal hardware requirements. An excellent configuration consists of: For a 100-baseT network: • SBC-554 Pentium SBC with PISA bus and on-board PCI NIC (http://www.emacinc.com/pc.htm#pentiumsbc), approx. $373 • PISA backplane, chassis, power supply (http://www.emacinc.com/sbcpc_addons/mbpc641.htm), approx. $305 • Second PCI NIC • 32 MB RAM • 4 MB M-Systems Flash Disk (minimum), approx. $45 For a 10-baseT network: • EMAC's Standard Server-in-a-Box product (http://www.emacinc.com/server_in_a_box.htm), approx.
  • Chapter 3. Booting Operating Systems

    Chapter 3. Booting Operating Systems

    Chapter 3. Booting Operating Systems Abstract: Chapter 3 provides a complete coverage on operating systems booting. It explains the booting principle and the booting sequence of various kinds of bootable devices. These include booting from floppy disk, hard disk, CDROM and USB drives. Instead of writing a customized booter to boot up only MTX, it shows how to develop booter programs to boot up real operating systems, such as Linux, from a variety of bootable devices. In particular, it shows how to boot up generic Linux bzImage kernels with initial ramdisk support. It is shown that the hard disk and CDROM booters developed in this book are comparable to GRUB and isolinux in performance. In addition, it demonstrates the booter programs by sample systems. 3.1. Booting Booting, which is short for bootstrap, refers to the process of loading an operating system image into computer memory and starting up the operating system. As such, it is the first step to run an operating system. Despite its importance and widespread interests among computer users, the subject of booting is rarely discussed in operating system books. Information on booting are usually scattered and, in most cases, incomplete. A systematic treatment of the booting process has been lacking. The purpose of this chapter is to try to fill this void. In this chapter, we shall discuss the booting principle and show how to write booter programs to boot up real operating systems. As one might expect, the booting process is highly machine dependent. To be more specific, we shall only consider the booting process of Intel x86 based PCs.
  • Release Notes for Fedora 22

    Release Notes for Fedora 22

    Fedora 22 Release Notes Release Notes for Fedora 22 Edited by The Fedora Docs Team Copyright © 2015 Fedora Project Contributors. 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.
  • Red Hat Enterprise Linux 8 Security Hardening

    Red Hat Enterprise Linux 8 Security Hardening

    Red Hat Enterprise Linux 8 Security hardening Securing Red Hat Enterprise Linux 8 Last Updated: 2021-09-06 Red Hat Enterprise Linux 8 Security hardening Securing 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. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
  • Network Boot and Exotic Root HOWTO

    Network Boot and Exotic Root HOWTO

    Network Boot and Exotic Root HOWTO Brieuc Jeunhomme frtest [email protected] Logilab S.A. Revision History Revision 0.3 2002−04−28 Revised by: bej Many feedback inclusions, added links to several projects Revision 0.2.2 2001−12−08 Revised by: dcm Licensed GFDL Revision 0.2.1 2001−05−21 Revised by: logilab Fixed bibliography and artheader Revision 0.2 2001−05−19 Revised by: bej Many improvements and included Ken Yap's feedback. Revision 0.1.1 2001−04−09 Revised by: logilab First public draft. Revision 0.1 2000−12−09 Revised by: bej Initial draft. This document explains how to quickly setup a linux server to provide what diskless linux clients require to get up and running, using an IP network. It includes data and partly rewritten text from the Diskless−HOWTO, the Diskless−root−NFS−HOWTO, the linux kernel documentation, the etherboot project's documentation, the linux terminal server project's homepage, and the author's personal experience, acquired when working for Logilab. Eventually this document may end up deprecating the Diskless−HOWTO and Diskless−root−NFS−HOWTO. Please note that you'll also find useful information in the From−PowerUp−to−bash−prompt−HOWTO and the Thin−Client−HOWTO, and the Claus−Justus Heine's page about NFS swapping. Network Boot and Exotic Root HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. What is this all about?.......................................................................................................................1 1.2. Thanks...............................................................................................................................................1 1.3. Diskless booting advocacy................................................................................................................1 1.3.1. Buying is cheaper than building.......................................................................................1 1.3.2.
  • Spacewalk 2.4 for Oracle® Linux Concepts and Getting Started Guide

    Spacewalk 2.4 for Oracle® Linux Concepts and Getting Started Guide

    Spacewalk 2.4 for Oracle® Linux Concepts and Getting Started Guide E71709-03 January 2017 Oracle Legal Notices Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 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 installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
  • Sbadmin for Linux System Recovery Guide Is a Supplement to the Sbadmin User Guide, Providing Details on Reinstalling a Linux System from a Sbadmin System Backup

    Sbadmin for Linux System Recovery Guide Is a Supplement to the Sbadmin User Guide, Providing Details on Reinstalling a Linux System from a Sbadmin System Backup

    Linux System Recovery Guide Version 8.2 Trademarks and Copyrights © Copyright Storix, Inc. 1999-2021 SBAdmin is a registered trademark of Storix, Inc. SBAdmin is a trademark of Storix, Inc in the USA and other countries Intel is a registered trademark of Intel, Inc. Linux is a registered trademark of Linus Torvalds. Intel, Pentium, IA32, Itanium, Celeron and IA64 are registered trademarks of Intel Corporation. AMD, Opteron, and Athlon are registered trademarks of Advanced Micro Devices. HP Integrity servers are registered trademarks of Hewlett-Packard Development Company. Publicly Available Software This product either includes or is developed using source code that is publicly available: AESCrypt* Rijndael and Cipher Block Feedback Copyright 1999, 2000 Enhanced Software Technologies Inc. mode (CFB-128) encryption/decryption http://aescrypt.sourceforge.net/ algorithms BusyBox Single executable containing tiny Copyright 1989, 1991 Free Software Foundation, Inc. versions of common UNIX utilities http://busybox.net/cgi-bin/cvsweb/busybox/ LILO LInux boot Loader Copyright 1999-2003 John Coffman. Copyright 1992-1998 Werner Almesberger. http://freshmeat.net/projects/lilo/ Tcl Open source scripting language Copyright Regents of the University of California, Sun Microsystems, Inc. http://tcl.sourceforge.net Tk Tk graphics toolkit Copyright Regents of the University of California, Sun Microsystems, Inc. http://tcl.sourceforge.net DropBear A Smallish SSH 2 Server and Client Copyright 2002, 2003 Matt Johnston http://www.matt.ucc.asn.au/dropbear/dropbear.html GRUB Grand Unified Bootloader (GNU GRUB) Copyright 1989, 1991 Free Software Foundation, Inc. http://www.gnu.org/software/grub/grub.html Lighttpd Secure, fast, compliant and flexible Copyright 2004 Jan Kneschkle, incremental web-server http://www.lighttpd.net OpenSSL Toolkit implementing Secure Socket Copyright 1998-2008 The OpenSSL Project Layer Copyright 1995-1998 Eric A.
  • Latest/Conf Ref.Html#files‘

    Latest/Conf Ref.Html#files‘

    dnf-plugins-extras Documentation Release 4.0.15-1 Tim Lauridsen Jul 19, 2021 Contents 1 DNF kickstart Plugin 3 2 Extras DNF Plugins Release Notes5 3 DNF rpmconf Plugin 15 4 DNF showvars Plugin 17 5 DNF snapper Plugin 19 6 DNF system-upgrade Plugin 21 7 DNF torproxy Plugin 25 8 DNF tracer Plugin 27 9 See Also 29 10 Indices and tables 31 i ii dnf-plugins-extras Documentation, Release 4.0.15-1 This documents extras plugins of DNF: Contents 1 dnf-plugins-extras Documentation, Release 4.0.15-1 2 Contents CHAPTER 1 DNF kickstart Plugin Install packages according to Anaconda kickstart file. 1.1 Synopsis dnf kickstart <ks-file> 1.2 Arguments <ks-file> Path to the kickstart file. 1.3 Examples dnf kickstart mykickstart.ks Install the packages defined in mykickstart.ks. 1.4 See Also • Anaconda Kickstart file documentation 3 dnf-plugins-extras Documentation, Release 4.0.15-1 4 Chapter 1. DNF kickstart Plugin CHAPTER 2 Extras DNF Plugins Release Notes Contents • Extras DNF Plugins Release Notes – 4.0.15 Release Notes – 4.0.14 Release Notes – 4.0.13 Release Notes – 4.0.12 Release Notes – 4.0.10 Release Notes – 4.0.9 Release Notes – 4.0.8 Release Notes – 4.0.7 Release Notes – 4.0.6 Release Notes – 4.0.5 Release Notes – 4.0.4 Release Notes – 4.0.2 Release Notes – 4.0.1 Release Notes – 4.0.0 Release Notes – 3.0.2 Release Notes – 3.0.1 Release Notes – 3.0.0 Release Notes – 2.0.5 Release Notes 5 dnf-plugins-extras Documentation, Release 4.0.15-1 – 2.0.4 Release Notes – 2.0.3 Release Notes – 2.0.2 Release Notes – 2.0.1 Release Notes – 2.0.0 Release Notes – 0.10.0
  • Foot Prints Feel the Freedom of Fedora!

    Foot Prints Feel the Freedom of Fedora!

    The Fedora Project: Foot Prints Feel The Freedom of Fedora! RRaahhuull SSuunnddaarraamm SSuunnddaarraamm@@ffeeddoorraapprroojjeecctt..oorrgg FFrreeee ((aass iinn ssppeeeecchh aanndd bbeeeerr)) AAddvviiccee 101011:: KKeeeepp iitt iinntteerraaccttiivvee!! Credit: Based on previous Fedora presentations from Red Hat and various community members. Using the age old wisdom and Indian, Free software tradition of standing on the shoulders of giants. Who the heck is Rahul? ( my favorite part of this presentation) ✔ Self elected Fedora project monkey and noisemaker ✔ Fedora Project Board Member ✔ Fedora Ambassadors steering committee member. ✔ Fedora Ambassador for India.. ✔ Editor for Fedora weekly reports. ✔ Fedora Websites, Documentation and Bug Triaging projects volunteer and miscellaneous few grunt work. Agenda ● Red Hat Linux to Fedora & RHEL - Why? ● What is Fedora ? ● What is the Fedora Project ? ● Who is behind the Fedora Project ? ● Primary Principles. ● What are the Fedora projects? ● Features, Future – Fedora Core 5 ... The beginning: Red Hat Linux 1994-2003 ● Released about every 6 months ● More stable “ .2” releases about every 18 months ● Rapid innovation ● Problems with retail channel sales model ● Impossible to support long-term ● Community Participation: ● Upstream Projects ● Beta Team / Bug Reporting The big split: Fedora and RHEL Red Hat had two separate, irreconcilable goals: ● To innovate rapidly. To provide stability for the long-term ● Red Hat Enterprise Linux (RHEL) ● Stable and supported for 7 years plus. A platform for 3rd party standardization ● Free as in speech ● Fedora Project / Fedora Core ● Rapid releases of Fedora Core, every 6 months ● Space to innovate. Fedora Core in the tradition of Red Hat Linux (“ FC1 == RHL10” ) Free as in speech, free as in beer, free as in community support ● Built and sponsored by Red Hat ● ...with increased community contributions.
  • Red Hat Enterprise Linux 8 Customizing Anaconda

    Red Hat Enterprise Linux 8 Customizing Anaconda

    Red Hat Enterprise Linux 8 Customizing Anaconda Changing the installer appearance and creating custom add-ons on Red Hat Enterprise Linux 8 Last Updated: 2021-09-29 Red Hat Enterprise Linux 8 Customizing Anaconda Changing the installer appearance and creating custom add-ons on 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. Node.js ® is an official trademark of Joyent.