From cd6ceb17a886ffae5fef375fb3a70c601e6a829e Mon Sep 17 00:00:00 2001 From: Steven Spencer Date: Thu, 20 Oct 2022 12:03:06 -0500 Subject: [PATCH] URL fix project hacktoberfest-accepted * Remove bugs for old 8_4.md file, as those no-longer exist * Remove bugs linke from old 8-changelog.md as this link no-longer exists * Changed `php.md` so that it uses your-server-ip instead of yourip * Changed `apache-sites-enabled.md` so that it uses your-server-hostname instead of ourownwiki.com * Changed `ssl_keys_https.md` to use example.com instead of ourownwiki.com * Changed `sftp.md` to use site1.com and site2.com instead of mybrokenaxel.com and myfixedaxel.com * Changed `asterisk_installation.md` to use a valid version in the download link * Changed `dokuwiki_server.md` to use example.com instead of wiki-doc.yourdomain.com --- docs/guides/cms/dokuwiki_server.md | 26 ++++----- .../communications/asterisk_installation.md | 6 +- docs/guides/file_sharing/sftp.md | 46 +++++++-------- docs/guides/security/ssl_keys_https.md | 22 ++++---- docs/guides/web/apache-sites-enabled.md | 56 +++++++++---------- docs/guides/web/php.md | 2 +- docs/release_notes/8-changelog.md | 2 - docs/release_notes/8_4.md | 4 +- 8 files changed, 81 insertions(+), 83 deletions(-) diff --git a/docs/guides/cms/dokuwiki_server.md b/docs/guides/cms/dokuwiki_server.md index 4eaef6491a..9c60c47c8f 100644 --- a/docs/guides/cms/dokuwiki_server.md +++ b/docs/guides/cms/dokuwiki_server.md @@ -16,7 +16,7 @@ tags: * Comfort with modifying configuration files from the command line with an editor (our examples here will use _vi_, but you can substitute your favorite editor) * Some knowledge about web applications and setup. * Our example will use the [Apache Sites Enabled](../web/apache-sites-enabled.md) for setup, so it is a good idea to review that routine if you plan on following along. -* We will be using "wiki-doc.yourdomain.com" as the domain name throughout this example. +* We will be using "example.com" as the domain name throughout this example. * We will assume throughout this document that you are the root user or can get there with _sudo_. * We are assuming a fresh install of the OS, however that is **NOT** a requirement. @@ -58,16 +58,16 @@ And add this to the very bottom of the file: Create the site configuration file in sites-available: -`vi /etc/httpd/sites-available/com.yourdomain.wiki-doc` +`vi /etc/httpd/sites-available/com.example` That configuration file should look something like this: ``` - ServerName wiki-doc.yourdomain.com - DocumentRoot /var/www/sub-domains/com.yourdomain.wiki-doc/html + ServerName example.com + DocumentRoot /var/www/sub-domains/com.example/html - + AllowOverride All Require all denied @@ -78,7 +78,7 @@ That configuration file should look something like this: - ErrorLog /var/log/httpd/wiki-doc.yourdomain.com_error.log + ErrorLog /var/log/httpd/example.com_error.log CustomLog /var/log/httpd/wiki-doc.yourdomain_access.log combined ``` @@ -87,13 +87,13 @@ Note that the "AllowOverride All" above, allows the .htaccess (directory specifi Go ahead and link the configuration file into sites-enabled, but don't start web services as yet: -`ln -s /etc/httpd/sites-available/com.yourdomain.wiki-doc /etc/httpd/sites-enabled/` +`ln -s /etc/httpd/sites-available/com.example /etc/httpd/sites-enabled/` ### Apache DocumentRoot We also need to create our _DocumentRoot_. To do this: -`mkdir -p /var/www/sub-domains/com.yourdomain.wiki-doc/html` +`mkdir -p /var/www/sub-domains/com.example/html` ## Installing DokuWiki @@ -124,7 +124,7 @@ We don't want that leading named directory when we decompress the archive, so we The second option is the "-C" option, and that tells tar where we want the archive to be decompressed to. So decompress the archive with this command: -`tar xzf dokuwiki-stable.tgz --strip-components=1 -C /var/www/sub-domains/com.yourdomain.wiki-doc/html/` +`tar xzf dokuwiki-stable.tgz --strip-components=1 -C /var/www/sub-domains/com.example/html/` Once we have executed this command, all of DokuWiki should be in our _DocumentRoot_. @@ -132,11 +132,11 @@ We need to make a copy of the _.htaccess.dist_ file that came with DokuWiki and In the process, we will be changing the name of this file to simply _.htaccess_ which is what _apache_ will be looking for. To do this: -`cp /var/www/sub-domains/com.yourdomain.wiki-doc/html/.htaccess{.dist,}` +`cp /var/www/sub-domains/com.example/html/.htaccess{.dist,}` Now we need to change ownership of the new directory and its files to the _apache_ user and group: -`chown -Rf apache.apache /var/www/sub-domains/com.yourdomain.wiki-doc/html` +`chown -Rf apache.apache /var/www/sub-domains/com.example/html` ## Setting Up DNS Or /etc/hosts @@ -151,7 +151,7 @@ And then modify your hosts file to look something like this (note the IP address ``` 127.0.0.1 localhost 127.0.1.1 myworkstation-home -10.56.233.179 wiki-doc.yourdomain.com wiki-doc +10.56.233.179 example.com wiki-doc # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback @@ -189,7 +189,7 @@ Now that our host name is set for testing and the web service has been started, OR -`http://wiki-doc.yourdomain.com/install.php` +`http://example.com/install.php` Either should work if you set your hosts file as above. This will bring you to the setup screen so that you can finish the setup: diff --git a/docs/guides/communications/asterisk_installation.md b/docs/guides/communications/asterisk_installation.md index a149900326..5f04f5543e 100644 --- a/docs/guides/communications/asterisk_installation.md +++ b/docs/guides/communications/asterisk_installation.md @@ -82,9 +82,9 @@ sudo dnf -y install git wget Before you download this script, make sure you have the latest version. To do so, navigate to [the Asterisk download link here](http://downloads.asterisk.org/pub/telephony/asterisk/) and look for the latest build of Asterisk. Then copy the link location. As of the writing of this document, the following was the latest build: ``` -wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-18.6.0.tar.gz -tar xvfz asterisk-18-current.tar.gz -cd asterisk-18.6.0/ +wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-20-current.tar.gz +tar xvfz asterisk-20-current.tar.gz +cd asterisk-20.0.0/ ``` Before running the `install_prereq` below (and the remaining commands), you are going to need to be the superuser or root. It's much easier at this point to get into _sudo_ permanently for a while. We will exit back out of _sudo_ later in the process: diff --git a/docs/guides/file_sharing/sftp.md b/docs/guides/file_sharing/sftp.md index 313cc938ba..f367c0c538 100644 --- a/docs/guides/file_sharing/sftp.md +++ b/docs/guides/file_sharing/sftp.md @@ -60,9 +60,9 @@ Everything is made up here. Any resemblance to persons or sites that are real, i **Sites:** -* mybrokenaxel.com +* mybrokenaxel = (site1.com) user = mybroken -* myfixedaxel.com +* myfixedaxel = (site2.com) user = myfixed **Administrators** @@ -96,8 +96,8 @@ mkdir -p /etc/httpd/sites-enabled Creating the web directories: ``` -mkdir -p /var/www/sub-domains/com.mybrokenaxel/html -mkdir -p /var/www/sub-domains/com.myfixedaxel/html +mkdir -p /var/www/sub-domains/com.site1/html +mkdir -p /var/www/sub-domains/com.site2/html ``` We will deal with the ownership of these directories in the script application found below. @@ -122,7 +122,7 @@ Then save the file and exit. We need two sites created. We will create the configurations in `/etc/httpd/sites-available` and then link them to `../sites-enabled`: ``` -vi /etc/httpd/sites-available/com.mybrokenaxel +vi /etc/httpd/sites-available/com.site1 ``` !!! note @@ -131,17 +131,17 @@ vi /etc/httpd/sites-available/com.mybrokenaxel ``` - ServerName www.mybrokenaxel.com + ServerName www.site1.com ServerAdmin username@rockylinux.org - DocumentRoot /var/www/sub-domains/com.mybrokenaxel/html + DocumentRoot /var/www/sub-domains/com.site1/html DirectoryIndex index.php index.htm index.html Alias /icons/ /var/www/icons/ - CustomLog "/var/log/httpd/com.mybrokenaxel.www-access_log" combined - ErrorLog "/var/log/httpd/com.mybrokenaxel.www-error_log" + CustomLog "/var/log/httpd/com.site1.www-access_log" combined + ErrorLog "/var/log/httpd/com.site1.www-error_log" - + Options -ExecCGI -Indexes AllowOverride None @@ -156,22 +156,22 @@ vi /etc/httpd/sites-available/com.mybrokenaxel Save this file and exit. ``` -vi /etc/httpd/sites-available/com.myfixedaxel +vi /etc/httpd/sites-available/com.site2 ``` ``` - ServerName www.myfixedaxel.com + ServerName www.site2.com ServerAdmin username@rockylinux.org - DocumentRoot /var/www/sub-domains/com.myfixedaxel/html + DocumentRoot /var/www/sub-domains/com.site2/html DirectoryIndex index.php index.htm index.html Alias /icons/ /var/www/icons/ - CustomLog "/var/log/httpd/com.myfixedaxel.www-access_log" combined - ErrorLog "/var/log/httpd/com.myfixedaxel.www-error_log" + CustomLog "/var/log/httpd/com.site2.www-access_log" combined + ErrorLog "/var/log/httpd/com.site2.www-error_log" - + Options -ExecCGI -Indexes AllowOverride None @@ -188,8 +188,8 @@ Save this file and exit. Once the two configuration files are created, go ahead and link them from within `/etc/httpd/sites-enabled`: ``` -ln -s ../sites-available/com.mybrokenaxel -ln -s ../sites-available/com.myfixedaxel +ln -s ../sites-available/com.site1 +ln -s ../sites-available/com.site2 ``` Now enable and start the `httpd` process: @@ -237,8 +237,8 @@ If this works for both administrative users, you should be ready to go to the ne We need to add our web users. That `../html` directory structure already exists, so we don't want to create it when we add the user, but we *do* want to specify it. We also do not want any login other than via SFTP so we need to use a shell that denies logins. ``` -useradd -M -d /var/www/sub-domains/com.mybrokenaxel/html -g apache -s /usr/sbin/nologin mybroken -useradd -M -d /var/www/sub-domains/com.myfixedaxel/html -g apache -s /usr/sbin/nologin myfixed +useradd -M -d /var/www/sub-domains/com.site1/html -g apache -s /usr/sbin/nologin mybroken +useradd -M -d /var/www/sub-domains/com.site2/html -g apache -s /usr/sbin/nologin myfixed ``` Let's break down those commands a bit: @@ -555,8 +555,8 @@ To test that these files show up and load as expected, you simply need to modify ``` 127.0.0.1 localhost -192.168.1.116 www.mybrokenaxel.com mybrokenaxel.com -192.168.1.116 www.myfixedaxel.com myfixedaxel.com +192.168.1.116 www.site1.com site1.com +192.168.1.116 www.site2.com site2.com # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet @@ -569,7 +569,7 @@ ff02::2 ip6-allrouters For real domains, you would want to populate your DNS servers with the hosts above. You can, though, use this *Poor Man's DNS* for testing any domain, even one that hasn't been taken live on real DNS servers. -Now, open your web browser and check to make sure that your `index.html` file for each domain displays by entering the URL in your browser's address bar. (Example: "http://mybrokenaxel.com") If your test index files load, everything is working correctly. +Now, open your web browser and check to make sure that your `index.html` file for each domain displays by entering the URL in your browser's address bar. (Example: "http://site1.com") If your test index files load, everything is working correctly. ## Part 3: Administrative Access with SSH key pairs diff --git a/docs/guides/security/ssl_keys_https.md b/docs/guides/security/ssl_keys_https.md index 2160523458..d29c149535 100644 --- a/docs/guides/security/ssl_keys_https.md +++ b/docs/guides/security/ssl_keys_https.md @@ -37,32 +37,32 @@ To start with, let's make sure that OpenSSL is installed on both your workstatio If it is not installed, your system will install it and any needed dependencies. -Our example domain is ourownwiki.com. Keep in mind that you would need to purchase and register your domain ahead of time. You can purchase domains through a number of "Registrars". +Our example domain is example.com. Keep in mind that you would need to purchase and register your domain ahead of time. You can purchase domains through a number of "Registrars". If you are not running your own DNS (Domain Name System), you can often use the same providers for DNS hosting. DNS translates your named domain, to numbers (IP addresses, either IPv4 or IPv6) that the Internet can understand. These IP addresses will be where the web site is actually hosted. Let's generate the key using openssl: -`openssl genrsa -des3 -out ourownwiki.com.key.pass 2048` +`openssl genrsa -des3 -out example.com.key.pass 2048` Note that we named the key, with a .pass extension. That's because as soon as we execute this command, it requests that you enter a passphrase. Enter a simple passphrase that you can remember as we are going to be removing this shortly: ``` -Enter pass phrase for ourownwiki.com.key.pass: -Verifying - Enter pass phrase for ourownwiki.com.key.pass: +Enter pass phrase for example.com.key.pass: +Verifying - Enter pass phrase for example.com.key.pass: ``` Next, let's remove that passphrase. The reason for this is that if you don't remove it, each time your web server restarts and loads up your key, you will need to enter that passphrase. You might not even be around to enter it, or worse, might not have a console at the ready to enter it. Remove it now to avoid all of that: -`openssl rsa -in ourownwiki.com.key.pass -out ourownwiki.com.key` +`openssl rsa -in example.com.key.pass -out example.com.key` This will request that passphrase once again to remove the passphrase from the key: -`Enter pass phrase for ourownwiki.com.key.pass:` +`Enter pass phrase for example.com.key.pass:` -Now that you have entered the passphrase a third time, it has been removed from the key file and saved as ourownwiki.com.key +Now that you have entered the passphrase a third time, it has been removed from the key file and saved as example.com.key ## Generate the CSR @@ -70,9 +70,9 @@ Next, we need to generate the CSR (certificate signing request) that we will use During the generation of the CSR, you will be prompted for several pieces of information. These are the X.509 attributes of the certificate. -One of the prompts will be for "Common Name (e.g., YOUR name)". It is important that this field be filled in with the fully qualified domain name of the server to be protected by SSL. If the website to be protected will be https://www.ourownwiki.com, then enter www.ourownwiki.com at this prompt: +One of the prompts will be for "Common Name (e.g., YOUR name)". It is important that this field be filled in with the fully qualified domain name of the server to be protected by SSL. If the website to be protected will be https://www.example.com, then enter www.example.com at this prompt: -`openssl req -new -key ourownwiki.com.key -out ourownwiki.com.csr` +`openssl req -new -key example.com.key -out example.com.csr` This opens up a dialog: @@ -86,7 +86,7 @@ This opens up a dialog: `Organizational Unit Name (eg, section) []:` This would describe the division of the organization that your domain falls under. Again, you can just hit 'Enter' to skip. -`Common Name (eg, your name or your server's hostname) []:` Here, we have to enter our site hostname, example "www.ourownwiki.com" +`Common Name (eg, your name or your server's hostname) []:` Here, we have to enter our site hostname, example "www.example.com" `Email Address []:` This field is optional, you can decide to fill it out or just hit 'Enter' to skip. @@ -105,7 +105,7 @@ Now you should have generated your CSR. Each certificate vendor will have basically the same procedure. You purchase the SSL and term (1 or 2 years, etc.) and then you submit your CSR. To do this, you will need to use the `more` command, and then copy the contents of your CSR file. -`more ourownwiki.com.csr` +`more example.com.csr` Which will show you something like this: diff --git a/docs/guides/web/apache-sites-enabled.md b/docs/guides/web/apache-sites-enabled.md index 48ad1822c4..53a0405612 100644 --- a/docs/guides/web/apache-sites-enabled.md +++ b/docs/guides/web/apache-sites-enabled.md @@ -72,17 +72,17 @@ The configuration file configuration content would look something like this: ```apache - ServerName www.ourownwiki.com + ServerName your-server-hostname ServerAdmin username@rockylinux.org - DocumentRoot /var/www/sub-domains/com.ourownwiki.www/html + DocumentRoot /var/www/sub-domains/your-server-hostname/html DirectoryIndex index.php index.htm index.html Alias /icons/ /var/www/icons/ - # ScriptAlias /cgi-bin/ /var/www/sub-domains/com.ourownwiki.www/cgi-bin/ + # ScriptAlias /cgi-bin/ /var/www/sub-domains/your-server-hostname/cgi-bin/ - CustomLog "/var/log/httpd/com.ourownwiki.www-access_log" combined - ErrorLog "/var/log/httpd/com.ourownwiki.www-error_log" + CustomLog "/var/log/httpd/your-server-hostname-access_log" combined + ErrorLog "/var/log/httpd/your-server-hostname-error_log" - + Options -ExecCGI -Indexes AllowOverride None @@ -96,15 +96,15 @@ The configuration file configuration content would look something like this: ``` Once the file is created, we need to write (save) it with: `shift : wq` -In our example above, the wiki site is loaded from the "html" sub-directory of _com.ourownwiki.www_, which means that the path we created in _/var/www_ (above) will need some additional directories to satisfy this: +In our example above, the wiki site is loaded from the "html" sub-directory of _your-server-hostname_, which means that the path we created in _/var/www_ (above) will need some additional directories to satisfy this: -`mkdir -p /var/www/sub-domains/com.ourownwiki.www/html` +`mkdir -p /var/www/sub-domains/your-server-hostname/html` ... which will create the entire path with a single command. Next we would want to install our files to this directory that will actually run the website. This could be something you made yourself, or an installable web application (in this case a wiki that you downloaded). Copy your files to the path above: -`cp -Rf wiki_source/* /var/www/sub-domains/com.ourownwiki.www/html/` +`cp -Rf wiki_source/* /var/www/sub-domains/your-server-hostname/html/` ## Configuration https - Using an SSL Certificate @@ -118,7 +118,7 @@ You can also use this alternate process for using an [SSL certificate from Let's ### Placement of the SSL keys and Certificate's -Now that you have your keys and certificate files, we need to place them logically in your file system on the web server. As we've seen with the example configuration file (above), we are placing our web files in _/var/www/sub-domains/com.ourownwiki.www/html_. +Now that you have your keys and certificate files, we need to place them logically in your file system on the web server. As we've seen with the example configuration file (above), we are placing our web files in _/var/www/sub-domains/your-server-hostname/html_. We want to place our certificate and key files with the domain, but NOT in the document root, which in this case is the _html_ folder. @@ -126,7 +126,7 @@ We never want our certificates and keys to potentially be exposed to the web. Th Instead, we will create a new directory structure for our SSL files, outside the document root: -`mkdir -p /var/www/sub-domains/com.ourownwiki.www/ssl/{ssl.key,ssl.crt,ssl.csr}` +`mkdir -p /var/www/sub-domains/your-server-hostname/ssl/{ssl.key,ssl.crt,ssl.csr}` If you are new to the "tree" syntax for making directories, what the above says is: @@ -139,9 +139,9 @@ If you ever need to re-issue the certificate from a different provider, etc., it Assuming that you have named your key, csr, and crt (certificate) files with the name of your site, and that you have them stored in _/root_, we will then copy them up to their respective locations that we just created: ``` -cp /root/com.wiki.www.key /var/www/sub-domains/com.ourownwiki.www/ssl/ssl.key/ -cp /root/com.wiki.www.csr /var/www/sub-domains/com.ourownwiki.www/ssl/ssl.csr/ -cp /root/com.wiki.www.crt /var/www/sub-domains/com.ourownwiki.www/ssl/ssl.crt/ +cp /root/com.wiki.www.key /var/www/sub-domains/your-server-hostname/ssl/ssl.key/ +cp /root/com.wiki.www.csr /var/www/sub-domains/your-server-hostname/ssl/ssl.csr/ +cp /root/com.wiki.www.crt /var/www/sub-domains/your-server-hostname/ssl/ssl.crt/ ``` ### The Site Configuration - https @@ -154,9 +154,9 @@ We want them to go to port 443 (or http secure, better known as SSL). Our port 8 ``` - ServerName www.ourownwiki.com + ServerName your-server-hostname ServerAdmin username@rockylinux.org - Redirect / https://www.ourownwiki.com/ + Redirect / https://your-server-hostname/ ``` @@ -168,20 +168,20 @@ Next, we need to define the https portion of the configuration file. The http se ``` - ServerName www.ourownwiki.com + ServerName your-server-hostname ServerAdmin username@rockylinux.org - Redirect / https://www.ourownwiki.com/ + Redirect / https://your-server-hostname/ - ServerName www.ourownwiki.com + ServerName your-server-hostname ServerAdmin username@rockylinux.org - DocumentRoot /var/www/sub-domains/com.ourownwiki.www/html + DocumentRoot /var/www/sub-domains/your-server-hostname/html DirectoryIndex index.php index.htm index.html Alias /icons/ /var/www/icons/ - # ScriptAlias /cgi-bin/ /var/www/sub-domains/com.ourownwiki.www/cgi-bin/ + # ScriptAlias /cgi-bin/ /var/www/sub-domains/your-server-hostname/cgi-bin/ - CustomLog "/var/log/httpd/com.ourownwiki.www-access_log" combined - ErrorLog "/var/log/httpd/com.ourownwiki.www-error_log" + CustomLog "/var/log/httpd/your-server-hostname-access_log" combined + ErrorLog "/var/log/httpd/your-server-hostname-error_log" SSLEngine on SSLProtocol all -SSLv2 -SSLv3 -TLSv1 @@ -189,11 +189,11 @@ Next, we need to define the https portion of the configuration file. The http se SSLCipherSuite EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384 :EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS - SSLCertificateFile /var/www/sub-domains/com.ourownwiki.www/ssl/ssl.crt/com.wiki.www.crt - SSLCertificateKeyFile /var/www/sub-domains/com.ourownwiki.www/ssl/ssl.key/com.wiki.www.key - SSLCertificateChainFile /var/www/sub-domains/com.ourownwiki.www/ssl/ssl.crt/your_providers_intermediate_certificate.crt + SSLCertificateFile /var/www/sub-domains/your-server-hostname/ssl/ssl.crt/com.wiki.www.crt + SSLCertificateKeyFile /var/www/sub-domains/your-server-hostname/ssl/ssl.key/com.wiki.www.key + SSLCertificateChainFile /var/www/sub-domains/your-server-hostname/ssl/ssl.crt/your_providers_intermediate_certificate.crt - + Options -ExecCGI -Indexes AllowOverride None @@ -223,7 +223,7 @@ Remember that our *httpd.conf* file is including */etc/httpd/sites-enabled* at t That's by design, so that we can easily remove things in the event that `httpd` fails to restart. So to enable our configuration file, we need to create a symbolic link to that file in *sites-enabled* and then start or restart the web service. To do this, we use this command: -`ln -s /etc/httpd/sites-available/com.ourownwiki.www /etc/httpd/sites-enabled/` +`ln -s /etc/httpd/sites-available/your-server-hostname /etc/httpd/sites-enabled/` This will create the link to the configuration file in *sites-enabled*, just like we want. diff --git a/docs/guides/web/php.md b/docs/guides/web/php.md index 82aedff4cf..4e4306be07 100644 --- a/docs/guides/web/php.md +++ b/docs/guides/web/php.md @@ -139,7 +139,7 @@ phpinfo(); ?> ``` -Use a web browser to check that the server is working properly by going to the page http://yourip/info.php. +Use a web browser to check that the server is working properly by going to the page http://your-server-ip/info.php. !!! Warning diff --git a/docs/release_notes/8-changelog.md b/docs/release_notes/8-changelog.md index a4a7fa68ff..d4eae45670 100644 --- a/docs/release_notes/8-changelog.md +++ b/docs/release_notes/8-changelog.md @@ -603,8 +603,6 @@ The following modules have been updated since the 8.5 release Nov 14, 2021: ### Known Issues -[bug 174](https://bugs.rockylinux.org/show_bug.cgi?id=174) - We are aware of an issue that `kdump` does not work on vmware systems such as ESXi. - We are also aware of our mirror system reporting back the wrong directory for doing updates. It was going to `kickstart` rather than `os`. This should be resolved and updates should work normally. ## 8.4 - 2021-09-21 diff --git a/docs/release_notes/8_4.md b/docs/release_notes/8_4.md index 3b0617d57e..a2b684767f 100644 --- a/docs/release_notes/8_4.md +++ b/docs/release_notes/8_4.md @@ -104,7 +104,7 @@ As with any release, there are sometimes bugs or issues found in the process of #### Rsyslog missing from Minimal ISO -The Rocky Linux Minimal ISO (`Rocky-8.4-x86_64-minimal.iso`) does not contain the `rsyslog` package. As a result, a system installed with the Rocky Linux Minimal ISO will not include `rsyslog.service` or `/var/log/messages` out of the box. The `rsyslog` package can be installed immediately after reboot from the Rocky Linux AppStream repository to resolve this issue. ([RB#14](https://bugs.rockylinux.org/show_bug.cgi?id=14)) +The Rocky Linux Minimal ISO (`Rocky-8.4-x86_64-minimal.iso`) does not contain the `rsyslog` package. As a result, a system installed with the Rocky Linux Minimal ISO will not include `rsyslog.service` or `/var/log/messages` out of the box. The `rsyslog` package can be installed immediately after reboot from the Rocky Linux AppStream repository to resolve this issue. You may run the following command post-install to complete the installation of rsyslog: @@ -118,7 +118,7 @@ If you need to have OpenSCAP profiles, please use the DVD1 ISO Variant or ensure #### Anaconda "Help" Button not functioning (#20) -The Help button in the Anaconda installer doesn't currently work. The Rocky Linux team has provided an [installation walk-through](../guides/installation.md) in the Rocky Linux Documentation to help resolve installation issues. ([RB#20](https://bugs.rockylinux.org/show_bug.cgi?id=20)) +The Help button in the Anaconda installer doesn't currently work. The Rocky Linux team has provided an [installation walk-through](../guides/installation.md) in the Rocky Linux Documentation to help resolve installation issues. #### Bug Report GUI missing debranding (libreport)