Updated / reviewed documentation so far (published in stg branch!):
Metadata Update from @pboy: - Issue tagged with: in progress, meeting
Issue tagged with: in progress
1. GRUB Boot Screen 2. "Installation Summary" Screen 3. "Installation Destination" Screen 4. "Manual Partitioning" Screen
In a standard ("DVD") installation, Anaconda uses "Local media" by default. Do not change anything.
In a standard installation (using the "Standard ISO image"), Anaconda uses "Local media" which will pull packages from the ISO image on your install media.
The network configuration should get edited before configuring the installation target. The hostname goes into the naming and replaces
Before configuring the Installation Destination configure the Network & Host Name to give your server a hostname. The new hostname can be entered at the bottom of this screen and then pressing the Apply button.
In any case. select one (or more) disks on the system to be installed that are to be included in the Server installation. Additionally, you can include e.g. SAN or other network drives into the installation right here. This will save you later some administration work. We don’t get further into this here, allthough.
Select one or more disks where Fedora Server will be installed. You may also include a SAN (Storage Attached Network) or other network attached drives as part of your Fedora Server install in this same configuration screen. However, this configuration is not covered here in this installation guide.
If the storage organization...
If you are satisfied with the Fedora Server default hard disk partitioning, you can leave Automatic checked under Storage Configuration. If the disks already contain partitions and file systems, you will want to select the option "Free up space by removing or shrinking existing partitions". A window will open after you click Done giving you the opportunity to delete partitions and file systems to make space for your Fedora Server installation on the install disks.
Select Custom Storage Configuration instead of Automatic and select Done int the upper bar. Anaconda will take you to the Manual Partitioning form.
Select Custom Storage Configuration instead of Automatic and select Done in the upper bar. Anaconda will take you to the Manual Partitioning form.
If there is more than one disk available, the default partitioning creates, on each of the other disks, one big partition with a Physical Volume (PV) and adds it to the VG.
For details see the Creating Software RAID section of the Installation Guide. NOTE: both of these links are to the Fedora 35 version of the docs. Please confirm your are using that version or find the same docs for your version.
Note: Just in case you need a DOS/MBR partitioning scheme for some goot reason, you can override the GPT default by adding xxxx to the kernel boot parameter at the initial boot screen.
At first ...
First, decide if you desire to have a root account on Fedora Server. Anaconda's default configuration disables the root account to prevent malicious actors from logging in as root. Instead, Anaconda requires a user account that can acquire administrative privileges using sudo.
It is possible to secure root access using an ssh key file, but server administrators may desire to retain the ability to have root access with a password through an attached console or Cockpit login. If you decide that you would like to have password access to the root account, select Root Account, then Enable root account, and enter a password for the root account in the form that appears. For security reasons, ssh login as root is only allowed with an ssh key file by default. You are not encouraged to modify this security setting by clicking on the option, "Allow root SSH login with password".
Second, select User Creation to create a user account for Fedora Server. You are encouraged to keep the default options of "Add administrative privileges to this user account" and "Require a password to use this account" checked. Unless you have decided against the security practice of not allowing root access with a password, your user account will need these options to have administrative access to the server after installation of Fedora Server.
For the operation...
You may want to check Time & Date on the Installation Summary page to ensure that you have the correct time zone and Network Time is activated. These settings ensure that your server will regularly synchronize its time with a trusted source. Having the correct time on your server will make tasks like finding events at a specific time and date in your log files easier.
This guide...
This guide offers a recommended checklist of tasks to ensure the safe and reliable operation of Fedora Server. System administrators may choose whether these tasks apply to their specific use case.
consider dropping "additionally" in the first paragraph.
I believe using "$" instead of "#" seems more appropriate for these line because you would be using the ssh command from your desktop's user account not the root account.
[…]# ssh hostmin@hostexample.com hostmin@host.example.com's password: […]# sudo su -
spelling correction: "[sudo] Passwort for hostmin:" should be "[sudo] password for hostmin:"
As above I believe it would be more correct to do all of this in your user account on your desktop instead of your root account, so the promote would have "$" instead of "#".
[…]# mkdir ~/.ssh […]# chmod 700 ~/.ssh […]# cd ~/.ssh […]# ssh-keygen -t rsa -b 4096 -C "root@host.example.com" -f ~/.ssh/<outputkeyfile> […]# ssh-copy-id -i $outputkeyfile.pub hostmin@host.example.com […]# vi ~/.ssh/config Host myhost Hostname host.example.com User hostmin ProxyCommand none ForwardAgent no ForwardX11 no Port 22 KeepAlive yes IdentityFile ~/.ssh/$outputkeyfile […]# ssh myhost
consider a title change: "2. Disable SSH Login with passwords for system users"
consider rephrasing: "Is anyone else is rejected with the message "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)" to "Are other users rejected with the message "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)"
consider rephrasing: "If this does not work: Check whether the latest update has been installed. The file /etc/ssh/sshd_config.d/50-redhat.conf there should not include a line „PasswordAuthentication yes“ (as this is already the default and should not be repeated in order not to hinder other configurations)." to "If other users are able to log in with a password besides your know authorized user, install the latest updates. Also, check the file /etc/ssh/sshd_config.d/50-redhat.conf to make sure that it does not include the line "PasswordAuthentication yes" (as this is already the default and should not be repeated or else it could hinder other configurations)."
/etc/ssh/sshd_config.d/50-redhat.conf
as before, it is described as the "desktop user" so I believe the console output should have "$" instead of "#".
[…]# mkdir ~/.ssh […]# cd ~/.ssh […]# ssh-keygen -t rsa -b 4096 -C "root@example.com" -f <outputkeyfile>
also in this line which is console output that comes later:
[…]# sftp hostmin@example.com
Both Guides updated as proposed with one exception: commented out the link and text about Fedora Installation Guide, which is really outdated and will probably be removed from F37 according to docs planning.
I'm glad you found my reviews useful. Thanks for all the work you have done to add my proposed suggestions to the documentation.
Metadata Update from @pboy: - Issue untagged with: meeting
Everything published and online. Close the ticket.
Metadata Update from @pboy: - Issue untagged with: in progress
Metadata Update from @pboy: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.