rocky-linux / documentation Goto Github PK
View Code? Open in Web Editor NEWOfficial Rocky Linux documentation repository.
Home Page: https://docs.rockylinux.org
License: Creative Commons Attribution Share Alike 4.0 International
Official Rocky Linux documentation repository.
Home Page: https://docs.rockylinux.org
License: Creative Commons Attribution Share Alike 4.0 International
Starting with the basic network configuration page here, there is likely other bits of guides/documentation that may not apply to certain Rocky Linux versions or processes have changed. The documentation should likely be evaluated as a result. Right now, there are users who frequently come to the general channel to ask about certain cases (especially the network-scripts being empty on Rocky Linux 9) being confused as some page assumes the configuration is the same on both 8 and 9.
There are a few things that should be considered:
One idea could be:
Another idea could be having a button or a way to reflect a given release dynamically on a page (this may be a feature that isn't in mkdocs or a plugin). There are some docs pages out there that do this where selecting a version at the top will change commands or portions of the guide to reflect that release.
Hi guys,
I just wanted to let you know about a little typo in your docs on the page "Postfix Process Reporting" -> "Testing Mail First".
cp /etc/**postifix**/main.cf /etc/postfix/main.cf.bak
P.S. I'm new to Rocky Linux but till now I'm more than happy with it. Thanks!
Kind Regards,
Dennis Bitsch
https://docs.rockylinux.org/en/guides/installation/
Currently in both Rocky Linux 8 and 9 guides, they point to ISO files that have since been moved to the vault. They should be updated to point to 8.7 and 9.1.
Add Afrikaans (af?) to the list of languages for Rocky Docs.
See:
https://en.wikipedia.org/wiki/Afrikaans#Etymology
https://fr.wikipedia.org/wiki/Afrikaans
and
https://github.com/rocky-linux/documentation/blob/main/crowdin.yml
Das Issue enthält 5 verschiedene Tasks, die nacheinander durchgeführt werden sollten.
Diese Tasks entsprechen 5 verschiedene Rollen, die mehrere Teilnehmer (2 Personen oder mehr) nach dem Team-Translating Prinzip abwechselnd übernehmen können.
Tip:
Um Konflikte mit dem Übersetzungs-Tool (hier Crowdin) zu vermeiden,
sollte man erst mit den Punkten 2.,3. und 4 anfangen, wenn Task Nr. 1 abgeschlossen ist.
Test foo bar baz
In some sense version 7 is the "last version" of CENTOS.
The guide at https://docs.rockylinux.org/guides/migrate2rocky/ could please include a note about upgrading from CENTOS 7. Maybe this is just a link to Red Hat's documentation on this topic. But either way I stopped trusting Red Hat since CENTOS 7 was released, so hearing from you would be reassuring.
Proeflees van vertalings in Afrikaans
Dokumentasie:
https://docs.rockylinux.org/af/
crowdin:
https://crowdin.com/project/rockylinuxorg/af
https://crowdin.com/project/rockydocs/af
On the URL https://docs.rockylinux.org/release_notes/8.4/#anaconda-help-button-not-functioning-20 (Anaconda "Help" Button not functioning (#20)
) there's a link to installation walk-through
which doesn't work. The link redirects to https://docs.rockylinux.org/release_notes/guides/rocky-8-installation/ which is not found.
Can we get a script to convert to Rocky Linux once it's released? After the CentOS announcement, I ran this script:
https://github.com/oracle/centos2ol
to convert to Oracle Linux but I would much rather be on Rocky Linux than Oracle if possible. I'm happy to help but I suspect someone else could convert this script to a Rocky version very quickly with the right repo details, etc. 👍
I created this issue, so I could use it to link to a related PR I'll submit later; just another test of using GH capabilities.
linking-a-pull-request-to-an-issue
This is a feature request to create template documents with appropriate GH markdown in place to provide an easy to use starting document for contributors to use. Presumably we'd want one for each basic type of document or genre published:
books
, gemstones
, guides
, labs
, release_notes
, and possibly one to use for the GH "Wiki" link (not to be confused with other RL Wikis).
Current release notes do not contain information to validate downloaded images (whether from torrents or from our mirrors). There should be a blurb that explains how to do so, by using the checksum files provided as well as having steps to validate against the checksum repo (by verifying commit signatures, optionally checking against pgp key servers): https://github.com/rocky-linux/checksums
Need to add to documentation a special observation to disable "setenforce 0"
or better off, "sudo setsebool httpd_can_network_connect 1 -P" , or some better instructions to allow nginx through SELinux
Othewise the nginx proxy_pass capabilities will not work throwing a "502 Bad Gateway" error
The docs.r.o project will like some help with putting in place a versioning solution that will allow the docs.r.o website to simultaneously maintain and host content for different versions of Rocky Linux as they are released. Perhaps with a tool like:
https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/
For further context please see:
https://chat.rockylinux.org/rocky-linux/pl/5a5psbidb7rdbb4d1yrekjtmka
Thank you :-)
While taking notes on setting things up I've noticed that many of our docs are geared for small installations as opposed to actual enterprise usage where LDAP, Kerberos (and AD integration), Actual use of Certificate Authorities, Certs/Key management (ssh, 509, PKI, etc), AFS(Andrew not Apple)/Ceph/ZFS/SAN/NAS/FC/iSCSI, dbase sharding, etc etc are not addressed at all. Should we create a section specific to such enterprise configurations?
As a real-world example, setting up KVM to do live migrations between hosts is a bit more complex and requires things which are not needed at all for a standalone setup on one desktop home server like NFS and SR-IOV of intel 40GB NICs. A college admin setting up a system for students to run containers or VMs on during a class is very different than one person setting this up for home/hobby usage (multi-user security, encrypted memory space/shared mem, etc). iDRAC, IPMI/LOM, OpenManage, and HA/HPC clusters would be other examples.
Putting some of these topics in with the list as we have it now would likely just confuse many users who aren't concerned with such setups, may never have heard of most of these topics, and make for confusing or annoying navigation for someone who just wants things to work without understanding all the details.
I have no agenda, just trying to be considerate. It may not be worth the effort of splitting such topics out at this stage; perhaps once we get more docs, but preventative front-loading can save much hassle later.
Hello,
In the official documentation to Import Rocky Linux to WSL please could you clarify how and where to find the container rootfs ?
We have this :
Download the image from the CDN images folder (if it is available)
Download the image from the latest Github Action build
Extract the image from either Docker Hub or Quay.io (ref.)
But in the CDN images folder the is no container rootfs I guess for windows user. In the Github Action build it looks the same I don't know what to use to import Rocky Linux to WSL.
And I don't have docker on my machine so I can't export the rootfs from a docker image.
Thank you very much for your help.
May be, is it plan to create an official WSL image that we can install from the Microsoft Store ?
Deutsche Reviewer gesucht!
Das Issue enthält 5 verschiedene Tasks, die nacheinander durchgeführt werden sollten.
Diese Tasks entsprechen 5 verschiedene Rollen, die mehrere Teilnehmer (2 Personen oder mehr) nach dem Team-Translating Prinzip abwechselnd übernehmen können.
Tip:
Um Konflikte mit dem Übersetzungs-Tool (hier Crowdin) zu vermeiden,
sollte man erst mit den Punkten 2.,3. und 4 anfangen, wenn Task Nr. 1 abgeschlossen ist.
I'll make some additions to the list at:
contribute-Special Notes
As there is an actual, official, RFC/STD for the use of home.arpa
for local only domains.
I'll include some examples of how other listed were never actual stds and in some cases were hijacked (demonstrable even now) by someone purchasing that name.
@wsoyinka I don't know if you would want to include the following info, or where you'd want to put it if you do, but for RHEL/CentOS/RL et. al. you can see what your installed kernels were config'd with :
cat /boot/config-<kernel-ver>
So one could use the following to check the currently running kernel versions' config:
cat /boot/config-$(uname -r) | grep -i <some-keyword>
It will show "=m", or "=y" if configured, but doesn't have entries for anything NOT configured
(i.e. it will not show "=n")
static ip configuration : /etc/sysconfig/network-scripts/ifcfg-Iface_NAME
I'd like to create (or see created) a book on deploying a FreeIPA/IdM installation on Rocky. I'm hoping to make this the first of some "what I learned deploying Rocky in a corporate environment" contributions I want to make. :)
I've got some decent experience working with it so far, and I'd like to contribute, and I should be able to next week.
Note: Everywhere "(CLI & UI)" appears, the CLI method is 100% preferred over the UI and will likely be done first.
Some 'maybes':
Okay, to continue the discussion from my earlier PR re: code in its own line or paragraph.
The Basics
I'd like to use this:
Run this command:
```bash
the-command
```
And not:
Run this command:
`the-command`
Now people have been focusing on on whether we should use the syntax-defining feature as shown in the first example. To clear a couple of things up, I'd first like to mention, as others have, there you can do this for a bunch of languages, not just bash.
Secondly, while I see defining the syntax as a big benefit of this formatting method, I don't think we should make setting the syntax tags "mandatory" by any means. People can just use a plain code block if it suits them, and I don't want to burden the translators with manually making sure the syntax tags are in there.
Thoughts?
The guide stays to install dnf install certbot python3-certbot-nginx does not work, however it appears that dnf install certbot python3-certbot-apache still is available.
The nginx package is missing.
This isn't as critical as my other issue, but I still think it's important.
In the context of a documentation site for a product, having the name of the product repeated in every title to me doesn't seem like something we want.
I'll happily be overruled on this, but I definitely think it wants correcting.
Issue to use the all-contributors spec to add contributors
I was reading the article about setting up nginx here: https://docs.rockylinux.org/guides/web/nginx-mainline/#installing-the-repository
The guide recommends running dnf module enable nginx:mainline
which results in the following error:
[root@3b221b8ee080 /]# dnf module enable nginx:mainline
Last metadata expiration check: 0:00:58 ago on Thu Mar 10 02:30:37 2022.
Error: Problems in request:
missing groups or modules: nginx:mainline
If I run dnf module list nginx
, I don't see mainline
listed as a stream.
[root@3b221b8ee080 /]# dnf module list nginx
Last metadata expiration check: 0:01:26 ago on Thu Mar 10 02:30:37 2022.
Rocky Linux 8 - AppStream
Name Stream Profiles Summary
nginx 1.14 [d] common [d] nginx webserver
nginx 1.16 common [d] nginx webserver
nginx 1.18 common [d] nginx webserver
nginx 1.20 common [d] nginx webserver
I follow instructions to install devtools on Rocky Linux 9 but get the following error message:
$ sudo make install
sudo dnf config-manager --set-enabled powertools
Error: No matching repo to modify: powertools.
make: *** [Makefile:12: .system] Error 1
I'm newbie of RL .
While following the guide I noted the "The git way" actually forgets to do the git part:
The git way
Install git on your server with:
dnf install -y git
Then clone the rocky-tools repository with:
(Which would then return a command not found.)
I've already created a pull request for the correction below.
Cheers
This issue has been moved to Issue #3 on the RL Wiki
Under Requesting Access to Groups/SIGs
"Find the group or groups you wish to join and find the sponsors"
has only a link to the generic MatterMost url.
Should this have links to actually help someone find groups/SIGS easily like:
https://wiki.rockylinux.org/team
https://wiki.rockylinux.org/special-interest-groups
https://lists.resf.org/mailman3/lists/
Or links to the actual MM SIG channels:
(list is not all encompassing, just the ones I currently know of)
AltArch SIG
Containers SIG
GOV(US) SIG
HPC SIG
Kernel SIG
Plus specific packages SIG
Virtualization SIG
Or a list like:
Alternative Architectures SIG:
MatterMost Chat Channel , Maillist, Wiki
Hi there! author of NvChad here. v2.0 has recently released https://nvchad.com/news and it uses lazy.nvim instead of packer.nvim for package manager. There are few breaking changes ( mostly related to package manager ) but the config has gotten easier.
old syntax is depreceated ( people can still use it tho! )
Test project issue
i.e.:
https://github.com/rocky-linux/documentation/blob/main/docs/index.md
https://github.com/rocky-linux/documentation/blob/main/docs/index.de.md
https://github.com/rocky-linux/documentation/blob/main/docs/index.fr.md
see also:
https://crowdin.com/project/rockylinuxorg
https://crowdin.com/project/rockylinuxorg/zh-TW
https://crowdin.com/project/rockylinuxorg/zh-CN
https://crowdin.com/project/rockylinuxorg/pt-PT
https://crowdin.com/project/rockylinuxorg/pt-BR
https://github.com/rocky-linux/rockylinux.org/blob/main/i18n/config.json
and
https://crowdin.com/project/rockydocs
https://github.com/rocky-linux/documentation/blob/main/crowdin.yml
We should probably update the "file names" of install docs from 8.6 and 9.0 to --> 8.7 and 9.1 version respectively. Ditto all corresponding translated files and .pages.
@sspencerwire thoughts ?
https://docs.rockylinux.org/guides/web/mod_SSL_apache/
In the navigation pane (left side)...web...Apache With mod_ssl
Windows 10 Firefox (both 96.0.1 and 96.0.2) render what in the md title is mod_ssl
as if it was diacritics (i.e. accents above the letters); I don't know if the backticks were intentional, should have been single quotes ( ' instead of ` ), accidental or not.
The page https://docs.rockylinux.org/gemstones/docker/ says to use Docker's CentOS repository. This does not seem right: Rocky does not track CentOS, rather RHEL. However, I see that Docker's RHEL repository covers only the IBM S390 architecture - https://docs.docker.com/engine/install/rhel/. The latter page suggests trying the CentOS repository for RHEL on x86_64.
To prevent everyone else to reads https://docs.rockylinux.org/gemstones/docker/ being confused and having to perform this same research, it would be useful if that page contained a little explanation of why Docker's CentOS repository was specified.
Replace
Ukrainian with
Українська
in the pulldown 文A here:
https://docs.rockylinux.org/uk/
See also: Русский
The kernel building guide should be noting to users that building and maintaining their own kernel is unsupported and provide warnings to users who wish to build them. Our wiki actually states the following:
Kernel rebuilds are not recommended nor supported for Rocky Linux. Before building a custom kernel or even considering it, ask yourself the following questions:
* Is the functionality you need available by installing a kernel module from [elrepo](https://elrepo.org)?
* Is the functionality you need available as a separate module from the kernel itself?
* Are you willing to maintain your own security posture?
* **Are you sure**? Rocky Linux and most other EL derivatives were designed to function as a complete environment. Replacing critical components can affect how the system acts.
* **Are you ABSOLUTELY sure**? 99.9% of the users no longer need to build their own kernel. You may simple need a kernel module/driver, in which case, you can use [elrepo](https://elrepo.org) or build your own kernel module (kmod/dkms)
* **Are you sure you don't just want a newer kernel version**? Newer kernels can be found at [elrepo](https://elrepo.org)
As a final warning, you if you break the kernel, you are on the hook for your system. Rocky Linux volunteers or developers are unable to assist you with these issues.
While it is a nice-to-have guide for users who want to build their own kernel or are learning, similar warnings should be given on the kernel building guide.
In the docs/guides/enabling_iptables_firewall.md I believe the instruction to enable iptables is incorrect:
Now we need to enable the iptables service to make sure that it starts on boot:
'dnf enable iptables'
that the command should be:
'systemctl enable iptables'
Hi,
I'm currently following the LXD server tutorial (using Rocky 8.7) and I'd like to propose a correction for this page: https://docs.rockylinux.org/books/lxd_server/01-install/
The part about the OpenZFS GPG key seems to be outdated. The file name is no longer /etc/pki/rpm-gpg/RPM-GPG-KEY-zfsonlinux but /etc/pki/rpm-gpg/RPM-GPG-KEY-openzfs.
Moreover, I'm not sure if that command actually "gets" the gpg key. Does it import it into gpg? After reading gpg's manpage I think "show-only" doesn't do that. I was asked to verify the gpg key by dnf when I installed zfs later on.
In the docs/guides/backup/mirroring_lsyncd.md, maybe the dnf install command is incorrect:
Install Dependencies
We will need some dependencies: a few that are required by lsyncd itself, and a few that are required to build packages from source. Use this command on your Rocky Linux machine to make sure you have the dependencies you need. If you are going to be building from source, it's a good idea to have all of the development tools installed:
dnf install groupinstall 'Development Tools'
that the command should be?
dnf group install 'Development Tools'
I know I've seen written it in a few places that Rocky is intended to be bug for bug compatible.
Does this mean it's just a question of changing the yum repos on my CentOS 8 install, and renaming my distro (/etc/redhat-release
) and it will follow Rocky upgrades? Or is something more complex necessary?
Looking forward to the release - nice work, everyone ❤️
Hello here is some content yayyyy
Deutsche Reviewer gesucht!
Das Issue enthält 5 verschiedene Tasks, die nacheinander durchgeführt werden sollten.
Diese Tasks entsprechen 5 verschiedene Rollen, die mehrere Teilnehmer (2 Personen oder mehr) nach dem Team-Translating Prinzip abwechselnd übernehmen können.
Tip:
Um Konflikte mit dem Übersetzungs-Tool (hier Crowdin) zu vermeiden,
sollte man erst mit den Punkten 2.,3. und 4 anfangen, wenn Task Nr. 1 abgeschlossen ist.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.