Add a new document

[jimcat8]

Author checklist (Completed by original Author)

• Good fit for the Rocky Linux project? Title and Author Metatags inserted ?
• If applicable, steps and instructions have been tested to work
• Initial self-review to fix basic typos and grammar completed

Rocky Documentation checklist (Completed by Rocky team)

• 1st Pass (Document is good fit for project and author checklist completed)
• 2nd Pass (Technical Review - check for technical correctness)
• 3rd Pass (Detailed Editorial Review and Peer Review)
• Final approval (Final Review)

[github-actions]

Test results for a6ba085:

Number of broken URLs: 17

URL,RESULT,FILENAME
 https://repocompare.rockylinux.org,failed,release_notes/8_5.md
 https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=$basearch&infra=$infra&content=$contentdir,failed,books/admin_guide/13-softwares.md
 https://coding.tools/regex-tester,failed,books/sed_awk_grep/1_regular_expressions_vs_wildcards.md
 https://ftp.gnu.org/gnu/hello/hello-2.12.tar.gz,failed,labs/systems_administration_I/lab7-software_management.md
 https://support.torproject.org/glossary/pluggable-transports/,failed,guides/proxies/tor_relay.md
 https://wiki.rockylinux.org/team/release_engineering/debranding/,failed,guides/package_management/package_debranding.md
 http://$(hostname):8080,failed,guides/repositories/pulp_fetch_upload.md
 https://IP:11443/,failed,guides/network/unifi_os.md
 https://git.launchpad.net/cloud-init,failed,guides/virtualization/cloud-init/07_contributing.md
 https://ftp.gnu.org/gnu/tar/,failed,guides/backup/tar.md
 https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf,failed,guides/hardware/ipmi_management.md
 https://www.ossec.net/docs/,failed,guides/web/apache_hardened_webserver/ossec-hids.md
 https://www.packer.io/docs/builders/vsphere/vsphere-iso,failed,guides/automation/templates-automation-packer-vsphere.md
 https://docs.rockylinux.org/guides/contribute/ai-contribution-policy.md,failed,guides/contribute/README.md
 https://andyscott.me,failed,guides/contribute/README.md
 http://your_ip,failed,guides/cms/mediawiki.md
 https://dl.rockylinux.org/pub/rocky/9.6/live/x86_64/,failed,guides/desktop/kde_installation.md

[alemorvan]

@jimcat8 @sspencerwire I don't think this chapter belongs in the administrator's guide.

This admin guide is designed to gradually teach students the skills they need to become Linux administrators.
Its content is the result of careful consideration.
It’s not a matter of simply adding chapters one after another; otherwise, I would have included the PAM guide I wrote in this book myself.

Here’s what I suggest: I propose that you start your own book on security, the "security guide", where you can express yourself in your own style.
You can move the chapters on special authorities and logs (and why not systemd) over there, and that way everyone will be happy.
What do you think about that?

[sspencerwire]

@jimcat8 @sspencerwire I don't think this chapter belongs in the administrator's guide.

This admin guide is designed to gradually teach students the skills they need to become Linux administrators. Its content is the result of careful consideration. It’s not a matter of simply adding chapters one after another; otherwise, I would have included the PAM guide I wrote in this book myself.

Here’s what I suggest: I propose that you start your own book on security, the "security guide", where you can express yourself in your own style. You can move the chapters on special authorities and logs (and why not systemd) over there, and that way everyone will be happy. What do youPer think about that?

Personally, this I think this is an excellent idea and I believe I've suggested this in the past. I think it would also be appropriate for @alemorvan to link to this guide (once finished) from the original admin guide's final chapter and/or in the introduction to the guide (index). It would be a way for @jimcat8 to extend knowledge in more detail as he wishes, while still coordinating with the original document's content, AND keeping it as @alemorvan has intended it to be-a stepping stone for new system administrators. I think this would be a win-win for everyone and would keep emotions from spiraling over content additions that may not be appropriate for the admin guide.

[alemorvan]

Yes, that works for me.
At the end of the administrator's guide, include a conclusion that says: "Okay, now that you're an admin, you can take things further with the security guide we also provide here."

[jimcat8]

Perhaps a separate directory can be created in the "books" directory, named "personalization".

[sspencerwire]

@jimcat8 a new section in the docs for a book (perhaps systems_admin_2, or something similar) seems like a way to get you less resistance to your documentation efforts, while enhancing the documentation content. It's a win for everyone and keeps @alemorvan's document virtually in tact. That doesn't keep you or anyone else from pushing fixes to the content if something is no-longer accurate, but it does make our (my) job easier in terms of reviewing, editing, and merging, without worrying if something goes against the original author's wishes. Antoine has requested to keep these instructions more basic, while advocating for moving some of things that you have pushed and merged into your own book. If you are amenable to this, this is what I'd like to do for you and for all involved. It does require you to pick a document heading, but from there, I can populate it with the content you have authored and you can specify (either to me, or by way of a separate push) how you would like that content organized. Let me know, and thank you for what you do!