Установка oracle linux 8 netinstall

Oracle В® Linux 8

Installing Oracle Linux

Oracle Legal Notices

Copyright В© 2019, 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. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Oracle Documentation License

This document uses the Web-based Help format from DocBook XML. The following license information applies to this format.

Copyright В© 1999-2007 Norman Walsh

Copyright В© 2003 Jiri Kosek

Copyright В© 2004-2007 Steve Ball

Copyright В© 2005-2008 The DocBook Project

Copyright В© 2011-2012 O’Reilly Media

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the «Software»), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

Except as contained in this notice, the names of individuals credited with contribution to this software shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the individuals in question.

Any stylesheet derived from this Software that is publicly distributed will be identified with a different name and the version strings in any derived Software will be changed so that no possibility of confusion between the derived package and this Software will exist.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL NORMAN WALSH OR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Web-based Help from DocBook XML

Copyright В© 2008-2012 Kasun Gajasinghe, David Cramer

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

Except as contained in this notice, the names of individuals credited with contribution to this software shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the individuals in question.

Any stylesheet derived from this Software that is publicly distributed will be identified with a different name and the version strings in any derived Software will be changed so that no possibility of confusion between the derived package and this Software will exist.

Warranty: THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL DAVID CRAMER, KASUN GAJASINGHE, OR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Certain search characteristics associated with the DocBook XSL webhelp stylesheets are provided as javascript files generated using Apache Lucene and other fourth party technologies, which are licensed under the Apache License reproduced below.

Источник

ChapterВ 4В Automating an Oracle Linux Installation by Using Kickstart

This chapter describes how to prepare and use kickstart to install Oracle Linux automatically.

4.1В About Kickstart Installations

The kickstart feature enables you to automate the OS installation. A kickstart installation uses a configuration file that instructs the installer how it should implement a specific installation. The feature offers the following benefits:

No user intervention is required during the installation process.

Greater facility in installing on multiple systems.

The kickstart configuration file is useful for troubleshooting a boot-time problem with an installed system.

You can use kickstart to install Oracle Linux locally. However, the best use of this feature is in the installation of the OS on multiple systems over the network. In network installations, a kickstart operation would include the following components:

Kickstart configuration file

Configured network that supports network installs such as providing connectivity to clients to access the necessary installation files, including the kickstart configuration file.

For an example of how to create a network installation setup, see AppendixВ A, Performing a Network Installation.

4.2В About the Kickstart Configuration File

The kickstart configuration file determines how the installer performs the installation on target clients. The instructions are in the form of kickstart-specific options and parameter definitions.

Every Oracle Linux installation creates a configuration file called /root/anaconda-ks.cfg . The file contains configuration definitions based on the system on which Oracle Linux is installed. The file’s contents can be read by kickstart and is therefore ready for use, either as is or as a template, to perform kickstart installations on other clients.

To obtain a kickstart configuration file for an automated installation of Oracle Linux 8, use one of the following methods:

Use the /root/anaconda-ks.cfg file of an existing system that is running Oracle Linux, such as Oracle Linux 7.

You would need to revise the file’s contents to make them applicable to an Oracle Linux 8 installation. If the system also includes the pykickstart package, the following useful tools can help you with reconfiguring the file’s contents:

ksverdiff identifies removed or deprecated kickstart options.

ksvalidator checks that the syntax in the file is correct.

Install Oracle Linux 8 manually on a system which would generate the /root/anaconda-ks.cfg file. Use the file to perform automated installation on other clients. You might need to adjust some of the file’s configurations depending on the specifications you want to apply to those clients.

The kickstart configuration file is divided into parts. Each part contains a group of options and are described in further detail in the subsequent sections:

Note that Oracle Linux 8 supports the Btrfs file system if you use the UEK installation media. This means that you can use the autopart —type btrfs kickstart option to automatically partition your disks using Btrfs. Manual partitioning using Btrfs is also possible as described in the upstream documentation.

4.2.1В Installation Options

Installation options define parameters to apply to the system during installation such as system storage, keyboard definitions, language setting, and so on. The line in bold in the following example enables PXE to bring up the network interface and is important in network installations.

4.2.2В Packages to Install

Packages to be installed are listed under the group heading %packages . The list is terminated by the %end line.

The list would include package groups and individual packages. Names of package groups use the @ prefix, such as @base , to distinguish them from individual packages.

Use the dnf group list command on an existing Oracle Linux server to display both the installed package groups and the package groups that are available to install.

To specify multiple packages, you can use the wildcard character ( * ). To exclude a package from the installation, insert the — character as a prefix to the package name.

The %packages keyword can take options. The following are the most useful:

Installs the available packages without prompting about missing packages. Without this option, kickstart would interrupt the installation and prompt you to continue or cancel the installation.

Sets the multilib policy in dnf configuration to all so that 32-bit packages can be installed on the system.

Instead of listing packages directly into the configuration file, you can compile these names into a file and store it in an accessible location, such as locally in a kickstart’s ramdisk file system, or on an HTTP server or an NFS share. Then on the configuration file, specify the full path to the list in an %include statement, for example:

4.2.3В Preinstallation Options

Preinstallation options define the actions that the installer must perform before beginning the installation process. Configuring this group of options is optional. The options are under the %pre heading and terminated by the %end line.

In the following example, the installer is instructed to run the script config-partitions that is stored on an HTTP server. Further, the installer should also download a list of packages from the web server for use with a %include /tmp/package-list statement in the %packages section.

In this example, the wget command saves the package list in kickstart’s file system, which exists as a ramdisk in memory.

An included script or file must be accessible at the specified path or URL. If no name service is available to identify hosts, then use IP addresses.

4.2.4В Post-Installation Options

Post-installation options define any actions that the installer must perform after the completion of the installation. Configuring this group of options is optional.

Post-installation options are under the %post heading and terminated by the %end line.

By default, kickstart runs postinstallation tasks in a chroot environment that is based on the root file system of the newly installed system. If you need to access any files that are outside the chroot environment, specify the —nochroot option to %post line. You can then access files in the kickstart file system with the newly installed system’s root file system being mounted at /mnt/sysimage .

In the following example, the script /tmp/post-config is run at the end of the installation.

If you configure the installed system’s network interface to obtain its settings using DHCP, you must either use IP addresses instead of domain names or set up a temporary resolv.conf file, for example:

4.3В Performing a Kickstart Installation

The steps to execute a kickstart installation differ slightly when used over the network and when used locally.

4.3.1В Installing Over the Network With Kickstart

Ensure that you have completed the following preparations:

The network has been configured to support network installation and that clients can properly access the necessary installation files.

Network locations are set up to contain the following:

The full Oracle Linux 8 installation ISO image

Properly configured boot loaders for PXE clients.

Kickstart configuration file(s)

Refer to AppendixВ A, Performing a Network Installation for details about configuring the network and the boot loaders.

To begin the installation, do the following:

Boot the client system.

While the system is booting, access its BIOS.

On the displayed BIOS screen, change the system’s boot settings to boot from the network.

Save the revisions and continue the boot process.

After the boot sequence is completed, the installation proceeds automatically.

4.3.2В Installing Locally With Kickstart

For a local use of kickstart, ensure that the following requirements are met:

Access to the full installation media, which can be on a local CD-ROM drive or USB drive. See the instructions on media preparation in Section 1.2, “Preparing Installation Media”.

Local access to the kickstart configuration file.

To begin the installation using kickstart, do the following:

Boot the system from the local boot media.

Select an installation option in the boot menu and then press either E (UEFI-based systems) or Tab (BIOS-based systems) to access the boot prompt.

Add the inst.ks boot option to specify the location of the kickstart file on the local media, for example:

If you are using an NFS server on the network, see Section A.3, “Configuring PXE Boot Loading” for examples of how you can define inst.ks .

For PXE clients, kickstart parameters are typically specified in the boot loader configuration files. For more information, see Section A.3, “Configuring PXE Boot Loading”.

Save the revisions and continue the boot process.

After the boot sequence is completed, the installation proceeds automatically.

Copyright В© 2019, 2021, Oracle and/or its affiliates. Legal Notices

Источник