From 7ff1a26e4b8e8f41ce6db0376c775b8107abc498 Mon Sep 17 00:00:00 2001 From: Petr Bokoc Date: Oct 16 2018 14:59:27 +0000 Subject: Convert links to https where applicable --- diff --git a/README.md b/README.md index 01d88c2..3baa901 100644 --- a/README.md +++ b/README.md @@ -14,8 +14,8 @@ All of this is written in AsciiDoc. It's a simple mostly-plain-text markup language. You may want to look at: -* [AsciiDoc Syntax Quick Reference](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/) -* [AsciiDoc Writer’s Guide](http://asciidoctor.org/docs/asciidoc-writers-guide/) +* [AsciiDoc Syntax Quick Reference](https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/) +* [AsciiDoc Writer’s Guide](https://asciidoctor.org/docs/asciidoc-writers-guide/) * [Antora Documentation](https://docs.antora.org/antora/1.0/page/) diff --git a/modules/install-guide/pages/Downloading_Fedora.adoc b/modules/install-guide/pages/Downloading_Fedora.adoc index 22e1f74..23558b1 100644 --- a/modules/install-guide/pages/Downloading_Fedora.adoc +++ b/modules/install-guide/pages/Downloading_Fedora.adoc @@ -15,7 +15,7 @@ Each of these downloads provides a different set of default packages, but you ca .Which Architecture Is My Computer? Most modern systems are 64{nbsp}bit x86 architecture. If your computer was manufactured after 2007, or you aren't sure, you probably have a `x86_64` system. -Changing a Fedora installation from one architecture to another is not supported. Use the following table to determine the architecture of your computer according to the type of processor. Consult your manufacturer's documentation for details on your processor, or resources such as link:++http://ark.intel.com/++[] or link:++http://products.amd.com/++[], if necessary. +Changing a Fedora installation from one architecture to another is not supported. Use the following table to determine the architecture of your computer according to the type of processor. Consult your manufacturer's documentation for details on your processor, or resources such as link:++https://ark.intel.com/++[] or link:++https://products.amd.com/++[], if necessary. [[List-Processor_and_Architecture_Types]] .Processor and architecture types @@ -24,7 +24,7 @@ Changing a Fedora installation from one architecture to another is not supported |=== |Processor manufacturer and model|Architecture type for Fedora |some Intel Atom, Core series, Pentium 4, and recent vintage Xeon; AMD Athlon, Duron, some Semprons; and older; VIA C3, C7|`i386` -|some Intel Atom, Core 2 series, Core i series and Xeon; +|some Intel Atom, Core 2 series, Core i series and Xeon; AMD: Athlon 64, Athlon II, Sempron64, Phenom series, Fusion series, Bulldozer series and Opteron; Apple MacBook, MacBook Pro, and MacBook Air|`x86_64` |=== @@ -49,9 +49,9 @@ ARM devices often require special setup procedures that aren't covered in this g Cloud Images:: Fedora Cloud images are preconfigured filesystem images with very few packages installed by default. They include special tools for interacting with cloud platforms, and are not intended to be used outside of cloud environments. + -Fedora Cloud comes in several varieties. The Fedora Cloud Base image is a minimal base for cloud deployments. The Fedora Cloud Atomic image is a Docker container host that uses link:++http://www.projectatomic.io/++[Project Atomic] technology for updates. A Docker base image for Fedora is also available. +Fedora Cloud comes in several varieties. The Fedora Cloud Base image is a minimal base for cloud deployments. The Fedora Cloud Atomic image is a Docker container host that uses link:++https://www.projectatomic.io/++[Project Atomic] technology for updates. A Docker base image for Fedora is also available. + -Cloud images are preconfigured and do not require installation as described in this guide. Get started using Fedora Cloud at link:++http://fedoraproject.org/wiki/Cloud++[] +Cloud images are preconfigured and do not require installation as described in this guide. Get started using Fedora Cloud at link:++https://fedoraproject.org/wiki/Cloud++[] Boot Images:: The tiny images at link:++https://boot.fedoraproject.org/++[] are written to CDs, USB drives, or even floppy disks. The BFO image loads installation media from Fedora's servers and directly loads an installation environment, like the netinstall ISO. + diff --git a/modules/install-guide/pages/Introduction.adoc b/modules/install-guide/pages/Introduction.adoc index 5b8e549..538e4bf 100644 --- a/modules/install-guide/pages/Introduction.adoc +++ b/modules/install-guide/pages/Introduction.adoc @@ -15,7 +15,7 @@ This document details the full range of installation options, including those th [[sect-introduction-about]] === About Fedora -To find out more about {PRODUCT}, visit the link:++http://fedoraproject.org/++[{PRODUCT} Project Website]. Other documentation describing additional topics related to {PRODUCT} is available at link:++http://docs.fedoraproject.org/++[{PRODUCT} Documentation]. Also see the link:++https://fedoraproject.org/wiki/Fedora_Project_Wiki++[{PRODUCT} Project Wiki]. +To find out more about {PRODUCT}, visit the link:++https://fedoraproject.org/++[{PRODUCT} Project Website]. Other documentation describing additional topics related to {PRODUCT} is available at link:++https://docs.fedoraproject.org/++[{PRODUCT} Documentation]. Also see the link:++https://fedoraproject.org/wiki/Fedora_Project_Wiki++[{PRODUCT} Project Wiki]. [[sect-introduction-additional-help]] === Getting Additional Help @@ -41,7 +41,7 @@ This guide helps a reader: [NOTE] ==== -This guide does not cover *use* of {PRODUCT}. To learn how to use an installed {PRODUCT} system, see the other manuals available at link:++http://docs.fedoraproject.org/++[Fedora Documentation]. +This guide does not cover *use* of {PRODUCT}. To learn how to use an installed {PRODUCT} system, see the other manuals available at link:++https://docs.fedoraproject.org/++[Fedora Documentation]. ==== diff --git a/modules/install-guide/pages/_partials/Legal_Notice.adoc b/modules/install-guide/pages/_partials/Legal_Notice.adoc index b65d4a5..5027815 100644 --- a/modules/install-guide/pages/_partials/Legal_Notice.adoc +++ b/modules/install-guide/pages/_partials/Legal_Notice.adoc @@ -3,7 +3,7 @@ Copyright {YEAR} {HOLDER}. -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 link:++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. +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 link:++https://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. diff --git a/modules/install-guide/pages/_partials/entities.adoc b/modules/install-guide/pages/_partials/entities.adoc index 0d34079..cde4231 100644 --- a/modules/install-guide/pages/_partials/entities.adoc +++ b/modules/install-guide/pages/_partials/entities.adoc @@ -1,7 +1,7 @@ :BOOKID: install-guide -:BZURL: link:https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Documentation&component=install-guide[http://bugzilla.redhat.com/] +:BZURL: link:https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Documentation&component=install-guide[https://bugzilla.redhat.com/] :HOLDER: Red Hat, Inc. and others diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_AddBtrfs.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_AddBtrfs.adoc index 1f57e81..92689dd 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_AddBtrfs.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_AddBtrfs.adoc @@ -46,7 +46,7 @@ If you select a redundant RAID type (such as `RAID1 (Redundancy)`), the volume w ==== + -You can also make sure that the volume is encrypted by selecting the `Encrypt` option; this will enable LUKS encryption for the entire volume. See the [citetitle]_{PRODUCT} Security Guide_, available at link:++http://docs.fedoraproject.org/++[], for information about LUKS disk encryption. +You can also make sure that the volume is encrypted by selecting the `Encrypt` option; this will enable LUKS encryption for the entire volume. See the [citetitle]_{PRODUCT} Security Guide_, available at link:++https://docs.fedoraproject.org/++[], for information about LUKS disk encryption. + Additionally, you can set a fixed size for the volume by selecting the `Fixed` option from the `Size policy` menu and entering a size for the volume group. + diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc index 422a21e..edd604b 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_AddLVM.adoc @@ -46,7 +46,7 @@ If you select a redundant RAID type (such as `RAID1 (Redundancy)`), the volume g ==== + -You can also make sure that the volume group is encrypted by selecting the `Encrypt` option; this will enable LUKS encryption for the entire volume group. See the [citetitle]_{PRODUCT} Security Guide_, available at link:++http://docs.fedoraproject.org/++[], for information about LUKS disk encryption. +You can also make sure that the volume group is encrypted by selecting the `Encrypt` option; this will enable LUKS encryption for the entire volume group. See the [citetitle]_{PRODUCT} Security Guide_, available at link:++https://docs.fedoraproject.org/++[], for information about LUKS disk encryption. + Additionally, you can set a fixed size for the volume group by selecting the `Fixed` option from the `Size policy` menu and entering a size for the volume group. + diff --git a/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc b/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc index 9d6306e..a3535ce 100644 --- a/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc +++ b/modules/install-guide/pages/_partials/install/CustomSpoke_PartitioningAdvice.adoc @@ -12,7 +12,7 @@ There is no best way to partition every system; the optimal setup depends on how * Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the `/boot` directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and `/usr` can not be on a Btrfs subvolume. -* If you are new to Linux, consider reviewing the [citetitle]_Linux Filesystem Hierarchy Standard_ at link:++http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html++[] for information about various system directories and their contents. +* If you are new to Linux, consider reviewing the [citetitle]_Linux Filesystem Hierarchy Standard_ at link:++https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html++[] for information about various system directories and their contents. * Each kernel installed on your system requires approximately 20 MB on the `/boot` partition. The default partition size of 500 MB for `/boot` should suffice for most common uses; increase the size of this partition if you plan to keep many kernels installed at the same time. diff --git a/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc b/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc index d319837..623922b 100644 --- a/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/DateTimeSpoke.adoc @@ -17,7 +17,7 @@ You can also select a time zone relative to Greenwich Mean Time (GMT) without se [NOTE] ==== -The list of cities and regions comes from the Time Zone Database ([package]*tzdata*) public domain, which is maintained by the Internet Assigned Numbers Authority (IANA). The Fedora Project can not add cities or regions into this database. You can find more information at the link:++http://www.iana.org/time-zones++[IANA official website]. +The list of cities and regions comes from the Time Zone Database ([package]*tzdata*) public domain, which is maintained by the Internet Assigned Numbers Authority (IANA). The Fedora Project can not add cities or regions into this database. You can find more information at the link:++https://www.iana.org//time-zones++[IANA official website]. ==== diff --git a/modules/install-guide/pages/_partials/install/FilterSpoke_AddiSCSI.adoc b/modules/install-guide/pages/_partials/install/FilterSpoke_AddiSCSI.adoc index 4e087a7..e9621c7 100644 --- a/modules/install-guide/pages/_partials/install/FilterSpoke_AddiSCSI.adoc +++ b/modules/install-guide/pages/_partials/install/FilterSpoke_AddiSCSI.adoc @@ -35,7 +35,7 @@ A complete IQN will therefore look as follows: + An example using the correct format is also displayed below the input field for reference. + -For more information about IQNs, see [citetitle]_3.2.6. iSCSI Names in RFC 3720 - Internet Small Computer Systems Interface (iSCSI)_, available from link:++http://tools.ietf.org/html/rfc3720#section-3.2.6++[] and [citetitle]_1. iSCSI Names and Addresses in RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery_, available from link:++http://tools.ietf.org/html/rfc3721#section-1++[]. +For more information about IQNs, see [citetitle]_3.2.6. iSCSI Names in RFC 3720 - Internet Small Computer Systems Interface (iSCSI)_, available from link:++https://tools.ietf.org/html/rfc3720#section-3.2.6++[] and [citetitle]_1. iSCSI Names and Addresses in RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery_, available from link:++https://tools.ietf.org/html/rfc3721#section-1++[]. . Specify the type of authentication to use for iSCSI discovery using the `Discovery Authentication Type` drop-down menu. Depending on which type of authentication you selected, additional input fields (such as `CHAP Username` and `CHAP Password` may then become visible. Fill in your authentication credentials; these should be provided by your organization. @@ -56,4 +56,4 @@ If the discovery was successful, you will see a list of all discovered nodes. + After selecting all nodes you want to use, click `Log In` to initiate an iSCSI session. [application]*Anaconda* will attempt to log in to all selected nodes. If the login process is succesful, the `Add iSCSI Storage Target` dialog will close, and all nodes you have configured will now be shown in the list of network disks in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. -You can repeat this procedure to discover additional iSCSI targets, or to add more nodes from a previously configured target. However, note that once you click the `Start Discovery` button for the first time, you will not be able to change the `iSCSI Initiator Name`. If you made an error when configuring the initiator name, you must restart the installation. \ No newline at end of file +You can repeat this procedure to discover additional iSCSI targets, or to add more nodes from a previously configured target. However, note that once you click the `Start Discovery` button for the first time, you will not be able to change the `iSCSI Initiator Name`. If you made an error when configuring the initiator name, you must restart the installation. diff --git a/modules/install-guide/pages/_partials/install/NetworkSpoke.adoc b/modules/install-guide/pages/_partials/install/NetworkSpoke.adoc index 773258b..5ede966 100644 --- a/modules/install-guide/pages/_partials/install/NetworkSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/NetworkSpoke.adoc @@ -9,7 +9,7 @@ The `Network & Hostname` screen is used to configure network interfaces. Options [NOTE] ==== -Network configuration is an expansive topic and many of the options available during the installation are beyond the scope of this document. For detailed information about networking, including both theoretical topics and specific instructions and examples, see the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Network configuration is an expansive topic and many of the options available during the installation are beyond the scope of this document. For detailed information about networking, including both theoretical topics and specific instructions and examples, see the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. ==== diff --git a/modules/install-guide/pages/_partials/install/NetworkSpoke_EditConnection.adoc b/modules/install-guide/pages/_partials/install/NetworkSpoke_EditConnection.adoc index cf6bf90..b449a1d 100644 --- a/modules/install-guide/pages/_partials/install/NetworkSpoke_EditConnection.adoc +++ b/modules/install-guide/pages/_partials/install/NetworkSpoke_EditConnection.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-network-configuration-advanced]] ==== Editing Network Interface Configuration -This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. +This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. To configure a network connection manually, select that connection in the list on the left side of the screen, and click the `Configure` button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface].. A full description of all configuration settings for all connection types is beyond the scope of this document; see the [citetitle]_Networking Guide_ for details. diff --git a/modules/install-guide/pages/_partials/install/NetworkSpoke_VirtualInterfaces.adoc b/modules/install-guide/pages/_partials/install/NetworkSpoke_VirtualInterfaces.adoc index 8dda47d..a05e5f9 100644 --- a/modules/install-guide/pages/_partials/install/NetworkSpoke_VirtualInterfaces.adoc +++ b/modules/install-guide/pages/_partials/install/NetworkSpoke_VirtualInterfaces.adoc @@ -12,7 +12,7 @@ To add a virtual network interface, click the `+` button at the bottom of the in * `Vlan` (_Virtual LAN_) - A method to create multiple distinct broadcast domains which are mutually isolated. -Select the interface type you want to add, and click `Add`. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. Basic documentation is also available in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration]. +Select the interface type you want to add, and click `Add`. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. Basic documentation is also available in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration]. [NOTE] ==== diff --git a/modules/install-guide/pages/_partials/install/PasswordSpoke.adoc b/modules/install-guide/pages/_partials/install/PasswordSpoke.adoc index 4ed6f21..e226aac 100644 --- a/modules/install-guide/pages/_partials/install/PasswordSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/PasswordSpoke.adoc @@ -11,7 +11,7 @@ The `root` account will always be created during the installation. However, you [WARNING] ==== -The `root` account has complete control over the system. If an unauthorized person gains access to this account, they can access or delete all users' personal files or otherwise exploit the machine for their own nefarious purposes. See the [citetitle]_{PRODUCT} Security Guide_, available at link:++http://docs.fedoraproject.org/++[], for detailed documentation about account security and guidelines for choosing a strong password. +The `root` account has complete control over the system. If an unauthorized person gains access to this account, they can access or delete all users' personal files or otherwise exploit the machine for their own nefarious purposes. See the [citetitle]_{PRODUCT} Security Guide_, available at link:++https://docs.fedoraproject.org/++[], for detailed documentation about account security and guidelines for choosing a strong password. ==== diff --git a/modules/install-guide/pages/_partials/install/StorageSpoke.adoc b/modules/install-guide/pages/_partials/install/StorageSpoke.adoc index 511f668..f294c59 100644 --- a/modules/install-guide/pages/_partials/install/StorageSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/StorageSpoke.adoc @@ -45,7 +45,7 @@ With automatic partitioning, you can also select the `I would like to make addit * `I will configure partitioning` - Select this option and press `Done` in the top left corner of the screen to configure your system's partitioning layout manually. This requires some knowledge of the theory behind disk partitions and related concepts, but gives you full control over the way the system will be installed. For instructions for manual partitioning, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning]. -Additionally, you can select `Encrypt my data`pass:attributes[{blank}]; this will encrypt all partitions except the ones needed to boot the system (such as `/boot`) using _Linux Unified Key Setup_ (LUKS). Encrypting your hard drive is recommended. For detailed information about LUKS encryption, see the [citetitle]_{PRODUCT} Security{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Additionally, you can select `Encrypt my data`pass:attributes[{blank}]; this will encrypt all partitions except the ones needed to boot the system (such as `/boot`) using _Linux Unified Key Setup_ (LUKS). Encrypting your hard drive is recommended. For detailed information about LUKS encryption, see the [citetitle]_{PRODUCT} Security{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. [WARNING] ==== diff --git a/modules/install-guide/pages/_partials/install/StorageSpoke_BootLoader.adoc b/modules/install-guide/pages/_partials/install/StorageSpoke_BootLoader.adoc index 15bfaa5..bcfc478 100644 --- a/modules/install-guide/pages/_partials/install/StorageSpoke_BootLoader.adoc +++ b/modules/install-guide/pages/_partials/install/StorageSpoke_BootLoader.adoc @@ -13,7 +13,7 @@ Installing [application]*GRUB2* may overwrite your existing boot loader. ==== -If you have other operating systems already installed, the {PRODUCT} installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing [application]*GRUB2* configuration, see the [citetitle]_{PRODUCT} System{nbsp}Administrator's{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[] +If you have other operating systems already installed, the {PRODUCT} installer will attempt to automatically detect and configure the boot loader to start them. You can manually configure any additional operating systems after you finish the installation, if they are not detected properly. For instructions on editing [application]*GRUB2* configuration, see the [citetitle]_{PRODUCT} System{nbsp}Administrator's{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[] If you are installing Fedora system with more than one disk, you may want to manually specify where the bootloader should be installed. Click the `Full disk summary and bootloader` link at the bottom of the `Installation Destination` screen. The `Selected Disks` dialog will appear. The bootloader will be installed on the device of your choice, or on a UEFI system, the `EFI system partition` will be created on that device during guided partitioning. diff --git a/modules/install-guide/pages/_partials/install/UserSpoke.adoc b/modules/install-guide/pages/_partials/install/UserSpoke.adoc index c768f2b..985f8a0 100644 --- a/modules/install-guide/pages/_partials/install/UserSpoke.adoc +++ b/modules/install-guide/pages/_partials/install/UserSpoke.adoc @@ -37,7 +37,7 @@ The `Make this user administrator` check box gives the user you are creatng admi If you give administrator privileges to an user, make sure that the account is protected by a strong password. Never give an user administrator privileges without requiring any password for the account. -See the [citetitle]_{PRODUCT} Security Guide_, available at the link:++http://docs.fedoraproject.org/++[], for detailed information about password security including guidelines for selecting strong passwords. +See the [citetitle]_{PRODUCT} Security Guide_, available at the link:++https://docs.fedoraproject.org/++[], for detailed information about password security including guidelines for selecting strong passwords. ==== diff --git a/modules/install-guide/pages/advanced/Boot_Options.adoc b/modules/install-guide/pages/advanced/Boot_Options.adoc index 0f73bc8..58bdcbc 100644 --- a/modules/install-guide/pages/advanced/Boot_Options.adoc +++ b/modules/install-guide/pages/advanced/Boot_Options.adoc @@ -202,7 +202,7 @@ Use a comma-separated list to disable multiple drivers. For example: modprobe.blacklist=ahci,firewire_ohci ---- -[option]#inst.sshd#:: Starts the `sshd` service during the installation, which allows you to connect to the system during the installation using `SSH` and monitor its progress. For more information on `SSH`, see the `ssh(1)` man page and the corresponding chapter in the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +[option]#inst.sshd#:: Starts the `sshd` service during the installation, which allows you to connect to the system during the installation using `SSH` and monitor its progress. For more information on `SSH`, see the `ssh(1)` man page and the corresponding chapter in the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. + [NOTE] ==== @@ -214,7 +214,7 @@ During the installation, the `root` account has no password by default. You can [[sect-boot-options-network]] === Network Boot Options -Initial network initialization is handled by [application]*dracut*. This section only lists some of the more commonly used options; for a complete list, see the `dracut.cmdline(7)` man page. Additional information on networking is also available in the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Initial network initialization is handled by [application]*dracut*. This section only lists some of the more commonly used options; for a complete list, see the `dracut.cmdline(7)` man page. Additional information on networking is also available in the [citetitle]_{PRODUCT} Networking Guide_, available at link:++https://docs.fedoraproject.org/++[]. [option]#ip=#:: Configures one or more network interfaces. To configure multiple interfaces, use the `ip` option multiple times - once for each interface. If multiple interfaces are configured, you must specify a primary boot interface using the [option]#bootdev# option described below. + @@ -380,7 +380,7 @@ VNC password must be six to eight characters long. Please enter a new one, or leave blank for no password. Password: - + ---- ==== @@ -535,7 +535,7 @@ The amount of time it takes to complete a single full pass of [application]*Memt To halt the tests and reboot your computer, press the kbd:[Esc] key at any time. -For more information about using [application]*Memtest86+*, see the official website at link:++http://www.memtest.org/++[]. A `README` file is also located in `/usr/share/doc/memtest86+-_version_pass:attributes[{blank}]/` on {PRODUCT} systems with the [package]*memtest86+* package installed. +For more information about using [application]*Memtest86+*, see the official website at link:++https://www.memtest.org/++[]. A `README` file is also located in `/usr/share/doc/memtest86+-_version_pass:attributes[{blank}]/` on {PRODUCT} systems with the [package]*memtest86+* package installed. [[sect-boot-options-mediacheck]] === Verifying Boot Media diff --git a/modules/install-guide/pages/advanced/Network_based_Installations.adoc b/modules/install-guide/pages/advanced/Network_based_Installations.adoc index 17b0a51..f2fa38c 100644 --- a/modules/install-guide/pages/advanced/Network_based_Installations.adoc +++ b/modules/install-guide/pages/advanced/Network_based_Installations.adoc @@ -100,7 +100,7 @@ next-server 192.168.1.2; [command]#systemctl restart dhcpd# [command]#journalctl --unit dhcpd --since -2m --follow# - + ---- [[pxe-tftpd]] @@ -173,18 +173,18 @@ label linux menu label ^Install Fedora {PRODVER} 64-bit menu default kernel f{PRODVER}/vmlinuz -append initrd=f{PRODVER}/initrd.img inst.stage2=http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp +append initrd=f{PRODVER}/initrd.img inst.stage2=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp label server menu label ^Install Fedora {PRODVER} ( Minimal Image ) menu default kernel f{PRODVER}/vmlinuz -append initrd=f{PRODVER}/initrd.img inst.stage2=http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp ks=https://example.com/fedora/kickstarts/minimal.ks +append initrd=f{PRODVER}/initrd.img inst.stage2=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp ks=https://example.com/fedora/kickstarts/minimal.ks label rescue menu label ^Rescue installed system kernel f{PRODVER}/vmlinuz -append initrd=f{PRODVER}initrd.img ip=dhcp root=live:http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/LiveOS/squashfs.img rescue +append initrd=f{PRODVER}initrd.img ip=dhcp root=live:https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/LiveOS/squashfs.img rescue label local menu label Boot from ^local drive @@ -208,18 +208,18 @@ set gfxpayload=keep insmod gzio menuentry 'Install {PRODUCT} 64-bit' --class fedora --class gnu-linux --class gnu --class os { - linuxefi f{PRODVER}/vmlinuz ip=dhcp inst.repo=http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ + linuxefi f{PRODVER}/vmlinuz ip=dhcp inst.repo=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ initrdefi f{PRODVER}/initrd.img } menuentry 'Install Fedora {PRODVER} Server' --class fedora --class gnu-linux --class gnu --class os { kernel f{PRODVER}/vmlinuz - append initrd=f{PRODVER}/initrd.img inst.repo=http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-install-server.ks?h=f21 + append initrd=f{PRODVER}/initrd.img inst.repo=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-install-server.ks?h=f21 } menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gnu --class os { kernel f{PRODVER}/vmlinuz - append f{PRODVER}/initrd=initrd.img root=live:http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/LiveOS/squashfs.img rescue + append f{PRODVER}/initrd=initrd.img root=live:https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/LiveOS/squashfs.img rescue } ---- @@ -238,14 +238,14 @@ menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gn + [subs="attributes"] ---- -# wget http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/images/pxeboot/vmlinuz -O /var/lib/tftpboot/f{PRODVER}/vmlinuz +# wget https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/images/pxeboot/vmlinuz -O /var/lib/tftpboot/f{PRODVER}/vmlinuz ---- . Download the initrd + [subs="attributes"] ---- -# wget http://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/images/pxeboot/initrd.img -O /var/lib/tftpboot/f{PRODVER}/initrd.img +# wget https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/images/pxeboot/initrd.img -O /var/lib/tftpboot/f{PRODVER}/initrd.img ---- [[pxe-repositories]] @@ -253,11 +253,11 @@ menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gn The examples in this section use the public Fedora mirrors as the package source. For faster installations, installing to many systems, or more isolated environments, you may wish to maintain a local repository. -Fedora Infrastructure maintains instructions for a configuring a local mirror at link:++https://fedoraproject.org/wiki/Infrastructure/Mirroring++[]. The preferred method for providing repositories is via HTTP, and you can refer to the [citetitle]_Fedora System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], to configure `httpd`. +Fedora Infrastructure maintains instructions for a configuring a local mirror at link:++https://fedoraproject.org/wiki/Infrastructure/Mirroring++[]. The preferred method for providing repositories is via HTTP, and you can refer to the [citetitle]_Fedora System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], to configure `httpd`. [[sect-install-server-cobbler]] == Advanced network installations with Cobbler For more complex environments, {PRODUCT} offers the [package]*cobbler* installation server. Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by [package]*cobbler*. -While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide. The cobbler community provides excellent documentation at link:++http://www.cobblerd.org/manuals/2.6.0/++[] to accompany the packages in the Fedora repository. +While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide. The cobbler community provides excellent documentation at link:++http://www.cobblerd.org/category/manuals/++[] to accompany the packages in the Fedora repository. diff --git a/modules/install-guide/pages/advanced/VNC_Installations.adoc b/modules/install-guide/pages/advanced/VNC_Installations.adoc index 7ab685c..35f9f68 100644 --- a/modules/install-guide/pages/advanced/VNC_Installations.adoc +++ b/modules/install-guide/pages/advanced/VNC_Installations.adoc @@ -110,7 +110,7 @@ You can then proceed with xref:../install/Installing_Using_Anaconda.adoc#chap-in [[sect-vnc-installations-connect-mode]] === Installing in VNC Connect Mode -VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in {PRODUCT} is available in the [citetitle]_{PRODUCT} Security{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. +VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in {PRODUCT} is available in the [citetitle]_{PRODUCT} Security{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. [[proc-vnc-installations-connect-mode]] .Starting VNC in Connect Mode @@ -134,7 +134,7 @@ The terminal will display a message similar to the following example: TigerVNC Viewer 64-bit v1.3.0 (20130924) Built on Sep 24 2013 at 16:32:56 Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) -See http://www.tigervnc.org for information on TigerVNC. +See https://tigervnc.org/ for information on TigerVNC. Thu Feb 20 15:23:54 2014 main: Listening on port 5901 diff --git a/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc b/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc index 827fded..60809be 100644 --- a/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc +++ b/modules/install-guide/pages/appendixes/Kickstart_Syntax_Reference.adoc @@ -41,7 +41,7 @@ $ [command]#ksverdiff -f F{PREVVER} -t F{PRODVER}# The [option]#-f# option specifies the release to start the comparison with, and the [option]#-t# option to specify the release to end with. For additional information, see the `ksverdiff(1)` man page. Also note that you can not use this to display changes in a release that is newer than your system - the version of [package]*pykickstart* on Fedora{nbsp}{PREVVER} can not display changes in Fedora{nbsp}{PRODVER}. -Additionally, you can review the [citetitle]_Fedora{nbsp}{PRODVER} Release Notes_, available at link:++http://docs.fedoraproject.org/++[], for a list of changes. +Additionally, you can review the [citetitle]_Fedora{nbsp}{PRODVER} Release Notes_, available at link:++https://docs.fedoraproject.org/++[], for a list of changes. [NOTE] ==== @@ -221,7 +221,7 @@ Used for OSTree installations. See link:++https://wiki.gnome.org/action/show/Pro Configures additional [application]*DNF* repositories that may be used as sources for package installation. This command can be used multiple times in a single Kickstart file. -See the [citetitle]_Fedora System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for information about the [application]*DNF* package manager. +See the [citetitle]_Fedora System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for information about the [application]*DNF* package manager. [IMPORTANT] ==== @@ -291,7 +291,7 @@ The created partitioning scheme will follow the recommended scheme described at [option]#--backuppassphrase#:: Adds a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in `/root`, encrypted using the X.509 certificate specified with [option]#--escrowcert#. This option is only meaningful if [option]#--escrowcert# is specified. -[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++http://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. +[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++https://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. [[sect-kickstart-commands-bootloader]] === bootloader (required) - Configure Boot Loader @@ -744,7 +744,7 @@ This option can only be used for partitions which result in a file system such a [option]#--passphrase=#:: Specifies the passphrase to use when encrypting this logical volume. You must use this option together with the [option]#--encrypted# option. This option has no effect by itself. -[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++http://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. +[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++https://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. [option]#--escrowcert=pass:attributes[{blank}]_URL_of_X.509_certificate_pass:attributes[{blank}]#:: Store data encryption keys of all encrypted volumes as files in `/root`, encrypted using the X.509 certificate from the URL specified with _URL_of_X.509_certificate_. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if [option]#--encrypted# is specified. @@ -953,7 +953,7 @@ This option can only be used for partitions which result in a file system such a [option]#--passphrase=#:: Specifies the passphrase to use when encrypting this partition. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. -[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++http://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. +[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++https://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. [option]#--escrowcert=pass:attributes[{blank}]_URL_of_X.509_certificate_pass:attributes[{blank}]#:: Stores data encryption keys of all encrypted volumes as files in `/root`, encrypted using the X.509 certificate from the URL specified with _URL_of_X.509_certificate_. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if [option]#--encrypted# is specified. @@ -1003,7 +1003,7 @@ _mntpoint_:: Location where the RAID file system is mounted. If it is `/`, the [option]#--passphrase=#:: Specifies the passphrase to use when encrypting this partition. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. -[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++http://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. +[option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++https://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. [option]#--escrowcert=pass:attributes[{blank}]_URL_of_X.509_certificate_pass:attributes[{blank}]#:: Stores data encryption keys of all encrypted volumes as files in `/root`, encrypted using the X.509 certificate from the URL specified with _URL_of_X.509_certificate_. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if [option]#--encrypted# is specified. @@ -1310,7 +1310,7 @@ The above command will create a bond device named `mynetwork` using the `em1` an [command]#network --bondopts=mode=active-backup,balance-rr;primary=eth1# ---- + -Available optional parameters are listed in the [citetitle]_Working with Kernel Modules_ chapter of the [citetitle]_Fedora System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Available optional parameters are listed in the [citetitle]_Working with Kernel Modules_ chapter of the [citetitle]_Fedora System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. + [IMPORTANT] ==== @@ -1361,7 +1361,7 @@ See also the [option]#--teamconfig=# option. [command]#network --device=bridge0 --bridgeslaves=em1# ---- -[option]#--bridgeopts=#:: An optional comma-separated list of parameters for the bridged interface. Available values are `stp`, `priority`, `forward-delay`, `hello-time`, `max-age`, and `ageing-time`. For information about these parameters, see the [citetitle]_bridge setting_ table in the `nm-settings(5)` man page or at link:++https://developer.gnome.org/NetworkManager/0.9/ref-settings.html++[]. Also see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[], for general information about network bridging. +[option]#--bridgeopts=#:: An optional comma-separated list of parameters for the bridged interface. Available values are `stp`, `priority`, `forward-delay`, `hello-time`, `max-age`, and `ageing-time`. For information about these parameters, see the [citetitle]_bridge setting_ table in the `nm-settings(5)` man page or at link:++https://developer.gnome.org/NetworkManager/0.9/ref-settings.html++[]. Also see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++https://docs.fedoraproject.org/++[], for general information about network bridging. [[sect-kickstart-commands-environment]] == Console and Environment @@ -1658,7 +1658,7 @@ This will generate a SHA512 crypt of your password using your provided salt. [[sect-kickstart-commands-selinux]] === selinux (optional) - Configure SELinux -Sets the state of SELinux on the installed system. The default policy is `enforcing`. For more information regarding SELinux in {PRODUCT}, see the [citetitle]_{PRODUCT} SELinux User's and Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Sets the state of SELinux on the installed system. The default policy is `enforcing`. For more information regarding SELinux in {PRODUCT}, see the [citetitle]_{PRODUCT} SELinux User's and Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. [subs="quotes, macros"] ---- diff --git a/modules/install-guide/pages/install/After_Installation.adoc b/modules/install-guide/pages/install/After_Installation.adoc index 340c9a3..f64cc3d 100644 --- a/modules/install-guide/pages/install/After_Installation.adoc +++ b/modules/install-guide/pages/install/After_Installation.adoc @@ -33,22 +33,22 @@ After you finish the installation and go through one of the initial setup utilit Recover a lost `root` password:: The `root` password, which is configured during the installation, is required for accessing the system as the `root` user. Without this password you will not be able to configure your system or install additional software. If you lost or forgot your `root` password, you can reset it by following the steps described in xref:Troubleshooting.adoc#sect-trouble-after-reset-root-password[Resetting the Root Password]. -Configure the network:: In most cases, network access is configured during the installation process, either in the [application]*Anaconda* installation program (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]) or in a Kickstart file (see xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-network[network (optional) - Configure Network Interfaces]). For information on configuring the network after the installation, see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Configure the network:: In most cases, network access is configured during the installation process, either in the [application]*Anaconda* installation program (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]) or in a Kickstart file (see xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-network[network (optional) - Configure Network Interfaces]). For information on configuring the network after the installation, see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++https://docs.fedoraproject.org/++[]. Perform an initial system update:: If you installed {PRODUCT} from a full installation ISO image (such as the Workstation live image or full Server DVD), it is recommended to perform an initial system update, because your installation media likely contained older versions of software packages. During the initial update, all installed packages are updated to their latest available versions. Updates to packages provide security fixes, bug fixes and enhancements. + -The [application]*DNF* package manager is used for updating installed packages. For more information about updating your system with [application]*DNF*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +The [application]*DNF* package manager is used for updating installed packages. For more information about updating your system with [application]*DNF*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. Install driver updates:: Usually, drivers for system devices are already supported in the kernel provided by Red{nbsp}Hat Enterprise{nbsp}Linux. However, occasionally, support for devices that have been released recently could be missing. In these cases, a driver update enabling your device may be available. + -Devices necessary to complete the installation can have driver updates provided before the installation begins. If a device is missing a driver, but it is not essential during the installation, it is recommended to wait until after the installation completes, and install additional drivers afterwards. For instructions on installing and enabling additional drivers on the installed system using [application]*RPM* and [application]*DNF*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Devices necessary to complete the installation can have driver updates provided before the installation begins. If a device is missing a driver, but it is not essential during the installation, it is recommended to wait until after the installation completes, and install additional drivers afterwards. For instructions on installing and enabling additional drivers on the installed system using [application]*RPM* and [application]*DNF*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. Configure additional repositories:: New software is installed from _package repositories_. Package repositories are organized sets of software and metadata that can be accessed by the [application]*DNF* package manager. By default, several update repositories provided by {PRODUCT} are configured automatically and you can install updates and additional software from those. However, if you want to set up additional repositories, for example ones containing your own software, some extra steps are needed. + -For information about configuring additional software repositories, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +For information about configuring additional software repositories, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. -Install additional packages:: You can control which packages will be installed by selecting an environment in the `Software Selection` dialog in the graphical installation (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection]). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the [application]*DNF* package manager to install additional packages after the installation. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for more information. +Install additional packages:: You can control which packages will be installed by selecting an environment in the `Software Selection` dialog in the graphical installation (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection]). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the [application]*DNF* package manager to install additional packages after the installation. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for more information. Switch to a graphical login:: Depending on the options you chose during the installation process, it is possible that your system does not have a graphical interface, instead offering only a text-based prompt. If this is the case and you wish to enable a graphical desktop after the installation, you must install the [application]*X Window System* and your preferred desktop environment (either [application]*GNOME* or [application]*KDE*). + -As with all other software, these packages can be installed using the [application]*DNF* package manager. For information about using [application]*DNF* to install new packages, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. For information on how to enable graphical login by default, see xref:Troubleshooting.adoc#sect-trouble-after-graphical-login[Booting into a Graphical Environment]. \ No newline at end of file +As with all other software, these packages can be installed using the [application]*DNF* package manager. For information about using [application]*DNF* to install new packages, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. For information on how to enable graphical login by default, see xref:Troubleshooting.adoc#sect-trouble-after-graphical-login[Booting into a Graphical Environment]. \ No newline at end of file diff --git a/modules/install-guide/pages/install/Booting_the_Installation.adoc b/modules/install-guide/pages/install/Booting_the_Installation.adoc index 10ff90c..2a5111a 100644 --- a/modules/install-guide/pages/install/Booting_the_Installation.adoc +++ b/modules/install-guide/pages/install/Booting_the_Installation.adoc @@ -24,7 +24,7 @@ There are no separate media provided for BIOS and UEFI systems; all of them can {PRODUCT} does not support UEFI booting for 32-bit x86 systems. Only BIOS boot is supported on these systems. -Also note that {PRODUCT} only fully supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 or later will boot and work normally, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from link:++http://www.uefi.org/specs/agreement/++[]. +Also note that {PRODUCT} only fully supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 or later will boot and work normally, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from link:++https://www.uefi.org/specs/agreement/++[]. ==== diff --git a/modules/install-guide/pages/install/Preparing_for_Installation.adoc b/modules/install-guide/pages/install/Preparing_for_Installation.adoc index 2d764b1..033744a 100644 --- a/modules/install-guide/pages/install/Preparing_for_Installation.adoc +++ b/modules/install-guide/pages/install/Preparing_for_Installation.adoc @@ -156,7 +156,7 @@ The Fedora Project offers different Editions tailored for some specific use case Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in xref:../Downloading_Fedora.adoc#chap-downloading-fedora[Downloading Fedora]. -You can also choose a Fedora _Spin_ featuring favorite alternative desktops or tools for specialized tasks at link:++http://spins.fedoraproject.org++[]. +You can also choose a Fedora _Spin_ featuring favorite alternative desktops or tools for specialized tasks at link:++https://spins.fedoraproject.org++[]. [[sect-verifying-images]] ==== Verifying the Downloaded Image diff --git a/modules/install-guide/pages/install/Troubleshooting.adoc b/modules/install-guide/pages/install/Troubleshooting.adoc index 1f43558..4ed703e 100644 --- a/modules/install-guide/pages/install/Troubleshooting.adoc +++ b/modules/install-guide/pages/install/Troubleshooting.adoc @@ -14,11 +14,11 @@ There are many places on the internet which can help you when you encounter a pr * link:++https://ask.fedoraproject.org/en/questions/++[Ask Fedora] - Fedora's knowledge base, available in multiple languages -* The #fedora IRC channel on link:++http://freenode.net/++[FreeNode] - one of the main IRC channels used by Fedora users, English only +* The #fedora IRC channel on link:++https://freenode.net//++[FreeNode] - one of the main IRC channels used by Fedora users, English only * link:++https://fedoraproject.org/wiki/++[Fedora Project Wiki] - the official wiki for Fedora Project -* link:++http://unix.stackexchange.com/++[Stack Exchange] - an English language Q&A board, not specific to Fedora +* link:++https://unix.stackexchange.com/++[Stack Exchange] - an English language Q&A board, not specific to Fedora [NOTE] ==== @@ -316,7 +316,7 @@ On this line, delete the `rhgb` option. After you finish this procedure, you can reboot your computer. {PRODUCT} will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the `rhgb` option to the `GRUB_CMDLINE_LINUX` line in the `/etc/default/grub` file and refresh the boot loader configuration again using the [command]#grub2-mkconfig# command. -See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for more information about working with the [application]*GRUB2* boot loader. +See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for more information about working with the [application]*GRUB2* boot loader. [[sect-trouble-after-graphical-login]] === Booting into a Graphical Environment @@ -342,7 +342,7 @@ Graphical login is now enabled by default - you will be presented with a graphic # systemctl set-default multi-user.target ---- -For more information about targets in [application]*systemd*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +For more information about targets in [application]*systemd*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. [[sect-trouble-after-no-gui]] === No Graphical User Interface Present @@ -392,7 +392,7 @@ If you have 4GB or more memory installed, but {PRODUCT} only shows around 3.5GB Some hardware configurations have a part of the system's RAM reserved and unavailable to the main system. Notably, laptop computers with integrated graphics cards will reserve some memory for the GPU. For example, a laptop with 4{nbsp}GB of RAM and an integrated Intel graphics card will show only roughly 3.7{nbsp}GB of available memory, even with a 64-bit system. -Additionally, the [application]*kdump* crash kernel dumping mechanism reserves some memory for the secondary kernel used in case of the primary kernel crashing. This reserved memory will also not be displayed as available when using the [command]#free# command. For details about [application]*kdump* and its memory requirements, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Additionally, the [application]*kdump* crash kernel dumping mechanism reserves some memory for the secondary kernel used in case of the primary kernel crashing. This reserved memory will also not be displayed as available when using the [command]#free# command. For details about [application]*kdump* and its memory requirements, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. ==== @@ -444,4 +444,4 @@ GRUB_DISABLE_RECOVERY="true" ---- -See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for more information about working with the [application]*GRUB2* boot loader. +See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for more information about working with the [application]*GRUB2* boot loader.