Fixed various minor issues.
This commit is contained in:
Peter Boy
parent
8e90245140
commit
2f1aee9155
10 changed files with 100 additions and 230 deletions
|
|
@ -106,9 +106,6 @@
|
|||
** xref:uefi-with-qemu.adoc[Using UEFI with QEMU]
|
||||
|
||||
//FIXME * xref:debug-wayland-problems.adoc[How to debug Wayland problems] - note: maintained on wiki, does not fit quick-docs IMHO
|
||||
//FIXME * xref:fedora-life-cycle.adoc[Fedora Release Life Cycle] - note: maintained on wiki, does not fit quick-docs IMHO
|
||||
|
||||
|
||||
|
||||
* xref:publish-rpm-on-copr.adoc[Publishing your software on Copr]
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,13 @@
|
|||
= Adding a user to sudoers
|
||||
Mirek Jahoda; Ankur Sinha ; The Fedora Docs Team
|
||||
:revnumber: F38
|
||||
:revdate: 2023-08-06
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
:category: Administration
|
||||
:tags: How-to TAG_02 TAG_03 ... TAG_n
|
||||
|
||||
|
||||
One of the most common operations that administrators want to accomplish when managing `sudo` permissions is to grant a new user general `sudo` access. This is helpful if you want to give an account full administrative access to the system.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,15 +1,21 @@
|
|||
[id='sec-Using-AIDE']
|
||||
= Checking Integrity With *AIDE*
|
||||
:experimental:
|
||||
include::{partialsdir}/attributes.adoc[]
|
||||
Héctor Louzao; The Fedora Documentation Team
|
||||
:revnumber: F38
|
||||
:revdate: 2023-08-09
|
||||
|
||||
:page-aliases: using-aide.adoc
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
:category: Administration
|
||||
:tags: How-to Monitoring
|
||||
|
||||
[abstract]
|
||||
Advanced Intrusion Detection Environment (AIDE) is a utility that creates a database of files on the system, and then uses that database to ensure file integrity and detect system intrusions.
|
||||
|
||||
== Installing *AIDE*
|
||||
|
||||
. To install the _aide_ package:
|
||||
+
|
||||
|
||||
[source,shell,subs="attributes"]
|
||||
----
|
||||
$ sudo dnf install aide
|
||||
|
|
@ -17,7 +23,6 @@ $ sudo dnf install aide
|
|||
|
||||
. To generate an initial database:
|
||||
+
|
||||
|
||||
[source,shell,subs="attributes"]
|
||||
----
|
||||
$ sudo aide --init
|
||||
|
|
@ -58,7 +63,9 @@ $ sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz
|
|||
. To change the location of the *AIDE* database, edit the `/etc/aide.conf` file and modify the `DBDIR` value. For additional security, store the database, configuration, and the `/usr/sbin/aide` binary file in a secure location such as a read-only media.
|
||||
+
|
||||
|
||||
IMPORTANT: To avoid SELinux denials after the AIDE database location change, update your SELinux policy accordingly. See the link:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/[SELinux User's and Administrator's Guide] for more information.
|
||||
IMPORTANT: To avoid SELinux denials after the AIDE database location change, update your SELinux policy accordingly. See the xref:changing-selinux-states-and-modes.adoc[Changing SELinux states and modes] guide for more information.
|
||||
|
||||
//link:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/[SELinux User's and Administrator's Guide] for more information.
|
||||
|
||||
== Performing Integrity Checks
|
||||
|
||||
|
|
@ -85,7 +92,7 @@ f++++++++++++++++: /etc/cups/subscriptions.conf.O
|
|||
[output truncated]
|
||||
----
|
||||
|
||||
At a minimum, *AIDE* should be configured to run a weekly scan. At most, *AIDE* should be run daily. For example, to schedule a daily execution of AIDE at _04:05_ a.m. using the *cron* command, see the xref:f{MAJOROSVER}@fedora:system-administrators-guide:monitoring-and-automation/Automating_System_Tasks.adoc[Automating System Tasks] chapter in the System Administrator's Guide.
|
||||
At a minimum, *AIDE* should be configured to run a weekly scan. At most, *AIDE* should be run daily. For example, to schedule a daily execution of AIDE at _04:05_ a.m. use the *cron* command.
|
||||
|
||||
Add the following line to the `/etc/crontab` file:
|
||||
|
||||
|
|
@ -1,5 +1,9 @@
|
|||
= How to debug Wayland problems
|
||||
|
||||
//FIXME * xref:debug-wayland-problems.adoc[How to debug Wayland problems] - note: maintained on wiki, does not fit quick-docs IMHO
|
||||
|
||||
// Someone commented it out in nav.adoc (as of 2023-08-06)
|
||||
|
||||
'''
|
||||
|
||||
[IMPORTANT]
|
||||
|
|
|
|||
|
|
@ -1,5 +1,12 @@
|
|||
= DNF System Upgrade
|
||||
Michael Wu; Anthony McGlone; The Fedora Docs team
|
||||
:revnumber: F38
|
||||
:revdate: 2023-05-04
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
:category: Administration
|
||||
:tags: How-to Upgrade
|
||||
|
||||
link:++https://github.com/rpm-software-management/dnf-plugins-extras++[`dnf-plugin-system-upgrade`] is a plugin for the xref:dnf.adoc[DNF] package manager and is used to upgrade your system to the current release of Fedora.
|
||||
For Fedora Silverblue and Fedora CoreOS, which use rpm-ostree, you may refer to link:++https://coreos.github.io/rpm-ostree/administrator-handbook/++[rpm-ostree documentation] for details.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,13 @@
|
|||
= APT command equivalents on Fedora with DNF
|
||||
Michal Ambroz; Christopher Engelhard ; The Fedora Docs team
|
||||
:revnumber: F37
|
||||
:revdate: 2023-02-03
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
:category: Administration
|
||||
:tags: How-to
|
||||
|
||||
|
||||
APT is the package manager/dependency solver for the Debian ecosystem, i.e. it manages `.deb` packages installed by the DPKG program. Fedora software is based on `.rpm` packages, and thus uses DNF, the package manager/dependency solver for the RPM program, instead. This document gives a brief overview of the most common APT commands one might find in tutorials and their DNF equivalents.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,17 @@
|
|||
= Using the DNF software package manager
|
||||
Weverton do Couto Timoteo; JetStream ; The Fedora Docs team
|
||||
:revnumber: Fxy
|
||||
:revdate: 2022-10-05
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
:category: Administration
|
||||
:tags: How-to DNF
|
||||
|
||||
[abstract]
|
||||
DNF is a software package manager that installs, updates, and removes packages on Fedora and is the successor to YUM (Yellow-Dog Updater Modified).
|
||||
|
||||
|
||||
DNF makes it easy to maintain packages by automatically checking for dependencies and determines the actions required to install packages.
|
||||
This method eliminates the need to manually install or update the package, and its dependencies, using the `rpm` command.
|
||||
DNF is now the default software package management tool in Fedora.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,16 @@
|
|||
= Disk Encryption User Guide
|
||||
|
||||
Mat McCabe ; Mauricio Tavares; The Fedora Docs team
|
||||
:revnumber: F37
|
||||
:revdate: 2023-01-05
|
||||
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
:category: Administration
|
||||
:tags: How-to Encryption LUKS
|
||||
|
||||
[abstract]
|
||||
|
||||
|
||||
=== Contents
|
||||
. <<What is block device encryption?>>
|
||||
. <<Encrypting block devices using dm-crypt/LUKS>>
|
||||
|
|
|
|||
|
|
@ -1,145 +0,0 @@
|
|||
= Fedora Release Life Cycle
|
||||
|
||||
include::{partialsdir}/unreviewed-message.adoc[]
|
||||
|
||||
////
|
||||
The Fedora Project releases a new version of Fedora approximately every 6 months and provides updated packages (maintenance) to these releases for approximately 13 months. This allows users to "skip a release" while still being able to always have a system that is still receiving updates.
|
||||
|
||||
[[development-schedule]]
|
||||
== Development Schedule
|
||||
|
||||
We say _approximately every 6 months_ because like many things, they don't always go exactly as planned. The schedule is not strictly time-based, but a hybrid of time and quality. The milestone releases are QA:Release_validation_test_plan[tested] for compliance with the https://fedoraproject.org/wiki/Fedora_Release_Criteria[Fedora Release Criteria], and releases will be delayed if this is not the case.
|
||||
|
||||
The schedule for the release currently under development, , is on its https://fedoraproject.org/wiki/Releases/{{FedoraVersion[|next}}/Schedule| release schedule] page. Beta, and General Availability (final) releases happen at 14:00 UTC.
|
||||
|
||||
[[development-planning]]
|
||||
=== Development Planning
|
||||
|
||||
Fedora development planning is handled by the https://fedoraproject.org/wiki/Changes/Policy[Release Planning Process]. So-called _Changes_ are proposed, initially reviewed, and monitored through the development process by the https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[engineering steering committee].
|
||||
|
||||
[[development-process]]
|
||||
=== Development Process
|
||||
|
||||
Fedora uses a system involving two 'development' trees. https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide] is a constantly rolling development tree. No releases are built directly from Rawhide. Approximately 10 weeks before the planned date of a Fedora release, a tree for that release is "https://fedoraproject.org/wiki/Releases/Branched[Branched]" from the Rawhide tree. At that point the Rawhide tree is moving towards the release _after_ the new Branched release, and the pending release is stabilized in the Branched tree.
|
||||
|
||||
After the https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling[Bodhi activation point], the Bodhi system is permanently active on the Branched release (all the way until it goes EOL), and requirements for updates to be marked as _stable_ are set out in the https://fedoraproject.org/wiki/Updates_Policy[Updates Policy]. Packages must go through the https://fedoraproject.org/wiki/Repositories#updates-testing[_updates-testing_] repository for the release before entering its https://fedoraproject.org/wiki/Repositories#stable[_stable_] repository, according to rules defined in the updates policy: these rules tighten gradually from Beta through to post-GA (Final), but the basic process does not change.
|
||||
|
||||
For some time prior to a milestone (Beta, Final) release a https://fedoraproject.org/wiki/Milestone_freezes[freeze] is in effect which prevents packages moving from _updates-testing_ to _stable_ except in accordance with the QA:SOP_blocker_bug_process[blocker] and QA:SOP_freeze_exception_bug_process[freeze exception] bug policies. This freeze is lifted once the milestone is finished, and so packages begin to move from _updates-testing_ to _stable_ as normal again, until the next milestone's freeze date.
|
||||
|
||||
[[schedule-methodology]]
|
||||
=== Schedule Methodology
|
||||
|
||||
Fedora release schedules are proposed by the https://fedoraproject.org/wiki/Fedora_Program_Management[Fedora Program Manager] and ratified by the https://fedoraproject.org/wiki/FESCo[Fedora Engineering Steering Committee (FESCo)], with input from other groups. FESCo is responsible for overseeing the technical direction of the Fedora distribution. A core schedule is created using the key tasks listed below. Detailed team schedules are built around these dates.
|
||||
|
||||
_Note: When referring to *Beta/Final Target*, we refer to an planned date. When referring to *Beta/Final release* only, we refer to a date the release has actually happened._
|
||||
|
||||
[cols=",,",options="header",]
|
||||
|=======================================================================
|
||||
|Task/Milestone |Start Day (Tuesdays or Thursdays) |Length
|
||||
|Planning and Development |_Branch point_ of _previous release_ plus *one day* |Variable
|
||||
|
||||
|https://fedoraproject.org/wiki/Changes/Policy#For_Developers[Changes Checkpoint: Proposal deadline for Changes requiring _Mass rebuild_] |Tue: _Mass rebuild_ minus *3 weeks* |n/a
|
||||
|
||||
|https://fedoraproject.org/wiki/Changes/Policy#For_Developers[Changes Checkpoint: Proposal deadline for System Wide Changes] |Tue: _Mass rebuild_ minus *1 week* |n/a
|
||||
|
||||
|*Mass rebuild* |_Branch point_ minus *5 weeks* |Until _Branch point_
|
||||
|
||||
|https://fedoraproject.org/wiki/Changes/Policy#For_Developers[Changes Checkpoint: Proposal deadline for Self Contained Changes] |Tue: _Branch point_ minus *3 weeks* |n/a
|
||||
|
||||
|*https://fedoraproject.org/wiki/Releases/Branched[Branch point]* |Tue: _Preferred Beta Release Target_ minus *5 weeks* |n/a
|
||||
|
||||
|https://fedoraproject.org/wiki/Changes/Policy#For_Developers[Changes Checkpoint: Completion deadline (testable)] |Tue: *Same day* as _Branch point_ |N/A
|
||||
|
||||
|String Freeze |Tue: _Branch point_ plus *1 week* |https://fedoraproject.org/wiki/Software_String_Freeze_Policy[Software String Freeze Policy] in effect until _Final Release (GA)_
|
||||
|
||||
|https://fedoraproject.org/wiki/Updates_Policy#Bodhi_activation[Bodhi activation point] |Tue: _Preferred Beta Target_ minus *3 weeks*, *Same day* as _Beta Freeze_ |Bodhi enabled and Updates_Policy requirements in effect until _EOL_
|
||||
|
||||
|https://fedoraproject.org/wiki/Milestone_freezes[Beta Freeze] |Tue: _Preferred Beta Target_ minus *3 weeks* |QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until _Beta Release_
|
||||
|
||||
|https://fedoraproject.org/wiki/Changes/Policy#For_Developers[Changes Checkpoint: 100% code complete deadline ] |Tue: *Same day* as _Beta Freeze_ |N/A
|
||||
|
||||
|QA:SOP_compose_request[Beta release candidates] |Any time after _Beta Freeze_ |Until _Beta Release_
|
||||
|
||||
|Beta Go_No_Go_Meeting |*Thu* @ 13:00 E\{D,S}T: planned _Preferred Beta Target_ *minus five days* (repeats if No-Go) |n/a
|
||||
|
||||
|*Preferred Beta Target* |Tue: _Preferred Final Target_ minus *5 weeks* |Live until _GA release_
|
||||
|
||||
|Beta Target #1 |Tue: _Preferred Beta Target_ plus *1 week*, _Preferred Final Target_ minus *4 weeks* |n/a
|
||||
|
||||
|https://fedoraproject.org/wiki/Milestone_freezes[Final Freeze] |Tue: _Preferred Final Target_ minus *2 weeks* |QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until _Final Release (GA)_
|
||||
|
||||
|QA:SOP_compose_request[Final release candidates] |Any time after _Final Freeze_ |Until _Final Release (GA)_
|
||||
|
||||
|Final Go_No_Go_Meeting |*Thu* @ 13:00 E\{D,S}T: planned _Final Release (GA)_ *minus five days* (repeats if No-Go) |n/a
|
||||
|
||||
|*Preferred Final Target* |Tue: *Primary date* from which rest of schedule derives + This date is either the Tuesday before May 1st or October 31st. |n/a
|
||||
|
||||
|Final Target #1 |Tue: _Preferred Final Target_ plus *1 week* |n/a
|
||||
|
||||
|Maintenance |Tue: *Same day* as _Final Release (GA)_ |~**13 Months**
|
||||
|
||||
|End of Life |_Final Release (GA) of next-but-one release_ plus *one month* |n/a
|
||||
|=======================================================================
|
||||
|
||||
[[development-schedule-rationale]]
|
||||
=== Development Schedule Rationale
|
||||
|
||||
Fedora generally develops new releases over a six month period to provide a regular and predictable release schedule. The bi-annual targeted release dates are _May Day_ (May 1st) and _Halloween_ (October 31) making them easy to remember and for avoiding significant holiday breaks. Changes to this standard must be approved by the community-elected https://fedoraproject.org/wiki/FESCo[Fedora Engineering Steering Committee (FESCo)].
|
||||
|
||||
A six month release schedule also follows the precedence of Red Hat Linux (precursor to Fedora). Former Red Hat software engineer Havoc Pennington offers a historical perspective http://article.gmane.org/gmane.linux.redhat.fedora.advisory-board/1475/[here]. GNOME started following a time based release based on the ideas and success of Red Hat Linux and other distributions following Fedora having adopted a similar release cycle. Several other major components, including the Linux kernel, Openoffice.org, Xorg, have started following a time based release schedule. While the exact release schedules vary between these components and other upstream projects, the interactions between these components and Fedora makes a six month time based release schedule a good balance.
|
||||
|
||||
Although due to how planning process and release validation works, Fedora is not a strictly time based distribution, but uses combination of both time and feature based release paradigms. This way we can react to bigger changes aka new installed, way how we release bits (Fedora.Next) etc.
|
||||
|
||||
[[schedule-contingency-planning]]
|
||||
=== Schedule Contingency Planning
|
||||
|
||||
If _Mass rebuild_ is not completed on time, all the subsequent milestones starting with _Branch point_ are pushed back for one week until the _Mass rebuild_ is completed.
|
||||
|
||||
If the Beta Go/No-Go Meeting results in a "No Go" determination, rescheduling of the milestone and subsequent milestones follows these rules:
|
||||
|
||||
* Slip of the Beta from the Preferred Target to Target #1 does not affect Final Release (GA) date. The Final Release (GA) date remains on _Preferred Final Target_.
|
||||
* Slip of the Beta to Target #1 adds a new _Beta Target #2_ and Final Release (GA) slips to _Final Target #1_ (and we don't yet add a _Final Target #2_).
|
||||
* Slip of the Beta past Target #N (where N >= 2) adds a new _Beta Target #(N+1)_ and also adds a new _Final Target #N_
|
||||
|
||||
If the Final Go_No_Go_Meeting results in a "No Go" determination, that milestone and subsequent milestones will be pushed back by one week.
|
||||
|
||||
One week is added to the schedule to maintain the practice of releasing on Tuesdays. Tuesdays are the designated release day because they are good days for news coverage and correspond to the established day we synchronize our content with the mirrors that carry our releases. Be aware of holidays and of possible PR conflicts (contact Fedora PR) with the new proposed final date.
|
||||
|
||||
Go/No Go meetings receive input from representatives of https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[FESCo],
|
||||
https://fedoraproject.org/wiki/ReleaseEngineering[Release Engineering], and https://fedoraproject.org/wiki/QA[Quality Assurance].
|
||||
|
||||
[[maintenance-schedule]]
|
||||
== Maintenance Schedule
|
||||
|
||||
We say maintained for _approximately 13 months_ because the supported period for releases is dependent on the date the release under development goes final. As a result, _Release X_ is supported until one month after the release of _Release X+2_.
|
||||
|
||||
This translates into:
|
||||
|
||||
* Fedora 26 will be maintained until 1 month after the release of Fedora 28.
|
||||
* Fedora 27 will be maintained until 1 month after the release of Fedora 29.
|
||||
|
||||
[[maintenance-schedule-rationale]]
|
||||
=== Maintenance Schedule Rationale
|
||||
|
||||
Fedora is https://fedoraproject.org/wiki/Objectives[focused] on free and open source software https://fedoraproject.org/wiki/Red_Hat_contributions[innovations] and moves quickly. If you want a distribution that moves slower but has a longer lifecycle, Red Hat Enterprise Linux, which is derivative of Fedora or free rebuilds of that such as CentOS might be more suitable for you. Refer to the RHEL page for more details.
|
||||
|
||||
Historically, the Fedora Project has found that supporting two releases plus Rawhide and the pre-release Branched code to be a manageable work load.
|
||||
|
||||
[[end-of-life-eol]]
|
||||
== End of Life (EOL)
|
||||
|
||||
When a release reaches the point where it is no longer supported when no updates are created for it, then it is considered _End of Life_ (EOL). Branches for new packages in the SCM are not allowed for distribution X after the Fedora X+2 release and new builds are no longer allowed.
|
||||
|
||||
The tasks performed at EOL are documented in the https://fedoraproject.org/wiki/End_of_life_SOP[End of life SOP].
|
||||
|
||||
[[additional-release-schedule-information]]
|
||||
== Additional Release Schedule Information
|
||||
|
||||
* Overview of Releases, including currently supported releases
|
||||
* https://fedoraproject.org/wiki/End_of_life[Unsupported Releases]
|
||||
* https://fedoraproject.org/wiki/Releases/HistoricalSchedules[Historical Release Information]
|
||||
|
||||
See a typo, something missing or out of date, or anything else which can be improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.
|
||||
////
|
||||
|
||||
This page is maintained on link:https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Project Wiki]
|
||||
|
|
@ -1,12 +1,22 @@
|
|||
= Fedora on Raspberry Pi
|
||||
Flo H; jtagcat; The Fedora Docs Team
|
||||
:revnumber: F38
|
||||
:revdate: 2023-08-05
|
||||
|
||||
The link:https://www.raspberrypi.org[Raspberry Pi] is a credit card-sized ARM based single board computer (SBC).
|
||||
// Optional free form useful additional information as comment
|
||||
|
||||
link:https://fedoraproject.org/wiki/Changes/RaspberryPi4[The Raspberry Pi 4 is officially supported from Fedora release 37 onwards]. This includes hardware accelerated graphics, for which OSS support was previously lacking.
|
||||
:category: Installation
|
||||
:tags: How-to ARM-SBC Raspberry-Pi
|
||||
|
||||
|
||||
[abstract]
|
||||
The link:https://www.raspberrypi.org[Raspberry Pi] is a credit card-sized ARM based single board computer (SBC). This documentation describes how to get started
|
||||
|
||||
The Raspberry Pi 4 is link:https://fedoraproject.org/wiki/Changes/RaspberryPi4[ officially supported] from Fedora release 37 onwards. This includes hardware accelerated graphics, for which OSS support was previously lacking.
|
||||
|
||||
Support for older Raspberry Pi models (2B and 3-series of devices including the 3B, 3B+, 3A+, 3CM and 3CM+) is available since Fedora Linux 29 and later releases. But Fedora decided to cut off support for (32 bit) armv7 / armhfp.
|
||||
|
||||
This documentation describes how to get started, and includes a Frequently Asked Questions (FAQ) section at the end of the document about what is supported, and what is not.
|
||||
At the end of the document you find a Frequently Asked Questions (FAQ) section about what is supported, and what is not.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
|
|
@ -27,22 +37,14 @@ This documentation describes how to get started, and includes a Frequently Asked
|
|||
|
||||
The procedure for installing Fedora ARM on a microSD in preparation for using Fedora on a Raspberry Pi depends on your computers' operating system (Microsoft Windows, macOS, or Linux).
|
||||
|
||||
* For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}>>.
|
||||
* For users of other Linux distributions, see: <<installing-fedora-on-a-raspberry-pi-for-linux-users_{context}>>.
|
||||
* For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}>>.
|
||||
* For macOS users, see: <<installing-fedora-on-a-raspberry-pi-for-macos-users_{context}>>.
|
||||
* For Fedora users, see: xref:raspberry-pi.adoc#_installing_fedora_on_a_raspberry_pi_using_the_fedora_arm_installer[Installing Fedora on a Raspberry Pi using the Fedora ARM installer].
|
||||
* For users of other Linux distributions, see:
|
||||
xref:raspberry-pi.adoc#_installing_fedora_on_a_raspberry_pi_for_linux_users[Installing Fedora on a Raspberry Pi for Linux users].
|
||||
* For Microsoft Windows users, see: xref:raspberry-pi.adoc#_installing_fedora_on_a_raspberry_pi_for_microsoft_windows_users[Installing Fedora on a Raspberry Pi for Microsoft Windows users].
|
||||
* For macOS users, see: xref:raspberry-pi.adoc#_installing_fedora_on_a_raspberry_pi_for_macos_users[Installing Fedora on a Raspberry Pi for macOS users].
|
||||
|
||||
// The following include statements pull in the module files that comprise the assembly. Include any combination of concept, procedure, or reference modules required to cover the user story. You can also include other assemblies.
|
||||
|
||||
// [leveloffset=+1] ensures that when a module starts with a level-1 heading (= Heading), the heading will be interpreted as a level-2 heading (== Heading) in the assembly.
|
||||
|
||||
// include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer.adoc[leveloffset=+1]
|
||||
|
||||
== Installing Fedora on a Raspberry Pi using the Fedora ARM installer
|
||||
// Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.
|
||||
|
||||
:experimental:
|
||||
include::{partialsdir}/attributes.adoc[]
|
||||
|
||||
This procedure shows Fedora users how to add Fedora ARM to a microSD for use with a Raspberry Pi using the Fedora ARM installer.
|
||||
|
||||
|
|
@ -75,7 +77,7 @@ $ dnf install -y arm-image-installer
|
|||
Where:
|
||||
+
|
||||
* The `__</path/to/fedora_image>__` has the format `Fedora-__<spin>__-armhfp-__<fedora_version>__-sda.raw.xz`.
|
||||
** For example: `/home/user/Downloads/Fedora-Server-armhfp-{MAJOROSVER}-1.1-sda.raw.xz`.
|
||||
** For example: `/home/user/Downloads/Fedora-Server-armhfp-35-1.1-sda.raw.xz`.
|
||||
* `__<RPi_Version>__` is:
|
||||
** `rpi2` for a Raspberry Pi 2.
|
||||
** `rpi3` for a Raspberry Pi 3.
|
||||
|
|
@ -100,11 +102,9 @@ $ cat /usr/share/doc/arm-image-installer/SUPPORTED-BOARDS
|
|||
|
||||
Your microSD card is ready to be used with your Raspberry Pi.
|
||||
|
||||
ifeval::["{context}" == "rpi"]
|
||||
._Next Steps_
|
||||
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].
|
||||
endif::[]
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:raspberry-pi.adoc#_booting_fedora_on_a_raspberry_pi_for_the_first_time[Booting Fedora on a Raspberry Pi for the first time].
|
||||
|
||||
._Additional Resources_
|
||||
|
||||
|
|
@ -115,7 +115,6 @@ endif::[]
|
|||
** link:https://web.libera.chat/?channels=#fedora-arm[IRC via the #fedora-arm channel on Libera.Chat]
|
||||
|
||||
|
||||
|
||||
== Installing Fedora on a Raspberry Pi for Linux users
|
||||
|
||||
This procedure shows Linux users how to add Fedora ARM to a microSD for use with a Raspberry Pi.
|
||||
|
|
@ -189,11 +188,9 @@ Ideally we would like this to happen automatically (great community project idea
|
|||
|
||||
Your microSD card is ready to be used with your Raspberry Pi.
|
||||
|
||||
ifeval::["{context}" == "rpi"]
|
||||
.Next Steps
|
||||
.Next steps
|
||||
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].
|
||||
endif::[]
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:raspberry-pi.adoc#_booting_fedora_on_a_raspberry_pi_for_the_first_time[Booting Fedora on a Raspberry Pi for the first time].
|
||||
|
||||
.Additional Resources
|
||||
|
||||
|
|
@ -205,14 +202,8 @@ endif::[]
|
|||
|
||||
|
||||
|
||||
|
||||
//include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users.adoc[leveloffset=+1]
|
||||
|
||||
== Installing Fedora on a Raspberry Pi for Microsoft Windows users
|
||||
|
||||
:experimental:
|
||||
include::{partialsdir}/attributes.adoc[]
|
||||
|
||||
This procedure shows Microsoft Windows users how to add Fedora ARM to a microSD for use with a Raspberry Pi.
|
||||
|
||||
._Prerequisites_
|
||||
|
|
@ -234,7 +225,7 @@ For example:
|
|||
+
|
||||
[source,shell,subs="attributes"]
|
||||
----
|
||||
> "C:\Program Files\7-Zip\7z.exe" x -y "C:\Users\admin\Downloads\Fedora-Server-armhfp-{MAJOROSVER}-1.1-sda.raw.xz"
|
||||
> "C:\Program Files\7-Zip\7z.exe" x -y "C:\Users\admin\Downloads\Fedora-Server-armhfp-35-1.1-sda.raw.xz"
|
||||
----
|
||||
|
||||
. Follow the instructions provided by the Raspberry Pi foundation for writing an image to a microSD card from Microsoft Windows: link:https://www.raspberrypi.org/documentation/installation/installing-images/windows.md[Raspberry Pi Foundation: Installing operating system images using Windows].
|
||||
|
|
@ -246,11 +237,9 @@ The `.img` and `.raw` extensions are used interchangeably for RAW file. Where th
|
|||
|
||||
Your microSD card is ready to be used with your Raspberry Pi.
|
||||
|
||||
ifeval::["{context}" == "rpi"]
|
||||
._Next Steps_
|
||||
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].
|
||||
endif::[]
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:raspberry-pi.adoc#_booting_fedora_on_a_raspberry_pi_for_the_first_time[Booting Fedora on a Raspberry Pi for the first time].
|
||||
|
||||
._Additional Resources_
|
||||
|
||||
|
|
@ -260,12 +249,8 @@ endif::[]
|
|||
** link:https://web.libera.chat/?channels=#fedora-arm[IRC via the #fedora-arm channel on Libera.Chat]
|
||||
|
||||
|
||||
|
||||
// include::{partialsdir}/proc_installing-fedora-on-a-raspberry-pi-for-macos-users.adoc[leveloffset=+1]
|
||||
== Installing Fedora on a Raspberry Pi for macOS users
|
||||
|
||||
include::{partialsdir}/attributes.adoc[]
|
||||
|
||||
This procedure shows macOS users how to add Fedora ARM to a microSD for use with a Raspberry Pi.
|
||||
|
||||
._Prerequisites_
|
||||
|
|
@ -287,7 +272,7 @@ For example:
|
|||
+
|
||||
[source,shell,subs="attributes"]
|
||||
----
|
||||
$ unar Fedora-Server-armhfp-{MAJOROSVER}-1.1-sda.raw.xz
|
||||
$ unrar Fedora-Server-38-1.6.aarch64.raw.xz
|
||||
----
|
||||
|
||||
. Follow the instructions provided by the Raspberry Pi foundation for writing an image to a microSD card from macOS: link:https://www.raspberrypi.org/documentation/installation/installing-images/mac.md[Raspberry Pi Foundation: Installing operating system images on Mac OS].
|
||||
|
|
@ -299,11 +284,9 @@ The `.img` and `.raw` extensions are used interchangeably for RAW file. Where th
|
|||
|
||||
Your microSD card is ready to be used with your Raspberry Pi.
|
||||
|
||||
ifeval::["{context}" == "rpi"]
|
||||
._Next Steps_
|
||||
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:booting-fedora-on-a-raspberry-pi-for-the-first-time_{context}[].
|
||||
endif::[]
|
||||
For information on starting and configuring Fedora on Raspberry Pi, see: xref:raspberry-pi.adoc#_booting_fedora_on_a_raspberry_pi_for_the_first_time[Booting Fedora on a Raspberry Pi for the first time]..
|
||||
|
||||
._Additional Resources_
|
||||
|
||||
|
|
@ -313,16 +296,9 @@ endif::[]
|
|||
** link:https://web.libera.chat/?channels=#fedora-arm[IRC via the #fedora-arm channel on Libera.Chat]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
include::{partialsdir}/proc_booting-fedora-on-a-raspberry-pi-for-the-first-time.adoc[leveloffset=+1]
|
||||
|
||||
== Booting Fedora on a Raspberry Pi for the first time
|
||||
|
||||
//include::{partialsdir}/attributes.adoc[]
|
||||
|
||||
Follow these steps to boot Fedora ARM on your Raspberry Pi. If your MicroSD card does not have enough room, you need to resize the main partition after the initial setup. See <<resizing-the-main-partition-of-the-microsd-card-after-setup_{context}>>.
|
||||
Follow these steps to boot Fedora ARM on your Raspberry Pi. If your MicroSD card does not have enough room, you need to resize the main partition after the initial setup. See <<resizing-the-main-partition-of-the-microsd-card-after-setup>>.
|
||||
|
||||
._Prerequisites_
|
||||
|
||||
|
|
@ -343,7 +319,7 @@ Follow these steps to boot Fedora ARM on your Raspberry Pi. If your MicroSD card
|
|||
|
||||
The system displays a login prompt or getting started guide (depending on your Desktop/SPIN).
|
||||
|
||||
[id='resizing-the-main-partition-of-the-microsd-card-after-setup_{context}']
|
||||
[id='resizing-the-main-partition-of-the-microsd-card-after-setup']
|
||||
._Resizing the main partition of the microSD card after setup (if required)_
|
||||
|
||||
Follow these steps to resize the partitions for Fedora ARM on Raspberry Pi:
|
||||
|
|
@ -362,28 +338,15 @@ $ xfs_growfs -d /
|
|||
|
||||
._Additional Resources_
|
||||
|
||||
* For information on configuring Fedora, including installing programs and updates, see: xref:f{MAJOROSVER}@fedora:system-administrators-guide:index.adoc[Fedora Docs: System Administrator’s Guide]
|
||||
* For assistance or support, see:
|
||||
** link:https://ask.fedoraproject.org/[Ask Fedora]
|
||||
** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]
|
||||
** irc://irc.freenode.net/#fedora-arm[IRC via the #fedora-arm channel on Freenode]
|
||||
|
||||
|
||||
|
||||
include::{partialsdir}/ref_frequently-asked-questions_-installing-fedora-on-a-raspberry-pi.adoc[leveloffset=+1]
|
||||
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// <List assemblies here, each on a new line>
|
||||
|
||||
// Base the file name and the ID on the module title. For example:
|
||||
// * file name: my-reference-a.adoc
|
||||
// * ID: [id='my-reference-a']
|
||||
// * Title: = My reference A
|
||||
|
||||
// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
|
||||
[id='reference-material_{context}']
|
||||
// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
|
||||
[id='reference-material']
|
||||
|
||||
[[sect-frequently-asked-questions]]
|
||||
== Fedora on Raspberry Pi: Frequently Asked Questions
|
||||
//In the title of a reference module, include nouns that are used in the body text. For example, "Keyboard shortcuts for ___" or "Command options for ___." This helps readers and search engines find the information quickly.
|
||||
|
|
@ -398,10 +361,10 @@ Common causes of the rainbow display include:
|
|||
|
||||
* There's no operating system installed. Check that an operating system was installed and the microSD card was properly inserted into the Raspberry Pi.
|
||||
For instructions about Fedora ARM on Raspberry Pi:
|
||||
** For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}>>.
|
||||
** For users of other Linux distributions, see: <<installing-fedora-on-a-raspberry-pi-for-linux-users_{context}>>.
|
||||
** For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}>>.
|
||||
** For macOS users, see: <<installing-fedora-on-a-raspberry-pi-for-macos-users_{context}>>.
|
||||
** For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer>>.
|
||||
** For users of other Linux distributions, see: <<installing-fedora-on-a-raspberry-pi-for-linux-users>>.
|
||||
** For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users>>.
|
||||
** For macOS users, see: <<installing-fedora-on-a-raspberry-pi-for-macos-users>>.
|
||||
|
||||
* If you try to use Fedora on a Raspberry Pi 1, Raspberry Pi Zero, or a Raspberry Pi model A, you will receive the rainbow display. This occurs because your Raspberry Pi is not supported (ARMv6 SoCs architectures are not supported).
|
||||
|
||||
|
|
@ -583,11 +546,8 @@ $ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyS0,115
|
|||
|
||||
* The most up-to-date information can be found on the link:https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi?rd=Raspberry_Pi[Raspberry Pi page] of the Fedora Wiki.
|
||||
* For Raspberry Pi hardware specifications and project ideas, see: link:https://www.raspberrypi.org/[The Raspberry Pi Foundation Website].
|
||||
* For information on configuring Fedora, including installing programs and updates, see: xref:f{MAJOROSVER}@fedora:system-administrators-guide:index.adoc[Fedora Docs: System Administrator’s Guide]
|
||||
* For assistance or support, see:
|
||||
** link:https://ask.fedoraproject.org/[Ask Fedora]
|
||||
** link:https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/[Fedora ARM mailing list]
|
||||
** link:https://web.libera.chat/?channels=#fedora-arm[IRC via the #fedora-arm channel on Libera.Chat]
|
||||
|
||||
// Restore the context to what it was before this assembly.
|
||||
:context: {parent-context}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue