From 9730ab501eef8822e9f5102a58fc2be991eec43e Mon Sep 17 00:00:00 2001 From: Peter Boy Date: Aug 29 2023 14:57:17 +0000 Subject: Removed finally processed former partials. --- diff --git a/modules/ROOT/pages/_partials/con_block-device-encryption.adoc b/modules/ROOT/pages/_partials/con_block-device-encryption.adoc deleted file mode 100644 index 06ec995..0000000 --- a/modules/ROOT/pages/_partials/con_block-device-encryption.adoc +++ /dev/null @@ -1,4 +0,0 @@ -[id='con_block-device-encryption_{context}'] -= Block device encryption - -Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication. This provides additional security beyond existing operating system security mechanisms as it protects the device's contents even if it has been physically removed from the system. diff --git a/modules/ROOT/pages/_partials/con_introduction-to-luks.adoc b/modules/ROOT/pages/_partials/con_introduction-to-luks.adoc deleted file mode 100644 index cac49c5..0000000 --- a/modules/ROOT/pages/_partials/con_introduction-to-luks.adoc +++ /dev/null @@ -1,24 +0,0 @@ -[id='con_introduction-to-luks_{context}'] -= Introduction to LUKS - -Linux Unified Key Setup (LUKS) is a specification for block device encryption. It establishes an on-disk format for the data, as well as a `passphrase/key` management policy. - -LUKS uses the kernel device mapper subsystem with the `dm-crypt` module. This arrangement provides a low-level mapping that handles encryption and decryption of the device data. You can use the `cryptsetup` utility to perform user-level operations such as creating and accessing encrypted devices. - -What LUKS does:: {blank} -+ -** LUKS encrypts entire block devices and is therefore well-suited for protecting the contents of mobile devices such as removable storage media or laptop disk drives. -+ -** The underlying contents of the encrypted block device are arbitrary. This makes it useful for encrypting [command]`swap` devices. This can also be useful with certain databases that use specially formatted block devices for data storage. -+ -** LUKS uses the existing device mapper kernel subsystem. -+ -** LUKS provides passphrase strengthening which protects against dictionary attacks. -+ -** LUKS devices contain multiple key slots, allowing users to add backup keys or passphrases. - -What LUKS does *not* do:: {blank} -+ -** LUKS is not well-suited for applications requiring more than eight users to have distinct access keys to the same device. -+ -** LUKS is not well-suited for applications requiring file-level encryption. diff --git a/modules/ROOT/pages/_partials/con_package-management-in-fedora.adoc b/modules/ROOT/pages/_partials/con_package-management-in-fedora.adoc deleted file mode 100644 index e22a46d..0000000 --- a/modules/ROOT/pages/_partials/con_package-management-in-fedora.adoc +++ /dev/null @@ -1,57 +0,0 @@ -[[package-management-in-fedora]] -= Package management in Fedora - -Like most modern Linux distributions, Fedora uses a _package management_ system. Package management tools automate installation, upgrading, and removing of software applications and components. - -Each application or component is defined as a _package_. When the package is installed, all code, configuration, and other files are deployed on the system. - -IMPORTANT: A single package is not necessarily the same as an application. Some applications can be shipped as several packages. Moreover, shared code (libraries) in Linux is normally shipped as separate packages, while in other systems applications often ship their own versions of required libraries and install them if necessary. - - -== File placement - -The package management tools track which files on your Fedora installation belong to each package; normally, every file that is installed in the `/usr` tree as well as most configuration files under `/etc` are installed by one of the packages. When installing a package, the package management system verifies its integrity; if any files are missing or corrupted, the package is not installed. - - -== Resolving dependencies - -The package management system also tracks all _dependencies_ between the packages. For example, if an application requires some libraries, the package for this application lists the libraries as dependencies. When you install the application package, the package management tools automatically install the library packages. If a dependency is not available, the tools do not install the package, so you can avoid a sudden malfunction. - -When you want to remove a package, package management tools cleanly delete all code files for this package without affecting other packages. By default, configuration files are not removed, so you can install the package again and keep the configuration that you have set up earlier. - - -== Updating packages - -Updating any package is entirely automatic with the package management system. The system replaces all the necessary code files and preserves existing configuration. - -In fact, for most Linux distributions, including Fedora, all of the system installation except the earliest part is performed by installing various packages. Security updates and upgrades to a next release are performed entirely by package management tools. - - -== RPM - -Fedora's package management system uses the https://rpm.org[RPM] package format. The application that manages packages in Fedora (since version 22) is https://fedoraproject.org/wiki/DNF[DNF]. Graphical package management is provided by the Gnome Software utility. For automatic updates, Fedora uses the PackageKit utility. Command-line and graphical tools provide the same results. - - -== Repositories - -To get packages, DNF uses _repositories_. A repository is an organized collection of packages. Repositories can be kept on any data media; notably, the Fedora installation image contains a repository. However, most up-to-date repositories are normally maintained online. - -Each Fedora release has an official _fedora_ repository and an _updates_ repository (which contains critical updates since the release). In these repositories, you can find most common Linux open-source software. You can also install packages from other repositories, not maintained by the Fedora project and known as _third-party repositories_. - -Most of the time, it is best practice to install software on your Fedora Linux system using only the Fedora package management system. In this case, packages are installed in the most reliable way and automatic updates can be provided. - - -== Installing from source code - -While many Linux applications can be built and installed from from source code, using such builds can make your system much harder to manage. For example, automatic updates to system packages (especially when updating to the next release) might impact an application that was installed from source. And, of course, no automatic security updates are available for the application. - - -== Other installation methods - -Sometimes you might need to install software using other package management systems. Notably: - -* https://www.cpan.org/[CPAN] for libraries for the Perl language -* https://pypi.python.org/pypi[PyPI] for libraries (and sometimes applications) for the Python language -* Commercial repositories for games - -However, installing applications using the Fedora package management systems is the preferred option. diff --git a/modules/ROOT/pages/_partials/creating-encrypted-block-devices.adoc b/modules/ROOT/pages/_partials/creating-encrypted-block-devices.adoc deleted file mode 100644 index dd23874..0000000 --- a/modules/ROOT/pages/_partials/creating-encrypted-block-devices.adoc +++ /dev/null @@ -1,179 +0,0 @@ -[id='creating-encrypted-block-devices_{context}'] -= Creating encrypted block devices - -This procedure describes the steps to create and configure encrypted block devices after installation. - -[id='proc_preparing_block_device_for_encrypting'] -== Step 1: Preparing a block device - -* Install the `cryptsetup` package: -+ ----------- -# dnf install cryptsetup-luks ----------- - -* Create the block devices you want to encrypt using `parted`, `pvcreate`, `lvcreate`, and `mdadm`. - -* Optionally, fill the device, for example, `/dev/sda3` with random data before encrypting it as this increases the strength of encryption. -+ -[NOTE] -======== -Filling the device with random data increases the time necessary for encryption. -======== -+ -[WARNING] -========= -The commands below destroy any existing data on the device. -========= - -** To fill the device with high-quality random data: -+ -------- -dd if=/dev/urandom of= -------- -+ -This takes several minutes per gigabyte on most systems. -+ -** To fill the device with lower-quality random data: -+ --------- -badblocks -c 10240 -s -w -t random -v --------- -+ -This is quicker compared to the high-quality random data method. - -[id='proc_format-device-as-dmcrypt-encrypted-device'] -== Step 2: Formatting an encrypted device - -. Format the device: -+ ---------- -# cryptsetup luksFormat ---------- -+ -Sample output: -+ --------- -WARNING! -======== -This will overwrite data on (for example, /dev/xvdc) irrevocably. - -Are you sure? (Type uppercase yes): YES -Enter LUKS passphrase: -Verify passphrase: -Command successful. --------- -This command initializes the volume, and sets an initial key or passphrase. -+ -[NOTE] -========== -The passphrase is not recoverable so do not forget it. -========== - -. To verify the formatting: -+ ------ -# cryptsetup isLuks && echo Success ------ - -. To see a summary of the encryption information for the device: -+ ---------- -# cryptsetup luksDump ---------- - -[id='proc_create-mapping-to-allow-access-to-decrypted-contents'] -== Step 3: Creating mapping to allow access to a decrypted content - -To access a decrypted content on a device, you need to create a mapping using the kernel `device-mapper`. - -LUKS provides a UUID (Universally Unique Identifier) for each device. This UUID is guranteed to remain the same as long as the LUKS header remains intact. To find a LUKS UUID for the device, run the following command: - --------- -# cryptsetup luksUUID --------- - -An example of a reliable, informative and unique mapping name would be `luks-`, where `` is replaced with the LUKS UUID for the device (for example, luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8). - -. Create a mapping to access the decrypted contents on the device: -+ --------- -# cryptsetup luksOpen --------- -+ -You are prompted to enter the passphrase for the device. Once you have authenticated, you can see the mapping `/dev/mapper/` which represents the decrypted device. You can read from and write to this device like you would any other unencrypted block device. - -. To see the status of the mapping: -+ ------- -# cryptsetup -v status ------- -+ -Sample output: -+ --------- -/dev/mapper/ is active. - type: LUKS1 - cipher: aes-cbc-essiv:sha256 - keysize: 256 bits - device: /dev/xvdc - offset: 4096 sectors - size: 419426304 sectors - mode: read/write -Command successful. --------- - -[id='proc_create-filesystems-on-mapped-device'] -== Step 4: Creating filesystems on a mapped device - -After <>, you can now use the mapped device node `/dev/mapper/` like any other block device. - -. To create an `ext2` filesystem on the mapped device: -+ -------- -# mke2fs /dev/mapper/ -------- - -. To mount this file system: -+ --------- -# mkdir /mnt/test/ -# mount /dev/mapper/ /mnt/test --------- - -[id='proc_add-mapping-information-to-etc-fstab'] -== Step 5: Adding the mapping information to `/etc/fstab` - -In order for a system to setup mapping to a device, add a corresponding entry in the `/etc/crypttab` file. - -. If your system does not have the `/etc/crypttab` file, create a new file and change the owner and group to `root` (`root:root`): -+ ----------- -# touch /etc/crypttab -# chmod 0744 ----------- - -. To identify the correct device in case the device name changes, add: -+ ---------- - none ---------- -+ -Here, the `` field should be given in the form `UUID=`, where `` is the LUKS UUID. - -[id='proc_add-entry-to-etc-fstab'] -== Step 6: Adding an entry to `/etc/fstab` - -To ensure a persistent mapping between the device and the mount point, add the entry in the `/etc/fstab` file: - ------- -/dev/mapper/ ------- - -== Additional resources - - * https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions[LUKS Project Wiki: Frequently Asked Questions] - - * https://man7.org/linux/man-pages/man8/cryptsetup.8.html[cryptsetup(8) man page] - - * https://man7.org/linux/man-pages/man8/dmsetup.8.html[dmsetup(8) man page] diff --git a/modules/ROOT/pages/_partials/proc_checking_fedora_version.adoc b/modules/ROOT/pages/_partials/proc_checking_fedora_version.adoc deleted file mode 100644 index a97fe51..0000000 --- a/modules/ROOT/pages/_partials/proc_checking_fedora_version.adoc +++ /dev/null @@ -1,10 +0,0 @@ -[id="checking_fedora_version"] -= Checking Fedora version - -To check which version of Fedora you are currently using, enter the following command: - ----- -uname -p ----- - -The resulting string is `x86` for a 32-bit version and `x86_64` for a 64-bit version of Fedora. \ No newline at end of file diff --git a/modules/ROOT/pages/_partials/proc_enabling-third-party-repository.adoc b/modules/ROOT/pages/_partials/proc_enabling-third-party-repository.adoc deleted file mode 100644 index c02220e..0000000 --- a/modules/ROOT/pages/_partials/proc_enabling-third-party-repository.adoc +++ /dev/null @@ -1,14 +0,0 @@ -[id='enabling-third-party-repository'] -= Enabling Third party repositories - -Once you have downloaded the rpm, you can enable the repository. - -== To enable repo: - -. Login as root: - `$ su` - -. Create a file in */etc/yum.repos.d/* directory to enable third party repository. This file must end with *.repo* . The repository file contains the URL of the the repository, a name, enabled, gpgcheck. - -. To enable repo, use the following command: - `# dnf --enablerepo=` diff --git a/modules/ROOT/pages/_partials/proc_installing-fonts.adoc b/modules/ROOT/pages/_partials/proc_installing-fonts.adoc deleted file mode 100644 index 7ff8ed0..0000000 --- a/modules/ROOT/pages/_partials/proc_installing-fonts.adoc +++ /dev/null @@ -1,47 +0,0 @@ -= Installing fonts -[[installing-fonts]] - -.Before you start - -Review the fonts on your system. Fedora includes many fonts by default, to see which fonts are installed on your system, use *GNOME Font Viewer*, which is installed by default. Alternatively use the *Fontmatrix* application which is availabe from *GNOME Software* and provides more features, such as searching for a font based on a raster image: - -. Start *GNOME Software* by choosing *Software* from the Start menu. -. Search for 'Fontmatrix'. -. Choose 'Fontmatrix' from the results and click 'Install'. - - -.Procedure - -. To install fonts from the Fedora repository: -.. Run the following command to list available fonts: -+ ----- -$ dnf search font ----- -.. Copy the name of the font you want to install. -.. Run the following command to install the font: -+ ----- -$ dnf install ----- -+ -For example: -+ ----- -$ dnf install google-noto-mono-fonts.noarch ----- -. To install fonts from the filesystem: -.. Locate the font file using the *Nautilus* file manager. -.. Double-click the font file to open the font in *GNOME Font Viewer*. A preview of the font is displayed. -.. Click *Install* to install the font. - - -[NOTE] -==== -If you use *GNOME Font Viewer* to install fonts, those fonts are only available to the current user. -==== - -.Additional resources - -* The help included with *Fontmatrix* provides an introduction to the Fedora font system. -* link:https://docs-old.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-x-fonts.html[Fedora documentation] regarding fonts. diff --git a/modules/ROOT/pages/_partials/proc_package-browsing-installing-software.adoc b/modules/ROOT/pages/_partials/proc_package-browsing-installing-software.adoc deleted file mode 100644 index 448293d..0000000 --- a/modules/ROOT/pages/_partials/proc_package-browsing-installing-software.adoc +++ /dev/null @@ -1,18 +0,0 @@ -[[package-browsing-installing]] -= Browsing and installing software on Fedora - -You can use a graphical utility to browse the available software packages. When you find the software that you want, you can use the utility to install it on your Fedora system. - -.Before you start - -To install any packages on your Fedora system, you need to have *root* privileges. - -.Procedure - -. On your GNOME desktop, select the *Activities* menu and then click the image:packages_icon_software.png[Software] icon. -. Find a software package in one of the following ways: -** Click on one of the listed categories, for example, *Work*. Then review the suggested software in the category. For example, in the "Work" category, you are able to select different applications: *Calendar*, *Database*, *Finance*, *Word Processor*. -** Choose one of the Editor's Picks or other recommended software in the window. -** Click the image:packages_icon_search.png[Search] icon, then enter a keyword or the name of the application. Review the suggested packages. -. Click a package to read its description. -. To install the package, click the *Install* button. When prompted, provide the root password. diff --git a/modules/ROOT/pages/_partials/proc_package-enabling-third-party.adoc b/modules/ROOT/pages/_partials/proc_package-enabling-third-party.adoc deleted file mode 100644 index d618cac..0000000 --- a/modules/ROOT/pages/_partials/proc_package-enabling-third-party.adoc +++ /dev/null @@ -1,30 +0,0 @@ -= Enabling third-party repositories -[[package-enabling-third-party]] - -You can install software packages from repositories that are not supported by the Fedora project, known as third-party repositories. - - -== RPM Fusion - -The most commonly used third-party repository is https://rpmfusion.org/[RPM Fusion]. It provides packages that can not be included in Fedora because of US software patents or other similar reasons. Among other things, RPM Fusion provides packages necessary for viewing media in many common formats. RPM Fusion packages are extensively tested, but they are not supported by the Fedora project. - - -== Copr - -A set of repositories for Fedora is known as https://copr.fedorainfracloud.org/[Copr]. Developers can provide packages in Copr repositories for software that is not at present included in Fedora. *These packages might be untested.* - - -== Application-specific repositories - -Certain non-free applications for Linux, such as Google Chrome or Skype, provide their own repositories for Fedora. - -To install software from a third-party repository, you must first _enable_ that repository. Then the packages from the repository become available in the command line and graphical package management tools. - -IMPORTANT: If you enable a third-party repository, packages that you did not explicitly select might also be installed from the repository. Do not enable repositories that you do not trust. The Fedora project does not support third-party repositories. - -.Procedure - -To enable a third-party repository, follow the instructions provided by the repository. For example: - -* For RPM Fusion, https://rpmfusion.org/Configuration -* For Copr repositories, https://docs.pagure.org/copr.copr/how_to_enable_repo.html diff --git a/modules/ROOT/pages/_partials/proc_package-install-command-line.adoc b/modules/ROOT/pages/_partials/proc_package-install-command-line.adoc deleted file mode 100644 index 57b6271..0000000 --- a/modules/ROOT/pages/_partials/proc_package-install-command-line.adoc +++ /dev/null @@ -1,25 +0,0 @@ -[[proc_package-install-command-line]] -= Installing software packages using the command line - -You can install packages in Fedora using the DNF utility. - -.Before you begin - -You must execute the command with *root* privileges. Use one of the following methods: - -* Prefix the command with `sudo` and provide your user password. The `sudo` command must be enabled for your user. -* Use the `su` command and provide the root password to switch to a root prompt in a terminal window. -* Log in as `root` on a virtual console. - -You must know the name of the package. Any dependencies will be installed automatically. - -.Procedure - -. Run the command: -+ ----- -# dnf install ----- -+ -where `` is the name of the package. -. Answer `y` to any prompts, if necessary. diff --git a/modules/ROOT/pages/_partials/proc_package-searching-web-apps.adoc b/modules/ROOT/pages/_partials/proc_package-searching-web-apps.adoc deleted file mode 100644 index a3744cb..0000000 --- a/modules/ROOT/pages/_partials/proc_package-searching-web-apps.adoc +++ /dev/null @@ -1,15 +0,0 @@ -[[package-searching-web]] -= Searching for Linux software alternatives on the Web - -To complete your tasks on a Linux system, you need to find the software applications that fit your needs. If you are switching from another operating system, you might need to find replacements for the software that you used before. - -Most applications available on Linux are open-source software. You can use open-source software without acquiring any licenses. Moreover, widespread open-source software is usually available in the official Fedora repository, so you can install it easily. - -.Procedure - -Access the following websites to review Linux alternatives to popular software packages: - -* https://www.linuxalt.com/ -* https://opensource.com/alternatives -* https://www.osalt.com/ -* https://alternativeto.net/