├── .github └── workflows │ └── deploy-gh_pages.yml ├── .gitignore ├── Containerfile ├── LICENSE ├── deploy.sh ├── docs ├── .vuepress │ ├── config.js │ ├── public │ │ ├── CNAME │ │ ├── ci-data │ │ │ ├── aws_amis.csv │ │ │ └── aws_amis_kitten_10.csv │ │ ├── images │ │ │ ├── 10-0.png │ │ │ ├── 2023.updated.almafedoraRedhatoverview.png │ │ │ ├── 9-0.png │ │ │ ├── ALBS-structure.svg │ │ │ ├── Comparison-relationship_chart.png │ │ │ ├── ELevate-Testing.svg │ │ │ ├── ELevate-scheme.svg │ │ │ ├── ELevate.svg │ │ │ ├── ELevateNG.svg │ │ │ ├── HowTo-LAMP-server-1.png │ │ │ ├── HowTo-LAMP-server-2.png │ │ │ ├── after-install-nmtui.png │ │ │ ├── after-install-settings-1.png │ │ │ ├── after-install-settings-2.png │ │ │ ├── almalinux-readme.png │ │ │ ├── building-packages-guide_etc-mock.png │ │ │ ├── building-packages-guide_results.png │ │ │ ├── building-packages-guide_rpmbuild.png │ │ │ ├── elections2023 │ │ │ │ ├── Abdullah_As-Sadeed-small.png │ │ │ │ ├── AlexIribarren-small.jpg │ │ │ │ ├── Benny-small.jpg │ │ │ │ ├── JING_LUO.png │ │ │ │ ├── JunYoshida-small.jpg │ │ │ │ └── igor-small.jpg │ │ │ ├── elevate-testing-scheme.svg │ │ │ ├── elevate_action-ID.png │ │ │ ├── elevate_action-type.png │ │ │ ├── elevate_actions-history.png │ │ │ ├── elevate_add-action.png │ │ │ ├── elevate_bulk-result.png │ │ │ ├── elevate_demo-video.png │ │ │ ├── elevate_dump-json.png │ │ │ ├── elevate_dump-result.png │ │ │ ├── elevate_edit-an-action.png │ │ │ ├── elevate_homebar.png │ │ │ ├── elevate_list-of-actions.png │ │ │ ├── elevate_list-of-users.png │ │ │ ├── elevate_search-an-action.png │ │ │ ├── elevate_source.png │ │ │ ├── errata_example.png │ │ │ ├── errata_feed.png │ │ │ ├── help-and-support-chat-element-1.png │ │ │ ├── help-and-support-chat-element-2.png │ │ │ ├── help-and-support-chat-element-3.png │ │ │ ├── help-and-support-paste-1.png │ │ │ ├── help-and-support-paste-2.png │ │ │ ├── help-and-support-paste-3.png │ │ │ ├── help-and-support-paste-4.png │ │ │ ├── hero.png │ │ │ ├── installation-guide-begin-installation.gif │ │ │ ├── installation-guide-encryption.gif │ │ │ ├── installation-guide-installation-destination.png │ │ │ ├── installation-guide-installation-language.png │ │ │ ├── installation-guide-installation-summary.png │ │ │ ├── installation-guide-kdump.png │ │ │ ├── installation-guide-keyboard.gif │ │ │ ├── installation-guide-language-support.png │ │ │ ├── installation-guide-macos-usb.png │ │ │ ├── installation-guide-network.png │ │ │ ├── installation-guide-reboot.png │ │ │ ├── installation-guide-root.gif │ │ │ ├── installation-guide-security-profiles.gif │ │ │ ├── installation-guide-software-selection.gif │ │ │ ├── installation-guide-time-date.gif │ │ │ ├── installation-guide-user.gif │ │ │ ├── installation-guide-welcome-menu.png │ │ │ ├── kitten10-screenshot.png │ │ │ ├── live-media-9-gnome.png │ │ │ ├── live-media-9-kde.png │ │ │ ├── live-media-9-mate.png │ │ │ ├── live-media-9-xfce.png │ │ │ ├── logo.png │ │ │ ├── migration.svg │ │ │ ├── openQA-All_Tests.png │ │ │ ├── openQA-Job_Groups.png │ │ │ ├── openQA-Live_View.png │ │ │ ├── openQA-Search.png │ │ │ ├── openQA-Test_Details.png │ │ │ ├── openQA-Test_Result_Overview.png │ │ │ ├── openQA-main_page.png │ │ │ ├── openQA-needle.png │ │ │ ├── openQA-video_recording.png │ │ │ ├── openscap-9_evaluation_report.png │ │ │ ├── openscap-9_full_security_guide.png │ │ │ ├── openscap-9_oval_scan.png │ │ │ ├── openscap-9_workbench.png │ │ │ ├── openscap-9_workbench_profiles.png │ │ │ ├── openscap-9_workbench_report.png │ │ │ ├── openscap-9_workbench_scan.png │ │ │ ├── openscap-oval-report.png │ │ │ ├── openscap-workbench-message.png │ │ │ ├── openscap-workbench-report.png │ │ │ ├── openscap-workbench-scanning.png │ │ │ ├── openscap_evaluation-report.png │ │ │ ├── openscap_security-guide-1.png │ │ │ ├── openscap_security-guide-2.png │ │ │ ├── openscap_security-policy.png │ │ │ ├── openscap_workbench-menu.png │ │ │ ├── openscap_workbench.png │ │ │ ├── release-notes_almalinux-install-source.png │ │ │ ├── sbom-details.png │ │ │ ├── sbom-details2.png │ │ │ ├── sbom-guide-bs-details.png │ │ │ ├── sbom-guide-bs-rpm-hash.png │ │ │ ├── sbom-guide-bs-search.png │ │ │ ├── sbom-guide-bs-select-arch.png │ │ │ ├── sbom-guide-cas-example.png │ │ │ ├── sbom-guide-live-example-auth-by-binary-file.gif │ │ │ ├── sbom-guide-live-example-auth-rpm-hash.gif │ │ │ ├── weblate-almalinux-foundation.png │ │ │ ├── weblate-ask-new-lang.png │ │ │ ├── weblate-create-account.png │ │ │ ├── weblate-send-translations.png │ │ │ ├── weblate-translate-website.png │ │ │ ├── wsl-alma.png │ │ │ ├── wsl-install.png │ │ │ ├── wsl-ms-store.png │ │ │ ├── wsl-powershell.png │ │ │ └── wsl.jpeg │ │ ├── robots.txt │ │ └── sitemap.xml │ └── styles │ │ ├── index.styl │ │ └── palette.styl ├── Comparison.md ├── Contribute-to-AlmaLinux-Build-System.md ├── Contribute-to-Documentation.md ├── Contribute-to-Packaging.md ├── Contribute-to-Testing.md ├── Contribute.md ├── Election2022.md ├── FAQ.md ├── Help-and-Support.md ├── Help-translating-site.md ├── Howto.md ├── LiveMedia.md ├── Mirrors.md ├── README.md ├── Transparency.md ├── alesco.md ├── alesco │ ├── meeting-minutes.md │ └── meeting-minutes │ │ ├── 2024-07-24.md │ │ ├── 2024-08-21.md │ │ ├── 2024-09-04.md │ │ ├── 2024-10-02.md │ │ ├── 2025-01-08.md │ │ ├── 2025-01-22.md │ │ ├── 2025-04-02.md │ │ ├── 2025-04-16.md │ │ ├── 2025-05-14.md │ │ └── 2025-05-28.md ├── cloud │ ├── AWS.md │ ├── AWS_AMIS.md │ ├── Azure.md │ ├── EC2-instance-connect.md │ ├── Generic-cloud-on-local.md │ ├── Generic-cloud.md │ ├── Google.md │ ├── OCI.md │ ├── OpenNebula.md │ ├── README.md │ └── cloud-changelog.md ├── community │ ├── coc.md │ └── platforms.md ├── containers │ ├── README.md │ └── docker-images.md ├── development │ ├── AWS_AMIS_kitten_10.md │ ├── AlmaLinux-Build-System.md │ ├── Modified-packages.md │ ├── Packaging.md │ ├── almalinux-os-kitten-10.md │ ├── building-almalinux-iso-locally.md │ ├── openQA.md │ └── private-keys │ │ ├── package-signing.md │ │ └── secure-boot.md ├── documentation │ ├── after-installation-guide.md │ ├── epel-and-rpmfusion.md │ ├── errata.md │ ├── guides.md │ ├── installation-guide.md │ ├── kickstart-guide.md │ ├── migration-guide.md │ ├── openQA.md │ ├── openscap-guide-for-9.md │ ├── openscap-guide.md │ ├── oval-streams.md │ ├── package-building-guide.md │ ├── raspberry-pi.md │ ├── sbom-guide.md │ └── wsl.md ├── election2023.md ├── elevate │ ├── Changelog.md │ ├── Contribution-guide.md │ ├── ELevate-NG-testing-guide.md │ ├── ELevate-frequent-issues.md │ ├── ELevate-offline-guide.md │ ├── ELevate-quickstart-guide.md │ ├── ELevate-testing-guide.md │ ├── ELevating-CentOS6-to-CentOS7.md │ ├── ELevating-CentOS7-to-AlmaLinux-9.md │ └── README.md ├── gsoc.md ├── installation │ └── vagrant-boxes.md ├── migration │ └── README.md ├── release-notes │ ├── 10.0-beta.md │ ├── 10.0.md │ ├── 8.10-beta.md │ ├── 8.10.md │ ├── 8.3-beta.md │ ├── 8.3-rc.md │ ├── 8.3.md │ ├── 8.4-arm.md │ ├── 8.4-beta-arm.md │ ├── 8.4-beta.md │ ├── 8.4.md │ ├── 8.5-beta-ppc.md │ ├── 8.5-beta.md │ ├── 8.5-ppc.md │ ├── 8.5.md │ ├── 8.6-beta.md │ ├── 8.6.md │ ├── 8.7-beta.md │ ├── 8.7.md │ ├── 8.8-beta.md │ ├── 8.8.md │ ├── 8.9-beta.md │ ├── 8.9.md │ ├── 9.0-beta.md │ ├── 9.0.md │ ├── 9.1-beta.md │ ├── 9.1.md │ ├── 9.2-beta.md │ ├── 9.2.md │ ├── 9.3-beta.md │ ├── 9.3.md │ ├── 9.4-beta.md │ ├── 9.4.md │ ├── 9.5-beta.md │ ├── 9.5.md │ ├── 9.6-beta.md │ ├── 9.6.md │ ├── README.md │ ├── almalinux-install-source.png │ └── kitten-10.md ├── repos │ ├── AlmaLinux.md │ ├── CentOS.md │ ├── Extras.md │ ├── README.md │ └── Synergy.md ├── series │ ├── LAMP-server.md │ ├── README.md │ ├── nginx │ │ ├── NginxSeriesA01.md │ │ ├── NginxSeriesA02R8.md │ │ ├── NginxSeriesA02R91.md │ │ ├── NginxSeriesA02R92.md │ │ ├── NginxSeriesA03.md │ │ ├── NginxSeriesA04P1.md │ │ └── README.md │ └── system │ │ ├── README.md │ │ ├── SystemSeriesA01.md │ │ ├── SystemSeriesA02.md │ │ ├── SystemSeriesA03.md │ │ ├── SystemSeriesA03R8.md │ │ ├── SystemSeriesA03R9.md │ │ ├── SystemSeriesA04.md │ │ ├── SystemSeriesA05.md │ │ ├── SystemSeriesA06.md │ │ ├── SystemSeriesA07.md │ │ ├── SystemSeriesA08.md │ │ ├── SystemSeriesA09.md │ │ └── SystemSeriesA10.md └── sigs │ ├── Atomic.md │ ├── Build-System.md │ ├── Certification.md │ ├── Cloud.md │ ├── Core.md │ ├── HPCandAI.md │ ├── Infrastructure.md │ ├── LiveMedia.md │ ├── Marketing.md │ ├── Migration.md │ ├── ProcessForCreatingNewSIG.md │ ├── README.md │ ├── marketing │ └── indico.md │ └── sigproposaltemplate.md ├── images └── hero.png └── package.json /.github/workflows/deploy-gh_pages.yml: -------------------------------------------------------------------------------- 1 | 2 | name: Deploy to GitHub Pages 3 | on: 4 | push: 5 | branches: 6 | - master 7 | jobs: 8 | build-and-deploy: 9 | if: github.repository == 'AlmaLinux/wiki' 10 | runs-on: ubuntu-latest 11 | steps: 12 | - name: Checkout 13 | uses: actions/checkout@master 14 | 15 | - name: Build and Deploy 16 | uses: jenkey2011/vuepress-deploy@master 17 | env: 18 | ACCESS_TOKEN: ${{ secrets.ACCESS_TOKEN }} 19 | TARGET_REPO: AlmaLinux/wiki 20 | TARGET_BRANCH: gh-pages 21 | BUILD_SCRIPT: yarn && yarn docs:build 22 | BUILD_DIR: docs/.vuepress/dist/ 23 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | yarn.lock 3 | -------------------------------------------------------------------------------- /Containerfile: -------------------------------------------------------------------------------- 1 | FROM docker.io/library/node:lts-alpine AS builder 2 | LABEL stage=auto-clean-stage1 3 | RUN mkdir -p /wiki/tmp 4 | COPY . /wiki/tmp 5 | WORKDIR /wiki/tmp 6 | RUN yarn 7 | 8 | FROM docker.io/library/node:lts-alpine 9 | RUN mkdir /wiki 10 | WORKDIR /wiki 11 | COPY --from=builder /wiki/tmp/package.json /wiki/package.json 12 | COPY --from=builder /wiki/tmp/node_modules /wiki/node_modules 13 | COPY --from=builder /wiki/tmp/yarn.lock /wiki/yarn.lock 14 | CMD yarn run docs:dev 15 | -------------------------------------------------------------------------------- /deploy.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # description: wiki.almalinux.org content deployment tool. 3 | 4 | set -e 5 | 6 | npm run docs:build || yarn run docs:build || yarnpkg run docs:build 7 | 8 | pushd docs/.vuepress/dist 9 | 10 | git init 11 | git add -A 12 | git commit -m 'deploy' 13 | 14 | git push -f git@github.com:AlmaLinux/wiki.git master:gh-pages 15 | 16 | popd 17 | -------------------------------------------------------------------------------- /docs/.vuepress/public/CNAME: -------------------------------------------------------------------------------- 1 | wiki.almalinux.org 2 | -------------------------------------------------------------------------------- /docs/.vuepress/public/images/10-0.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/10-0.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/2023.updated.almafedoraRedhatoverview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/2023.updated.almafedoraRedhatoverview.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/9-0.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/9-0.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/Comparison-relationship_chart.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/Comparison-relationship_chart.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/HowTo-LAMP-server-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/HowTo-LAMP-server-1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/HowTo-LAMP-server-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/HowTo-LAMP-server-2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/after-install-nmtui.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/after-install-nmtui.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/after-install-settings-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/after-install-settings-1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/after-install-settings-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/after-install-settings-2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/almalinux-readme.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/almalinux-readme.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/building-packages-guide_etc-mock.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/building-packages-guide_etc-mock.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/building-packages-guide_results.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/building-packages-guide_results.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/building-packages-guide_rpmbuild.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/building-packages-guide_rpmbuild.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elections2023/Abdullah_As-Sadeed-small.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elections2023/Abdullah_As-Sadeed-small.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elections2023/AlexIribarren-small.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elections2023/AlexIribarren-small.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elections2023/Benny-small.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elections2023/Benny-small.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elections2023/JING_LUO.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elections2023/JING_LUO.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elections2023/JunYoshida-small.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elections2023/JunYoshida-small.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elections2023/igor-small.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elections2023/igor-small.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_action-ID.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_action-ID.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_action-type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_action-type.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_actions-history.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_actions-history.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_add-action.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_add-action.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_bulk-result.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_bulk-result.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_demo-video.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_demo-video.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_dump-json.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_dump-json.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_dump-result.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_dump-result.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_edit-an-action.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_edit-an-action.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_homebar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_homebar.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_list-of-actions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_list-of-actions.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_list-of-users.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_list-of-users.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_search-an-action.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_search-an-action.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/elevate_source.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/elevate_source.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/errata_example.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/errata_example.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/errata_feed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/errata_feed.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-chat-element-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-chat-element-1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-chat-element-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-chat-element-2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-chat-element-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-chat-element-3.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-paste-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-paste-1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-paste-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-paste-2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-paste-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-paste-3.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/help-and-support-paste-4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/help-and-support-paste-4.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/hero.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/hero.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-begin-installation.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-begin-installation.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-encryption.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-encryption.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-installation-destination.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-installation-destination.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-installation-language.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-installation-language.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-installation-summary.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-installation-summary.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-kdump.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-kdump.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-keyboard.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-keyboard.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-language-support.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-language-support.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-macos-usb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-macos-usb.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-network.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-network.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-reboot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-reboot.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-root.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-root.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-security-profiles.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-security-profiles.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-software-selection.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-software-selection.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-time-date.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-time-date.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-user.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-user.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/installation-guide-welcome-menu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/installation-guide-welcome-menu.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/kitten10-screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/kitten10-screenshot.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/live-media-9-gnome.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/live-media-9-gnome.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/live-media-9-kde.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/live-media-9-kde.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/live-media-9-mate.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/live-media-9-mate.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/live-media-9-xfce.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/live-media-9-xfce.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/logo.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-All_Tests.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-All_Tests.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-Job_Groups.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-Job_Groups.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-Live_View.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-Live_View.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-Search.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-Search.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-Test_Details.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-Test_Details.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-Test_Result_Overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-Test_Result_Overview.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-main_page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-main_page.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-needle.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-needle.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openQA-video_recording.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openQA-video_recording.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_evaluation_report.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_evaluation_report.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_full_security_guide.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_full_security_guide.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_oval_scan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_oval_scan.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_workbench.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_workbench.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_workbench_profiles.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_workbench_profiles.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_workbench_report.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_workbench_report.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-9_workbench_scan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-9_workbench_scan.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-oval-report.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-oval-report.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-workbench-message.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-workbench-message.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-workbench-report.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-workbench-report.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap-workbench-scanning.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap-workbench-scanning.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap_evaluation-report.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap_evaluation-report.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap_security-guide-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap_security-guide-1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap_security-guide-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap_security-guide-2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap_security-policy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap_security-policy.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap_workbench-menu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap_workbench-menu.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/openscap_workbench.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/openscap_workbench.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/release-notes_almalinux-install-source.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/release-notes_almalinux-install-source.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-details.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-details.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-details2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-details2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-bs-details.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-bs-details.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-bs-rpm-hash.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-bs-rpm-hash.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-bs-search.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-bs-search.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-bs-select-arch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-bs-select-arch.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-cas-example.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-cas-example.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-live-example-auth-by-binary-file.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-live-example-auth-by-binary-file.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/sbom-guide-live-example-auth-rpm-hash.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/sbom-guide-live-example-auth-rpm-hash.gif -------------------------------------------------------------------------------- /docs/.vuepress/public/images/weblate-almalinux-foundation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/weblate-almalinux-foundation.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/weblate-ask-new-lang.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/weblate-ask-new-lang.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/weblate-create-account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/weblate-create-account.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/weblate-send-translations.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/weblate-send-translations.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/weblate-translate-website.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/weblate-translate-website.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/wsl-alma.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/wsl-alma.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/wsl-install.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/wsl-install.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/wsl-ms-store.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/wsl-ms-store.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/wsl-powershell.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/wsl-powershell.png -------------------------------------------------------------------------------- /docs/.vuepress/public/images/wsl.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/.vuepress/public/images/wsl.jpeg -------------------------------------------------------------------------------- /docs/.vuepress/public/robots.txt: -------------------------------------------------------------------------------- 1 | User-agent: * 2 | Disallow: /cgi-bin/ 3 | Sitemap: https://wiki.almalinux.org/sitemap.xml -------------------------------------------------------------------------------- /docs/.vuepress/styles/index.styl: -------------------------------------------------------------------------------- 1 | body 2 | font-family $bodyFontFamily 3 | 4 | h1 5 | font-size $h1FontSize 6 | 7 | h2 8 | font-size $h2FontSize 9 | 10 | table thead th 11 | background-color $theadBgColor 12 | color $theadFontColor 13 | font-weight $theadFontWeight 14 | 15 | tr:nth-child(2n) 16 | background-color $tipBgColor 17 | 18 | .navbar 19 | background-color $navbarBgColor 20 | 21 | .navbar .site-name 22 | color $navbarFontColor 23 | font-size $navbarFontSize 24 | font-weight $navbarFontWeight 25 | 26 | .navbar .links 27 | background-color $navbarBgColor 28 | font-family $navbarFontFamily 29 | 30 | .nav-links a 31 | color $navbarFontColor 32 | font-size $navbarLinksFontSize 33 | font-weight $navbarLinksFontWeight 34 | 35 | .nav-links a:hover 36 | color $navbarLinksHoverColor 37 | 38 | .sidebar .nav-links 39 | background-color $navbarBgColor 40 | 41 | .sidebar-heading 42 | font-size $sidebarFontSize 43 | font-weight $sidebarFontWeight 44 | 45 | .sidebar 46 | & > .sidebar-links 47 | & > li > a.sidebar-link 48 | font-size $sidebarFontSize 49 | font-weight $sidebarFontWeight 50 | 51 | .custom-block.warning 52 | background-color $warningBgColor 53 | border-color $warningBorderColor 54 | 55 | .custom-block.warning .custom-block-title 56 | color: $warningTitleColor 57 | 58 | .custom-block.tip 59 | background-color $tipBgColor 60 | border-color $tipBorderColor 61 | 62 | .custom-block.danger 63 | background-color $dangerBgColor 64 | border-color $dangerBorderColor 65 | -------------------------------------------------------------------------------- /docs/.vuepress/styles/palette.styl: -------------------------------------------------------------------------------- 1 | // Body 2 | $contentWidth = auto 3 | $h1FontSize = 1.8rem 4 | $h2FontSize = 1.5rem 5 | $bodyFontFamily = -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Arial,"Noto Sans",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji" !important 6 | 7 | // Links color 8 | $accentColor = #017698 9 | 10 | // Navbar 11 | $navbarBgColor = #082336 !important 12 | $navbarFontColor = #ffffff !important 13 | $navbarLinksHoverColor = #0069DA !important 14 | $navbarFontSize = 1.4rem !important 15 | $navbarLinksFontSize = 15px !important 16 | $navbarFontWeight = 600 !important 17 | $navbarLinksFontWeight = 600 !important 18 | $navbarFontFamily = montserrat,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,oxygen-sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif,apple color emoji,segoe ui emoji,segoe ui symbol !important 19 | 20 | // Sidebar 21 | $sidebarFontSize = 1em !important 22 | $sidebarFontWeight = 600 !important 23 | 24 | // Code block 25 | $codeBgColor = #264154 26 | 27 | // Warning 28 | $warningBgColor = #FFCB1250 29 | $warningBorderColor = #e1ad00 30 | $warningTitleColor = #e1ad00 31 | 32 | // Tip 33 | $tipBgColor = #dcd7d740 34 | $tipBorderColor = #68bc11 35 | 36 | // Danger 37 | $dangerBgColor = #ff6e7140 38 | $dangerBorderColor = #e1282b 39 | 40 | // Tables 41 | $theadBgColor = #304b5e 42 | $theadFontColor = #ffffff 43 | $theadFontWeight = 600 44 | -------------------------------------------------------------------------------- /docs/Contribute-to-Testing.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Testing' 3 | --- 4 | 5 | ###### last updated: 2024-08-30 6 | 7 | # Contribute to Testing 8 | 9 | At AlmaLinux, we're dedicated to providing a high-quality experience for our community. We believe that thorough testing is crucial to guaranteeing the quality and reliability of the distribution. We put a lot of effort into testing and making sure everything works smoothly regardless of where or what you run. 10 | 11 | ## Beta testing 12 | 13 | New AlmaLinux OS Beta and Stable versions are released every six months. We rely on our community to help us test Beta releases by providing feedback, reporting bugs, and identifying issues. Your input is crucial in ensuring our production releases are smooth and successful and we welcome your participation in this process. 14 | 15 | If you're interested in contributing to Beta testing, please, see the installation/upgrade instructions in [release notes](/release-notes/) and join the [testing](https://chat.almalinux.org/almalinux/channels/testing) chat channel to stay informed. 16 | 17 | ## openQA 18 | 19 | AlmaLinux has implemented openQA - a tool created and maintained by SUSE - for the automation of testing. With openQA we set up testing environments and scenarios, making it easier to run tests to reproduce the installation process of our images. This helps us identify and fix any issues with the installer, graphics, branding, and visual defects, allowing our developers to quickly and efficiently test AlmaLinux and catch any problems before they're released to the public. 20 | 21 | openQA is publicly available at [openqa.almalinux.org](https://openqa.almalinux.org/) and users can monitor the testing progress and see the results as screenshots and video recordings. 22 | 23 | We have long-term goals of improving our openQA infrastructure with additional tests and expanding our openQA documentation on our wiki. If you're interested in contributing to openQA, please, see more details on the [openQA](/development/openQA) wiki page and join the [testing](https://chat.almalinux.org/almalinux/channels/testing) chat channel to stay updated and involved. 24 | 25 | ## Updated packages 26 | 27 | AlmaLinux OS is binary compatible with RHEL® and part ways in some matters. Before releasing an updated package with a patch or security fix, the AlmaLinux OS Foundation invites the community to participate in testing before its official release. 28 | 29 | If you're interested in testing, please, join the [testing](https://chat.almalinux.org/almalinux/channels/testing) and [release engineering](https://chat.almalinux.org/almalinux/channels/engineeringreleng) chat channels to stay updated and involved. 30 | 31 | ## Migration and Upgrades 32 | 33 | AlmaLinux offers one project for upgrading your operating system in-place ([ELevate](https://wiki.almalinux.org/elevate/)), and one for migrating to AlmaLinux ([AlmaLinux-deploy](https://wiki.almalinux.org/documentation/migration-guide.html))! We're actively working on improving them with the community's help, and invite you to join us. 34 | 35 | If you're interested in participating check the [Migration](/migration/) wiki section, [Migration SIG](/sigs/Migration) page and join the [Migration SIG](https://chat.almalinux.org/almalinux/channels/migration) chat channel to get involved. You can assist AlmaLinux in: 36 | * Add a 3rd party repository support to the ELevate Project and test it. 37 | * Testing new features and expanding the documentation. 38 | * Identifying and reporting bugs as well as resolving known issues to make the migration process smoother. Bugs should be reported to the corresponding repositories - [ELevate leapp repository](https://github.com/AlmaLinux/leapp-repository) or [AlmaLinux migration tool](https://github.com/AlmaLinux/almalinux-deploy). 39 | 40 | #### Trademarks 41 | 42 | Red Hat, and Red Hat Enterprise Linux, are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries. 43 | -------------------------------------------------------------------------------- /docs/Help-translating-site.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Help translating AlmaLinux.org' 3 | --- 4 | 5 | The content of [almalinux.org](https://almalinux.org/) is localized and translated by a large community of contributors through [Weblate](https://hosted.weblate.org/engage/almalinux/). This guide will guide you through contributing to those translations. 6 | 7 | [![Translation status](https://hosted.weblate.org/widget/almalinux/website-backend/multi-auto.svg)](https://hosted.weblate.org/engage/almalinux/) 8 | 9 | # Help translating the site 10 | 11 | The translations that get submitted through Weblate are automatically submitted to the [almalinux.org repo](https://github.com/AlmaLinux/almalinux.org) as a pull request from Weblate. Pull requests from Weblate are reviewed by a member of the marketing SIG or another team lead, and merged as appropriate. 12 | 13 | If you would like to help contribute to translations, you can do so by following the directions below! 14 | 15 | ## Create an account 16 | 17 | First you need to create a [Weblate](https://hosted.weblate.org/accounts/register/) account. You could use accounts from other service providers or fill in the form shown below to create it. 18 | 19 | ![image](/images/weblate-create-account.png) 20 | 21 | ## Starting to translate 22 | 23 | After creating an account we need to head to [AlmaLinux Foundation Weblate](https://hosted.weblate.org/projects/almalinux/): 24 | 25 | ![image](/images/weblate-almalinux-foundation.png) 26 | 27 | Choosing each one of the two should send you to a page similar to the image below. 28 | 29 | ![image](/images/weblate-translate-website.png) 30 | 31 | Then choose the language you want to translate to. For this example, I'll choose [Hebrew](https://hosted.weblate.org/translate/almalinux/website-backend/he/?q=state:%3Ctranslated). 32 | 33 | ![image](/images/weblate-send-translations.png) 34 | 35 | After translating from English to your chosen language (.e.g Hebrew) press on "Save and continue" and your translation will be sent eventually as a PR to the [almalinux.org repo](https://github.com/AlmaLinux/almalinux.org) and reviewed by a member of the marketing SIG or another team lead, then merged as appropriate. 36 | 37 | ## Request new languages 38 | 39 | You can request new languages to be added by creating a ticket in [GitHub issues](https://github.com/AlmaLinux/almalinux.org/issues), like so: 40 | 41 | ![image](/images/weblate-ask-new-lang.png) -------------------------------------------------------------------------------- /docs/Howto.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Howtos" 3 | --- 4 | 5 | # AlmaLinux Howto Guides (external) 6 | 7 | ## Installation Guides 8 | 9 | - [EPEL and RPM Fusion](/documentation/epel-and-rpmfusion) 10 | - [Nginx](https://orcacore.com/install-nginx-web-server-almalinux-9/) 11 | - [Foreman](https://www.how2shout.com/linux/how-to-install-foreman-on-rocky-or-almalinux-8/) 12 | - [phpMyAdmin](https://wiki.crowncloud.net/?How_to_Install_phpMyAdmin_on_AlmaLinux_8) 13 | - [Apache Web Server](https://www.linode.com/docs/guides/install-and-use-apache-on-almalinux/) 14 | - [DirectAdmin](https://www.techrepublic.com/article/how-to-install-cpanelwhm-alternative-directadmin-on-almalinux/) 15 | - [Redis](https://dev.to/inneutroncloud/how-to-install-redis-on-almalinux-8-52k) 16 | - [MongoDB](https://mobilemonitoringsolutions.com/how-to-install-the-nosql-database-server-mongodb-on-linux/) 17 | - [Caddy](https://orcacore.com/install-configure-caddy-almalinux-8/) 18 | - [OpenSSL 1.1.1i](https://www.hostnextra.com/kb/how-to-install-openssl-1-1-1i-on-almalinux/) 19 | - [WordPress with Nginx, PHP 8.1, and MariaDB](https://thishosting.rocks/how-to-install-wordpress-on-almalinux/) 20 | - [Java](https://linuxstans.com/how-to-install-java-almalinux/) 21 | 22 | ## Remote Desktop 23 | 24 | - [Remote Desktop Access with VNC](https://www.answertopia.com/almalinux/almalinux-remote-desktop-access-with-vnc/) 25 | - [Displaying Applications Remotely (X11 Forwarding)](https://www.answertopia.com/almalinux/displaying-almalinux-applications-remotely-x11-forwarding/) 26 | 27 | ## Virtualization 28 | 29 | - [vagrant-libvirt plugin](https://docs.euro-linux.com/HowTo/vagrant-with-libvirt/) 30 | - [Docker CE](https://docs.docker.com/engine/install/rhel/) 31 | - [XCP-ng VM Tools](https://techviewleo.com/install-xcp-ng-vm-tools-on-centos-almalinux/) 32 | 33 | ## Authentication & Security 34 | 35 | - [Configuring SSH Key-based Authentication](https://www.answertopia.com/almalinux/configuring-ssh-key-based-authentication-on-almalinux/) 36 | - [Enabling SSH 2FA](https://www.techrepublic.com/article/how-to-enable-ssh-2fa-on-almalinux-for-more-secure-logins/) 37 | 38 | ## Networking 39 | 40 | - [Network Configuration with NetworkManager](https://www.answertopia.com/almalinux/almalinux-network-management/) 41 | - [Firewall Configuration with firewalld](https://www.answertopia.com/almalinux/almalinux-firewall-configuration-with-firewalld/) 42 | - [NFS File Sharing](https://www.answertopia.com/almalinux/using-nfs-on-almalinux-to-share-files-with-remote-systems/) 43 | - [SAMBA File Sharing](https://www.answertopia.com/almalinux/sharing-files-between-almalinux-and-windows-with-samba/) 44 | 45 | # ARM 46 | 47 | - [ESXI ARM support](https://williamlam.com/2021/07/almalinux-os-8-4-on-esxi-arm.html) 48 | - [Raspberry Pi](https://github.com/AlmaLinux/raspberry-pi/) 49 | 50 | ## Other 51 | 52 | - [Creating a mirror](https://gnulinux.ro/blog-page-8312-how-to-create-a-public-official-mirror-for-almalinux-in-three-steps) 53 | - [Unattended installation using kickstart](./documentation/kickstart-guide.md) 54 | -------------------------------------------------------------------------------- /docs/LiveMedia.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Live Media" 3 | --- 4 | # Live Media 5 | 6 | ## About Live Media 7 | 8 | Live Media is a way to try AlmaLinux on your computer without installing it to the hard drive. You can run it from a USB or DVD to preview and for system rescue needs. Images support both BIOS and UEFI, including Secure Boot mode. 9 | 10 | ## Live Media Options 11 | There are a few AlmaLinux Live Media Options: 12 | 13 | * GNOME Mini: contains a core GNOME environment with Firefox browser 14 | * GNOME: contains a full GNOME environment with popular workstation applications like LibreOffice, Thunderbird and so on. 15 | 16 | ![image](/images/live-media-9-gnome.png) 17 | 18 | * KDE: contains KDE desktop environment with Firefox browser, Konqueror browser, and applications like LibreOffice, Thunderbird, etc. 19 | 20 | ![image](/images/live-media-9-kde.png) 21 | 22 | * MATE: contains MATE desktop environment with Firefox browser, LibreOffice and other applications. 23 | 24 | ![image](/images/live-media-9-mate.png) 25 | 26 | * XFCE: contains XFCE desktop environment with Firefox browser, Thunderbird, LibreOffice, and more applications. 27 | 28 | ![image](/images/live-media-9-xfce.png) 29 | 30 | ## How to download and write images 31 | 32 | The first step is to download an AlmaLinux image: 33 | | | | | 34 | | --- | --- | --- | 35 | | AlmaLinux 8 | [x86\_64](https://repo.almalinux.org/almalinux/8/live/x86_64/) | | 36 | | AlmaLinux 9 | [x86\_64](https://repo.almalinux.org/almalinux/9/live/x86_64/) | [aarch64](https://repo.almalinux.org/almalinux/9/live/aarch64/) | 37 | 38 | Then it all depends on what OS you use. 39 | 40 | **Linux:** 41 | 42 | It is simple to use the dd command for any Linux OS. 43 | 44 | Insert your target USB and locate it. There are different ways to do it but here are some of them: 45 | 46 | * ` sudo fdisk -l` - this command shows you the connected block storage devices, including the USB devices. 47 | 48 | * `lsblk` - this command gives you all the available block storage devices, including the USB block storage devices. 49 | 50 | * `sudo blkid` - this command gives you the same information as `lsblk`, but you have to rub it as root. 51 | 52 | You need to look for /dev/sda or /dev/sdb or /dev/sdc, which is your target USB. 53 | 54 | 55 | After you found out the location of your target USB, navigate to the location of your source ISO. Run dd command to copy files from ISO to USB: 56 | 57 | `sudo dd if=/AlmaLinux-8-x86_64-Live-GNOME-Mini-beta-1.iso of=/dev/sdc status=progress` 58 | 59 | `dd`: Start the dd command to write DVD/CD iso image. 60 | `if=AlmaLinux-8-x86_64-Live-GNOME-Mini-beta-1.iso`: path to the input file. 61 | `of=/dev/sdc` : path to destination USB disk/stick. 62 | `status=progress`: display a progress bar while writing the image to the USB stick such as /dev/sdb. 63 | That’s all! You now have ready Live AlmaLinux on a USB stick. 64 | 65 | :::warning 66 | This example is for AlmaLinux 8. Don't forget to replace **8** version with **9** to work with AlmaLinux 9 image. 67 | ::: 68 | 69 | **Windows:** 70 | 71 | For Windows OS there is a helpful free and open-source application - [Rufus](https://rufus.ie/). 72 | 73 | Open the application, choose your target USB, ISO you need to burn, press start - and Live OS is ready to run. 74 | 75 | **macOS:** 76 | 77 | The cross-platform tool [Fedora Media Writer](https://fedoraproject.org/workstation/download#fedora-media-writer) is used to write images on macOS. It is simple too. Open Fedora Media Writer, select the AlmaLinux ISO, choose the correct options, then write the image. 78 | 79 | More details and information about AlmaLinux Live Media can be found on [Live Media SIG](https://wiki.almalinux.org/sigs/LiveMedia.html). 80 | -------------------------------------------------------------------------------- /docs/README.md: -------------------------------------------------------------------------------- 1 | # About AlmaLinux Wiki 2 | 3 | [AlmaLinux](https://almalinux.org/) is an Open Source and forever-free enterprise Linux distribution, governed and driven by the community, focused on long-term stability and a robust production grade platform. AlmaLinux OS is binary compatible with RHEL®. The [AlmaLinux OS Foundation](Transparency.md) was established as a 501(c)(6) non-profit to steward ownership and governance of the project. The foundation includes over 400 individual members, over 100 Mirror sponsors, and over 25 Corporate sponsors. 4 | 5 |
6 |
7 | 8 |
9 |
10 |

Quick Links & Resources

11 | 42 |
43 |
44 | 45 | ## Contributions to the Wiki 46 | 47 | There are many ways to contribute to the wiki! To see how, check out the [Contributing to Documentation](https://wiki.almalinux.org/Contribute-to-Documentation.html) guide. Before submitting pull requests, always make sure that your updates will build and display correctly, by testing in your local environment using `yarn docs:dev`. 48 | 49 | ### Transparency Statement 50 | 51 | * We are community-owned, which requires transparency. Here is our [progress toward that goal](Transparency.md). 52 | * Minutes from the [meetings of the board of directors](Transparency.md#-minutes-of-almalinux-os-foundation-board-meetings) 53 | 54 | ### License 55 | This Wiki content is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/). 56 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes.md: -------------------------------------------------------------------------------- 1 | --- 2 | Title: 'ALESCo Meeting Minutes' 3 | --- 4 | 5 | Each meeting of ALESCo is public, and future meetings can be found on [events.almalinux.org](https://events.almalinux.org/category/7/) 6 | 7 | # ALESCo Meeting Minutes 8 | - [May 28, 2025](/alesco/meeting-minutes/2025-05-28) 9 | - [May 14, 2025](/alesco/meeting-minutes/2025-05-14) 10 | - [April 16, 2025](/alesco/meeting-minutes/2025-04-16) 11 | - [April 2, 2025](/alesco/meeting-minutes/2025-04-02) 12 | - [January 22, 2025](/alesco/meeting-minutes/2025-01-22) 13 | - [January 8, 2025](/alesco/meeting-minutes/2025-01-08) 14 | - November 13, 2024 15 | - [October 2, 2024](/alesco/meeting-minutes/2024-10-02) 16 | - [September 4, 2024](/alesco/meeting-minutes/2024-09-04) 17 | - [August 21, 2024](/alesco/meeting-minutes/2024-08-21) 18 | - [July 24, 2024](/alesco/meeting-minutes/2024-07-24) 19 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2024-07-24.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2024-07-24) 2 | Minutes recorded by Cody Robertson. 3 | 4 | Edited by Cody Robertson and Jonathan Wright for publishing. 5 | 6 | ## Members 7 | ### Attendance 8 | - Jonathan Wright 9 | - Cody Robertson 10 | - Andrew Lukoshko 11 | - Elkhan Mammadli 12 | - Ben Thomas 13 | - Neal Gompa 14 | 15 | ## Community Attendees 16 | - Michel Lind 17 | 18 | ## Decisions Adopted 19 | 1. AlmaLinux 10's default x86_64 microarchitecture build will be v3, following RHEL. Approved building and maintaining x86_64_v2 as a separate architecture for AlmaLinux 10. 20 | - Unanimous decision. 21 | 2. AlmaLinux 10 will have frame pointers enabled, diverging from RHEL 10 which will not have frame pointers. 22 | - Unanimous decision 23 | 3. AlmaLinux will publish a rolling-style distro build, serving as a continuous beta release, starting with AlmaLinux 10. 24 | - Unanimous decision 25 | 26 | ## Minutes 27 | - ALESCo Logistics 28 | - Items: 29 | - Meeting times 30 | - Recording 31 | - Meeting chat (public?, live?) 32 | - Where to publish: minutes, recordings (GitHub repository, wiki, etc) 33 | - Issue tracker (GH repo?) 34 | - Policy/procedure documentation 35 | - Will be discussing further via chat channels 36 | - RHEL moving to x86_64 v3 microarchitecture in version 10 37 | - Some older hardware becomes unsupported 38 | - Improved performance 39 | - Community has voiced concerns with RHEL's decision on social media 40 | - CERN and other labs have voiced concerns 41 | - AlmaLinux will build a maintain a separate x86_64_v2 release. v3 will be the default. 42 | - Package naming is TBD. RHEL is using x86_64 for v3 which is incorrect, they should use x86_64_v3 43 | - Will have discussions with them at FLOCK about this 44 | - We'd like to follow RHEL's direction as our upstream, so we hope to talk with them about using the architecture tagging properly. 45 | - AlmaLinux v2 builds will use x86_64_v2 tags 46 | - Andrew & team working on patching various applications in the RPM stack to support this within AlmaLinux 47 | - Can potentially PR this work upstream to help convince RHEL to use the proper _v3 naming within RHEL 10 48 | - Enable frame pointers in AlmaLinux 10 builds 49 | - Most competing distros are enabling them now 50 | - Negligible performance impact 51 | - Loss of a register affects x86 32bit, legacy hardware take a noticeable hit 52 | - Allows continuous real-time profiling for "cheap" 53 | - Fedora enabled them several versions ago with no complaints after enablement 54 | - Especially useful in HPC 55 | - CentOS Hyperscale SIG considering enabling it by default 56 | - Do we offer non-frame pointer builds 57 | - Rolling release build for AlmaLinux 10 58 | - Serves as continous beta release 59 | - Will run full composes at least twice-yearly 60 | - Package updates will be a constant flow 61 | - Separate mirror source/repo on infra side 62 | - We're doing this already for AlmaLinux 10 development, just not currently publishing the resulting builds in a repoitory/as an OS 63 | - Not a replacement for point releases 64 | - We have to be mindful of security releases/patches from upstream 65 | - OpenQA to test all of the builds 66 | - Build in-line with point release (ex, frame pointers enabled) 67 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2024-08-21.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2024-08-21) 2 | Minutes recorded by Jonathan Wright. 3 | 4 | Edited by Jonathan Wright for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Jonathan Wright 9 | - Cody Robertson 10 | - Andrew Lukoshko 11 | - Elkhan Mammadli 12 | - Ben Thomas 13 | - Neal Gompa 14 | 15 | ### Board Attendees 16 | - benny Vasquez 17 | - Alex Iribarren 18 | 19 | ## Community Attendees 20 | 21 | ## Decisions Adopted 22 | 1. SPICE support to be added back to AlmaLinux 10 23 | - Removed in RHEL 9 24 | - Will revisit for enablement in AlmaLinux 9 at a later time 25 | - Unanimous decision 26 | 27 | ## Minutes 28 | - SPICE Support in AlmaLinux 29 | - Neal: Dropped in RHEL due to no RHEL stacks dependent on it. 30 | - Cody: https://bugzilla.redhat.com/show_bug.cgi?id=2030592 31 | - We can package server-side components in AlmaLinux 32 | - We can package client-side components in EPEL 33 | - benny: Concerned about further deviation from RHEL 34 | - Retracted after clarification of no modifcations to kernel, and only addition of packages 35 | - Neal: Virt stack in RHEL remains relatively close to upstream, so good for maintainability of these additions 36 | - Neal: Upstream libvirt maintainers are good to work with, can probably propose running their CI against AlmaLinux Kitten 10 37 | - Voted to enable/build necessary packages for AlmaLinux 10 unanimously 38 | - Tabled discussion of adding back to AlmaLinux 9 at a later time 39 | - benny: ALESCo Live Community Q&A 40 | - No ALESCo members against this 41 | - Will be moderated by benny 42 | - Potentially quarterly 43 | - benny will coordinate a time that works for ALESCo members, maybe Sept. 4 or Sept. 11 44 | - Great for transparency and community engagement 45 | - Disabled HW in RHEL10 46 | - Andrew: What should we re-enable 47 | - All: Mellanox definitely 48 | - Andrew: 10s of devices disabled in EL10 kernel 49 | - Jonathan: QLogic & other less-used devices? 50 | - Neal: Linux Plumbers will be useful to make connections to RHEL kernel maintainers 51 | - They are generally willing to merge things for RHEL-disabled components as long as they don't impact enabled-components. 52 | - We probably need a separate process for users to request hardware enablement of devices 53 | - Ben: Already has requests within UCL for re-adding support for QLogic cards 54 | - Alex (Board): Must be careful when enabling things that might appear easy to flip a flag now but will potentially later become more difficult to maintain. 55 | - Jonathan: We can agree on an initial list of things to re-enable that are very common and/or we have direct experience with and vote on the rest as demand arises throughout the AlmaLinux 10 life cycle. 56 | - Elkhan: Separate kernel for PPC with KVM enabled 57 | - Neal: Basically what centos hyperscale does with their kernel - RHEL-ish config (based on Fedora) + enablement on some thingfs 58 | - Neal: What if we just re-enable it in the main Alma kernel since it is a flag? 59 | - Jonathan: We can mark that feature specifically as experimental, even in the main Alma kernel 60 | - Andrew: Just changing the flag isn't enough, a few patches are required to get it to build 61 | - Elkhan: Use-case is openQA and image building 62 | - All: not aware of any use-cases or requests from users 63 | - Ben: Separate workflow for kernel-specific requests? 64 | - Neal: fits within the other already-discussed to-be-defined change request processes 65 | - Andrew: Secure-Boot Signing ELRepo or other 3rd party kernels 66 | - Building works, signing works, never got further feedback on if we want to do this or not 67 | - Are we going to collaborate with 3rd party if we were to do this? 68 | - Neal: Anything we sign should be AlmaLinux-hosted 69 | - All: agreed on this point 70 | - Neal: Have discussed with Jonathan about also maintaing the Hyperscale kernel for AlmaLinux 71 | - Jonathan: Situation is too fluid right now to make a decision on this at the moment. 72 | - Jonathan: Better if we have a SIG that wants to maintain something within AlmaLinux versus pulling from a 3rd party 73 | - Neal: Signing SIG kernels in general 74 | - We have to be able to trust the full tree and trace back all changes to the origin 75 | - Jonathan: Motion to revisit this at a later time 76 | - All: agreed 77 | - Jonathan: Revisit ALESCo meeting times 78 | - Have heard from interested community members they cannot attend the current time of 10AM EST 79 | - Was difficult to select current time, tough to fit into ALESCo members schedules given varying countries/schedules 80 | - Neal: Potential compromise is scheduling the community Q/A sessions at varying times to be more accessible 81 | - Cody: Can re-run a discussion among ALESCo members to try to find a new time 82 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2024-09-04.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2024-09-04) 2 | Minutes recorded by Jonathan Wright. 3 | 4 | Edited by Jonathan Wright for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Jonathan Wright 9 | - Cody Robertson 10 | - Andrew Lukoshko 11 | - Elkhan Mammadli 12 | - Ben Thomas 13 | - Neal Gompa 14 | 15 | ### Board Attendees 16 | - benny Vasquez 17 | 18 | ## Community Attendees 19 | - Lance Albertson 20 | 21 | ## Decisions Adopted 22 | - KVM will be supported on POWER in AlmaLinux 10. 23 | - Unanimous decision 24 | 25 | ## Minutes 26 | - Cody: Old business: tabled discussion about adding SPICE to EL9 from previous meeting 27 | - Andrew: too early to decide, built for 10 but haven't tested yet 28 | - Cody: will table indefinitely/for a month or two 29 | - Cody: will revisit times for meetings this week 30 | - Cody: alesco chair 31 | - Jonathan: nominates Cody 32 | - vote: unanimous 33 | 34 | - Lance: kvm on power on el9, currently maintaining own patches 35 | - Elkhan/Andrew: we're doing this sort of now internally, not published/maintained 36 | - Elkhan: have you noticed any issues? 37 | - Lance: haven't tested much yet, don't have el9 live on infra yet, seems fine so far 38 | - Jonathan: dropped from 10 as well? 39 | - Andrew: yes 40 | - Neal: maybe should skip 9 and aim for 10 41 | - Jonathan to lance: can you skip to 10? 42 | - Lance: dependent upon rdo, probably would have to keep patching manually 43 | - Neal: let's push as much as we can upstream to centos kernel 44 | - Lance: power 8 support in el10? It got dropped 45 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2024-10-02.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2024-10-02) 2 | Minutes recorded by Cody Robertson. 3 | 4 | Edited by Cody Robertson for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Andrew Lukoshko 9 | - Cody Robertson 10 | - Elkhan Mammadli 11 | - Jonathan Wright 12 | - Neal Gompa 13 | 14 | ### Unable to attend 15 | - Ben Thomas 16 | 17 | ### Board Attendees 18 | - Alex Iribarren 19 | - benny Vasquez 20 | 21 | ## Community Attendees 22 | - No community attendees 23 | 24 | ## Decisions Adopted 25 | - Rebuilding EPEL for x86_64_v2 26 | - The motion to rebuild EPEL for x86_64 v2 was tabled to gather more data and revisit after the release of AlmaLinux Kitten. 27 | 28 | ## Minutes 29 | 30 | ### Rebuilding EPEL for x86_64 v2 31 | - Cody: Introduced the topic of rebuilding EPEL for the x86_64 v2 architecture. Noted that previous votes focused on v3 and there was ambiguity regarding v2. 32 | - Andrew: Expressed concerns about the potential workload and maintenance challenges. 33 | - Highlighted the need to adjust macro systems and spec files. 34 | - Did not want to maintain changes or forks on our side. 35 | - Jonathan: Clarified that the build system can reasonably supports this 36 | - Andrew: Yes, not a problem 37 | - Neal: Pointed out that Fedora still builds for v1 and EPEL packages are Fedora backports, so issues might be minimal. 38 | - Neal: Emphasized the importance of EPEL for the usability of RHEL-based distributions. 39 | - Neal: Suggested that releasing without EPEL support might hinder adoption. 40 | - Alex: Agreed with Andrew’s concerns. 41 | - Neal: Can do this in stages, thinks we should approve it and see demand to make further decisions 42 | - Jonathan: Proposed tabling the decision to gather more data on user demand and revisit the topic after the release of AlmaLinux Kitten. 43 | - Neal: Warned that releasing AlmaLinux 10 without EPEL support for x86_64 v2 could impede adoption/usage 44 | - Suggested that if they decide not to build EPEL for v2, they should consider not releasing the v2 variant at all. 45 | - Decision: The team agreed to table the motion and reassess after AlmaLinux Kitten is released. 46 | 47 | ### GitHub Repository for Official Changes/RFCs 48 | 49 | - Cody: Presented a PoC for a GitHub repository to manage Requests for Comments (RFCs) and official changes [[1]](https://github.com/codyro/alesco-poc/) 50 | - Inspired by ArchLinux and Rust RFC processes. 51 | - Neal: Suggested replacing the “Alternatives” section with a “Feedback” section to capture community input. 52 | - Neal: Emphasized that submitting an RFC does not obligate the ALESCo committee to implement it; contributors should be responsible for the work. 53 | - Neal: Proposed adding sections about the benefit to AlmaLinux and feedback from the community/marketing perspective 54 | - Jonathan: Agreed with the proposed changes 55 | - Jonathan: Discussed the possibility of mentoring contributors who might need assistance. 56 | - Jonathan: Suggested directing contributors to the appropriate SIGs (Special Interest Groups). 57 | - Cody: Agreed to incorporate the feedback and adjust the RFC template accordingly and share the updated template for further input 58 | - Cody: Mentioned the need for an example template using a past decision. 59 | - Neal: Jonathan and him can draft up the x86_64_v2 one as an example 60 | - All: Decided to use the existing ALESCo repository for managing meeting agendas and issues instead of creating a new one. 61 | 62 | ### Alternating Meeting Schedule 63 | - Cody: Brought up the idea of alternating meeting times to accommodate participants in different time zones. 64 | - Cody: Found it unfeasible at this time due to scheduling conflicts and global distribution of team members. 65 | - Cody: Proposed to reassess the possibility in the future. 66 | - All: Agreed to put the idea on the back burner and revisit it in a few months if meetings gain more traction. 67 | 68 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2025-01-22.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2025-01-22) 2 | Minutes recorded by Jonathan Wright. 3 | 4 | Edited by Jonathan Wright for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Andrew Lukoshko 9 | - Elkhan Mammadli 10 | - Jonathan Wright 11 | - Neal Gompa 12 | - Ben Thomas 13 | 14 | ### Unable to attend 15 | - Cody Robertson 16 | 17 | ### Board Attendees 18 | 19 | ## Community Attendees 20 | - Luna Jernberg 21 | 22 | ## Decisions Adopted 23 | - N/A 24 | 25 | ## Minutes 26 | 27 | ### Rebuilding EPEL for x86_64 v2 28 | - Discussed pending draft RFC (https://hackmd.io/5__7wEQXS42L-ZdX9AFuPQ#) written by Jonathan and Neal. 29 | - Andrew: we should pull from directly from `src.fedoraproject.org` and not include any patches, ever. If a build fails, send patch upstream to EPEL. 30 | - Neal/Jonathan strongly agreed. 31 | - This ensures we do not accidentally fork EPEL. 32 | - Andrew to update implementation plan so the RFC can be officially submitted. 33 | - RFC submission expected this week. 34 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2025-04-02.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2025-04-02) 2 | Minutes recorded by Jonathan Wright. 3 | 4 | Edited by Jonathan Wright for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Andrew Lukoshko 9 | - Elkhan Mammadli 10 | - Jonathan Wright 11 | - Neal Gompa 12 | - Ben Thomas 13 | 14 | ### Unable to attend 15 | - Cody Robertson 16 | 17 | ### Board Attendees 18 | - benny Vasquez 19 | 20 | ## Community Attendees 21 | 22 | ## Decisions Adopted 23 | - Merged updated ALESCo Policy/Workflow for RFCs 24 | - https://github.com/AlmaLinux/ALESCo/pull/5 25 | 26 | ## Minutes 27 | 28 | ### RFC: Enable KVM on AlmaLinux 9 on ppc64le 29 | https://github.com/AlmaLinux/ALESCo/pull/3 30 | - Neal: what if we ship hyperscale kernel as an alternative kernel and turn it on there 31 | - Lance: That would work 32 | - Jonathan: That changes the RFC pretty significantly 33 | - Andrew: We can ship 2 AlmaLinux kernels, one with KVM/PPC enabled similar to something we do for ARM kernels already 34 | - Andrew/Neal: Userspace supports clean failure/fallback if kernel support is missing. 35 | - Neal: Default on PPC is PowerKVM anyway. 36 | - Jonathan: Hyperscale kernel is only supported 5 years 37 | - Neal: Hyperscale can look at supporting it for 10. 38 | - Jonathan: How many alt kernels is too many? 39 | - Jonathan to Lance: can you skip 9 and go to 10, where we're already shipping KVM/PPC support? 40 | - Lance: Don't know yet due to OpenStack. 41 | - Jonathan: We need Andrew's input since the workload of build and maintaining this will fall on his team. 42 | - Andrew: Will prepare POC of KVM/PPC on stock AlmaLinux kernel 43 | - Lance: Can test artifacts and provide feedback. 44 | - All: Will revisit after receiving Lance's feedback. 45 | 46 | ### RFC: Introduce x86_64-v1 compatibility for AlmaLinux 10 47 | https://github.com/AlmaLinux/ALESCo/pull/4 48 | - benny: Until the work can be justified we can't do anything with this yet. 49 | - Jonathan: Premature to vote right now, proposer needs more time to reply to comments. 50 | - Neal: Sympathetic to his argument biggest problem is virtualization stack which straight up will not work on v1. 51 | - Jonathan: Even Fedora will probably move on from v1 in the next several years - conversations about this are coming up more and more. That would put us in a worse position supporting v1. 52 | - Neal: We're constrained by the software we ship, of which a lot is skewing towards requiring v2 and higher. 53 | - Jonathan: Tabling for vote at next meeting. 54 | 55 | ### ALESCo Process Updates 56 | https://github.com/AlmaLinux/ALESCo/pull/5 57 | This was heavily discussed in person at our leadership summit in Brussels, Belgium in February of 2025. 58 | 59 | - Neal: Let's add a chunk to make PRs as draft so they don't get accidentally merged. 60 | - benny: Haven't seen anything accidentally merged. 61 | - Neal: I almost did one this morning. 62 | - Ben: Does this stop alerts? 63 | - benny: No, alerts still go out. 64 | - Neal: Draft PRs don't trigger actions and stops from merging until it's not a draft. That's the only implications of a draft. 65 | - benny: I'm fine with drafts. 66 | - Neal: Define GH action to convert it to a draft? 67 | - Ben: What about a branch rule? 68 | - Neal: Complex to make rules like that. 69 | - All: Good with it, pending Jonathan's more detailed review. 70 | - benny: Make GH account using board email, add as reviewer to new PRs. -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2025-04-16.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2025-04-16) 2 | Minutes recorded by Neal Gompa. 3 | 4 | Edited by Neal Gompa for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Neal Gompa 9 | - Ben Thomas 10 | - Elkhan Mammadli 11 | - Jonathan Wright 12 | 13 | ### Unable to attend 14 | - Andrew Lukoshko 15 | - Cody Robertson 16 | 17 | ### Board Attendees 18 | - N/A 19 | 20 | ## Community Attendees 21 | - Lance Albertson 22 | 23 | ## Decisions Adopted 24 | - The RFC to build an x86_64-v1 variant of AlmaLinux 10 was REJECTED 25 | 26 | ## Minutes 27 | 28 | ### RFC: Introduce x86_64-v1 compatibility for AlmaLinux 10 29 | - Discussed RFC (https://github.com/AlmaLinux/ALESCo/pull/4) written by Bohdan Khomutskyi. 30 | - Jonathan asked if attending ALESCo members have all reviewed it, everyone assented 31 | - RFC was put up to a vote 32 | - All attending ALESCo members voted to decline to implement the proposal 33 | 34 | ### RFC: Enable KVM on AlmaLinux 9 on ppc64le 35 | - Touched on RFC (https://github.com/AlmaLinux/ALESCo/pull/3) written by Lance Albertson. 36 | - Andrew provided a test `kernel-kvm` package for ppc64le for Lance to test before going on vacation 37 | - Lance has just started to test the package 38 | - ALESCo will defer discussion until the next meeting. 39 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2025-05-14.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2025-05-14) 2 | 3 | Minutes recorded by Cody Robertson. 4 | 5 | Edited by Cody Robertson for publishing. 6 | 7 | ## Members 8 | ### ALESCo Member Attendees 9 | - Andrew Lukoshko 10 | - Ben Thomas 11 | - Cody Robertson 12 | - Elkhan Mammadli 13 | - Jonathan Wright 14 | - Neal Gompa 15 | 16 | ### Unable to Attend 17 | - N/A 18 | 19 | ### Board Attendees 20 | - benny Vasquez (not present for full meeting) 21 | 22 | ### Community Attendees 23 | - Boris Burkov 24 | - Davide Cavalca 25 | - Koichiro Iwao 26 | - Lance Albertson 27 | - Luna Jernberg 28 | - Michel Lind 29 | 30 | ### Decisions Adopted 31 | - Enable KVM on PPC64LE for AlmaLinux 9 32 | - Ship NVIDIA open-source driver via AlmaLinux add-on repo (AlmaLinux 9 & AlmaLinux 10) 33 | - Offer btrfs as a Tech Preview (initially in "Kitten" branch) 34 | 35 | ## Minutes 36 | 37 | ### Enable KVM on PPC64LE (RFC [#0002](https://github.com/AlmaLinux/ALESCo/pull/3)) 38 | - PPC64LE KVM packages work; OpenStack Nova/PPC libvirt issues 39 | - Outcome: RFC accepted unanimously. 40 | 41 | ### NVIDIA Open-Source Driver (RFC [#0004](https://github.com/AlmaLinux/ALESCo/pull/8)) 42 | - Packaging complete; kernel-module signing almost finished. 43 | - negativo17 (https://negativo17.org/nvidia-driver/) repo will serve until official NVIDIA repo appears. Have discussed w/ them. 44 | - Outcome: RFC accepted unanimously. 45 | - Actions: 46 | - Neal to finish signing workflow. 47 | - Jonathan to coordinate with NVIDIA’s Simone about repo hand-off 48 | 49 | ### Enable CRB by Default in AlmaLinux 10 (RFC [#0006](https://github.com/AlmaLinux/ALESCo/pull/10)) 50 | - Motivation: SELinux-policy split will break EPEL without CRB. 51 | - Pros: smoother UX; already on in RHEL containers. 52 | - Cons: diverges from vanilla RHEL; minor metadata hit 53 | - Outcome: Vote postponed to next meeting. 54 | - Actions: 55 | - All members to seek concrete breakage scenarios. 56 | 57 | ### Btrfs Tech Preview (RFC [#0005](https://github.com/AlmaLinux/ALESCo/pull/9)) 58 | - CentOS Stream Hyperscale patches exist; installer already patched. 59 | - Concerns: long-term KABI drift, but Stream gives early warning. 60 | - Outcome: Approved for “Kitten” branch only; async vote later for 10 GA. 61 | - Actions: 62 | - Enable for Kitten, see how it goes to help determine if we consider it for 10 GA 63 | 64 | ### Use dynamic workspace indicator on GNOME (RFC [#0003](https://github.com/AlmaLinux/ALESCo/pull/6)) 65 | - Goal: keep workspace-dots indicator and add AlmaLinux logo to the left. 66 | - Needs a new patch; no vote yet. 67 | - Actions: 68 | - Elkhan & Neal (with help from Javi) to draft PoC/patch 69 | 70 | -------------------------------------------------------------------------------- /docs/alesco/meeting-minutes/2025-05-28.md: -------------------------------------------------------------------------------- 1 | # ALESCo Meeting Minutes (2025-05-28) 2 | Minutes recorded by Neal Gompa. 3 | 4 | Edited by Neal Gompa for publishing. 5 | 6 | ## Members 7 | ### ALESCo Member Attendees 8 | - Neal Gompa 9 | - Andrew Lukoshko 10 | - Ben Thomas 11 | - Jonathan Wright 12 | 13 | ### Unable to attend 14 | - Elkhan Mammadli 15 | - Cody Robertson 16 | 17 | ### Board Attendees 18 | - N/A 19 | 20 | ## Community Attendees 21 | - Davide Cavalca 22 | - Lance Albertson 23 | - Luna Jernberg 24 | 25 | ## Decisions Adopted 26 | - The RFC to enable CRB by default for AlmaLinux 10+ was APPROVED 27 | - The RFC to show the GNOME dynamic workspace indicator on GNOME was APPROVED 28 | 29 | ## Minutes 30 | 31 | ### RFC: Enable CRB by default for AlmaLinux 10+ 32 | - Discussed RFC (https://github.com/AlmaLinux/ALESCo/pull/10) written by Neal Gompa 33 | - Jonathan asked if everyone is ready to vote, everyone assented 34 | - RFC was put to a vote 35 | - Vote results: +4, 0, -1 (4 in favor, 0 abstained, 1 not in favor) 36 | - Cody voted +1 async for this in the GitHub discussion 37 | - Andrew voted -1 38 | - RFC approved 39 | 40 | ### RFC: Enable Btrfs as a tech preview 41 | - Discussed RFC (https://github.com/AlmaLinux/ALESCo/pull/9) written by Michel Lind 42 | - Jonathan asked if everyone is ready to vote 43 | - Andrew dissented and would like to see it land in Kitten first and then land in 10.1 44 | - Neal agrees with this, especially since AlmaLinux OS 10.0 is already released 45 | - Andrew wants to see how this affects the kernel with a proof of concept implementation first 46 | - Neal and Andrew will work to build this out 47 | - Vote punted until proof of concept is built 48 | 49 | ### RFC: Use dynamic workspace indicator on GNOME 50 | - Discussed RFC (https://github.com/AlmaLinux/ALESCo/pull/6) written by Elkhan Mammadli 51 | - Jonathan notes there have been lots of updates to improve this since last discussed 52 | - Jonathan asked if everyone is ready to vote, everyone assented 53 | - RFC was put to a vote 54 | - All attending ALESCo members voted to approve the proposal 55 | 56 | ### Open Floor 57 | 58 | #### Feedback on PowerKVM 59 | - Lance: QEMU machine types for PowerKVM are broken with libvirt/OpenStack 60 | - Andrew and Lance will work together to resolve issues 61 | -------------------------------------------------------------------------------- /docs/cloud/AWS.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'AWS' 3 | --- 4 | # AlmaLinux OS Amazon Web Services AMIs 5 | 6 | AlmaLinux OS offers Amazon Machine Images in a number of formats and regions for consumption on AWS. All AlmaLinux OS AMIs are completely free of charge regardless of the deployment channel. 7 | 8 | :::tip 9 | To learn more about AWS AMIs please see the [AWS EC2 Documentation on AMIs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html). There are currently 2 deployment channels available: [Marketplace](#aws-marketplace) and [Community](#community-amis). 10 | ::: 11 | 12 | ## Contributing 13 | You can find more information about how these, and other cloud images are built on our [Cloud Images GitHub Repository](https://github.com/AlmaLinux/cloud-images). Join our [Cloud SIG on Mattermost](https://chat.almalinux.org/almalinux/channels/sigcloud) to help out with the effort or for support. You can also discuss on our [Cloud SIG Forum](https://forums.almalinux.org/c/sigs/cloud-sig/10) and on our [AlmaLinux Community Reddit](https://www.reddit.com/r/AlmaLinux). 14 | 15 | ## AWS Marketplace 16 | The AWS Marketplace is a curated digital catalog used to find, deploy and manage software offerings. All AWS Marketplace products undergo thorough review and vetting by the AWS team to ensure security and quality. 17 | 18 | The AlmaLinux OS Foundation's [official AlmaLinux OS images](https://aws.amazon.com/marketplace/seller-profile?id=529d1014-352c-4bed-8b63-6120e4bd3342) are available via the AWS Marketplace at the links provided: 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 |
AlmaLinux OS 8x86_64arm64
AlmaLinux OS 9x86_64arm64
32 | 33 | ## Community AMIs 34 | 35 | Community AMIs are images that are shared directly by the AlmaLinux OS Foundation for others to utilize directly within their infrastructure. Below is a complete list of currently published AMIs and their corresponding IDs. For purposes of automation and integration into build tools and CI/CD pipelines, this list is also available as a [CSV](https://wiki.almalinux.org/ci-data/aws_amis.csv) file. 36 | 37 | ***Additional Regions Coming Soon*** 38 | 39 | 40 | -------------------------------------------------------------------------------- /docs/cloud/Azure.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Azure' 3 | --- 4 | # AlmaLinux OS in Azure Cloud 5 | 6 | AlmaLinux offers images for Azure across all Azure regions via the Azure Marketplace. Images are deployable via the marketplace, portal and CLI and for both Gen1 and Gen2 machines. The images are completely free of charge regardless of the deployment channel. 7 | 8 | The AlmaLinux team and community would like to thank Microsoft Azure for their sponsorship of AlmaLinux which helped make this, and other initiatives possible. 9 | 10 | ## Azure Community Gallery 11 | 12 | Azure Community Galleries allow anyone to publicly share virtual machine images. The AlmaLinux Foundation uploads images to the gallery `almalinux-56b45196-f8a2-4e53-858a-bc4d0ebca440`. Microsoft [provides examples](https://docs.microsoft.com/en-us/azure/virtual-machines/vm-generalized-image-version?#create-a-vm-from-a-community-gallery-image) of using community gallery images via `az` CLI, the portal, and REST. 13 | 14 | To use an image in a program, you will need to send an [ImageReference](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.management.compute.models.imagereference) like this one to the API: 15 | 16 | ```json 17 | "imageReference": { 18 | "communityGalleryImageId": "/CommunityGalleries/almalinux-56b45196-f8a2-4e53-858a-bc4d0ebca440/Images/almalinux-9-gen2/Versions/latest" 19 | } 20 | ``` 21 | 22 | ## Azure Marketplace 23 | The Azure Marketplace is a curated digital catalog used to find, deploy and manage software offerings. All Azure Marketplace products undergo thorough review and vetting by the Azure team to ensure security and quality. Additionally, the AlmaLinux image has gone through significant automated testing with Microsoft's test suite to ensure compatibility across a wide range of Azure compute resources. 24 | 25 | The official images can be found below: 26 | 27 | * [x86_64/AMD64](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-x86_64?tab=Overview) 28 | * [AArch64/ARM64](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-arm?tab=Overview) 29 | * [HPC](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-hpc?tab=Overview) 30 | 31 | The Azure Marketplace makes new images available more slowly than the Community Gallery. It also requires each subscription using AlmaLinux for the first time to accept a EULA before successfully creating any VM with the offering. 32 | 33 | ## Azure Portal 34 | When deploying a new Virtual Machine instance in the Azure portal, Select Image -> See All Images, and in the marketplace pop search for AlmaLinux. 35 | 36 | ## Azure CLI 37 | You can easily deploy images using the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/?view=azure-cli-latest). You can list all available images by running: 38 | ```shell 39 | az vm image list --all --publisher almalinux -o table 40 | ``` 41 | You can then deploy by running: 42 | 43 | ### AlmaLinux OS 8 x86_64 44 | ```shell 45 | az vm create -n MyVm -g MyResourceGroup --image almalinux:almalinux-x86_64:8-gen1:latest 46 | az vm create -n MyVm -g MyResourceGroup --image almalinux:almalinux-x86_64:8-gen2:latest 47 | ``` 48 | 49 | ### AlmaLinux OS 9 x86_64 50 | ```shell 51 | az vm create -n MyVm -g MyResourceGroup --image almalinux:almalinux-x86_64:9-gen1:latest 52 | az vm create -n MyVm -g MyResourceGroup --image almalinux:almalinux-x86_64:9-gen2:latest 53 | ``` 54 | 55 | ### AlmaLinux OS 8 AArch64 56 | ```shell 57 | az vm create -n MyVm -g MyResourceGroup --image almalinux:almalinux-arm:8-arm-gen2:latest 58 | ``` 59 | 60 | ### AlmaLinux OS 9 AArch64 61 | ```shell 62 | az vm create -n MyVm -g MyResourceGroup --image almalinux:almalinux-arm:9-arm-gen2:latest 63 | ``` 64 | 65 | For a full range of options that are customizable from the CLI please check the [Azure CLI Reference Docs](https://learn.microsoft.com/en-us/cli/azure/). 66 | -------------------------------------------------------------------------------- /docs/cloud/Google.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Google Cloud' 3 | --- 4 | 5 | # AlmaLinux OS Google Cloud Platform 6 | 7 | AlmaLinux OS Images for Google Cloud are available via the [Google Cloud Marketplace](https://console.cloud.google.com/marketplace/browse?filter=partner:AlmaLinux) as well as via the `gcloud` CLI. 8 | 9 | * [AlmaLinux OS 8](https://console.cloud.google.com/marketplace/product/almalinux-cloud/almalinux-8) 10 | * [AlmaLinux OS 9](https://console.cloud.google.com/marketplace/product/almalinux-cloud/almalinux-9) 11 | 12 | For `cloud` AlmaLinux OS images are available in the almalinux-cloud project. To list AlmaLinux images, use the following gcloud command: 13 | 14 | ```shell 15 | gcloud compute images list --project almalinux-cloud --no-standard-images 16 | ``` 17 | -------------------------------------------------------------------------------- /docs/cloud/OCI.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Oracle Cloud Infrastructure' 3 | --- 4 | # AlmaLinux OS in Oracle Cloud Infrastructure 5 | 6 | AlmaLinux offers images for Oracle Cloud Infrastructure across all OCI regions via the [Oracle Cloud Marketplace](https://cloudmarketplace.oracle.com/marketplace/en_US/homeLinkPage). Images are deployable for Regular, Shielded and ARM type instances via the Oracle Cloud Marketplace, Partner Image on Oracle Cloud Infrastructure Console and [OCI CLI](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/cliconcepts.htm). The images are completely free of charge regardless of the deployment channel. 7 | 8 | 9 | ## About Oracle Cloud Infrastructure 10 | Oracle Cloud Marketplace is an online store—a one-stop shop—selling hundreds of business apps and professional services that complement your existing Oracle Cloud implementation. 11 | All apps and services on the marketplace are offered by approved, registered, and expert partners and developers. Plus, Oracle has vetted, reviewed, and approved each product. 12 | 13 | ## Where to get the image and guidance steps 14 | 15 | The official AlmaLinux OS images are available on [Oracle Cloud Marketplace](https://cloudmarketplace.oracle.com/marketplace/en_US/partners/125035508) at the links provided: 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 |
AlmaLinux OS 8x86_64AArch64
AlmaLinux OS 9x86_64AArch64
30 | 31 | ### Oracle Cloud Infrastructure Console 32 | In the **Image and shape** section, choose the image and shape. For instance: in the Image section, click Change image. Then, select Partner images as an Image source from the list. 33 | 34 | ### OCI CLI 35 | You can easily deploy images using the [OCI CLI](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/cliconcepts.htm). You can list all available images and get the OCID of the image by running: 36 | ```shell 37 | oci compute image list $OCID 38 | ``` 39 | You can then deploy by running: 40 | ```shell 41 | oci compute instance launch --image-id 42 | ``` 43 | For a full range of options that are customizable from the CLI please check the [OCI CLI Reference Docs](https://docs.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/index.html). 44 | 45 | -------------------------------------------------------------------------------- /docs/cloud/README.md: -------------------------------------------------------------------------------- 1 | # Cloud Images 2 | 3 | At AlmaLinux, cloud integration is among our top priorities, ensuring that users get the most streamlined and efficient experience when deploying our OS in the cloud. Our dedication to this initiative is evident through the exceptional work of our [Cloud Special Interest Group (Cloud SIG)](/sigs/Cloud). They relentlessly work on perfecting and tailoring AlmaLinux for cloud environments, making our cloud images stand out for their performance, stability, and adaptability. 4 | 5 | :::tip 6 | If you are looking for AlmaLinux OS Kitten images, please, visit the [AlmaLinux OS Kitten page](/development/almalinux-os-kitten-10). 7 | ::: 8 | 9 | Presently, we are proud to offer robust support for a wide range of platforms including: 10 | | Cloud | AlmaLinux OS 8 | AlmaLinux OS 9 | 11 | | --- | --- | --- | 12 | | [AWS](AWS) | [Intel/AMD (x86_64)](https://aws.amazon.com/marketplace/pp/prodview-mku4y3g4sjrye)
[ARM64 (AArch64)](https://aws.amazon.com/marketplace/pp/prodview-zgsymdwitnxmm) | [Intel/AMD (x86_64)](https://aws.amazon.com/marketplace/pp/prodview-ykmb6re2rcouy)
[ARM64 (AArch64)](https://aws.amazon.com/marketplace/pp/prodview-pvttztrj2uzjk) | 13 | | [Azure](Azure) | [Intel/AMD (x86_64)](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-x86_64)
[ARM64 (AArch64)](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-arm)
[HPC Intel/AMD (x86_64)](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-hpc) | [Intel/AMD (x86_64)](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-x86_64)
[ARM64 (AArch64)](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-arm) | 14 | | [Generic Cloud (Cloud-init)](Generic-cloud)| [Intel/AMD (x86_64)](https://repo.almalinux.org/almalinux/8/cloud/x86_64/images/)
[ARM64 (AArch64)](https://repo.almalinux.org/almalinux/8/cloud/aarch64/images)
[IBM Z (s390x)](https://repo.almalinux.org/almalinux/8/cloud/s390x/images/)
[Power LE (ppc64le)](http://repo.almalinux.org/almalinux/8/cloud/ppc64le/images/) | [Intel/AMD (x86_64)](https://repo.almalinux.org/almalinux/9/cloud/x86_64/images/)
[ARM64 (AArch64)](https://repo.almalinux.org/almalinux/9/cloud/aarch64/images/)
[IBM Z (s390x)](https://repo.almalinux.org/almalinux/9/cloud/s390x/images/)
[Power LE (ppc64le)](https://repo.almalinux.org/almalinux/9/cloud/ppc64le/images/) | 15 | | [Google Cloud](Google) | [Intel/AMD (x86_64)](https://console.cloud.google.com/marketplace/product/almalinux-cloud/almalinux-8)| [Intel/AMD (x86_64)](https://console.cloud.google.com/marketplace/product/almalinux-cloud/almalinux-9) | 16 | | [OpenNebula](OpenNebula) | [Intel/AMD (x86_64)](https://repo.almalinux.org/almalinux/8/cloud/x86_64/images/)
[ARM64 (AArch64)](https://repo.almalinux.org/almalinux/8/cloud/aarch64/images) |[Intel/AMD (x86_64)](https://repo.almalinux.org/almalinux/9/cloud/x86_64/images/)
[ARM64 (AArch64)](https://repo.almalinux.org/almalinux/9/cloud/aarch64/images/)| 17 | | [Oracle Cloud Infrastructure](OCI) | [Intel/AMD (x86_64)](https://cloudmarketplace.oracle.com/marketplace/en_US/listing/125544666)
[ARM64 (AArch64)](https://cloudmarketplace.oracle.com/marketplace/en_US/listing/125567282) |[Intel/AMD (x86_64)](https://cloudmarketplace.oracle.com/marketplace/en_US/listing/127985411)
[ARM64 (AArch64)](https://cloudmarketplace.oracle.com/marketplace/en_US/listing/127985893) | 18 | 19 | Additionally, for those wishing to simulate cloud environments or test locally, we also provide options to run the [Cloud image on your local machine](Generic-cloud-on-local). Dive in and experience the pinnacle of cloud-based Linux distributions with AlmaLinux. 20 | 21 | ## Changelog 22 | 23 | You can find all the changes for every AlmaLinux Cloud Image starting versions 8.9 and 9.3 on the [changelog](cloud-changelog) page. 24 | 25 | ## Contribute and Get Help 26 | 27 | If you are interested in contributing or need any assistance, check the [SIG/Cloud](/sigs/Cloud) wiki page and join the *~SIG/Cloud* chat channel in [Mattermost](https://chat.almalinux.org/almalinux/channels/sigcloud) chat channel on [chat.almalinux.org](https://chat.almalinux.org). 28 | -------------------------------------------------------------------------------- /docs/community/coc.md: -------------------------------------------------------------------------------- 1 | --- 2 | Title: 'Code of Conduct' 3 | --- 4 | 5 | # AlmaLinux Community Code of Conduct (CoC) 6 | The AlmaLinux community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the distribution from coding through to marketing. Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to when they’re using project resources. 7 | 8 | This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to be excellent to each other. 9 | 10 | * Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. 11 | 12 | * Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the AlmaLinux community should be respectful when dealing with other contributors as well as with people outside the AlmaLinux community and with users of AlmaLinux. 13 | 14 | When we disagree, we try to understand why. Disagreements, both social and technical, happen all the time and AlmaLinux is no exception. It is important that we resolve disagreements and differing views constructively. 15 | 16 | Remember that we’re different. The strength of AlmaLinux comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere, rather offer to help resolving issues and to help learn from mistakes. 17 | 18 | ## Applicability 19 | Our Code of Conduct applies to all AlmaLinux community resources, including forums, IRC channels, mailing lists, etc. 20 | 21 | ## Attribution 22 | "Code of Conduct" by [Red Hat, Inc.](https://www.redhat.com/) is licensed under [CC-BY-SA 3.0](https://creativecommons.org/licenses/by-sa/3.0/legalcode). Used with modifications. -------------------------------------------------------------------------------- /docs/community/platforms.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Community Platforms' 3 | --- 4 | 5 | # AlmaLinux IRC Channels 6 | 7 | AlmaLinux maintains a presence on the [freenode IRC network](https://freenode.net/). 8 | 9 | Please observe the AlmaLinux [Code of Conduct](coc.md) and respect your fellow users at all times. 10 | 11 | ## Official Channels 12 | 13 | | Channel | Purpose | 14 | |-|-| 15 | | #almalinux | General discussion and community-based user support | 16 | | #almalinux-arm | (SIG) ARM-specific discussion and support 17 | | #almalinux-cloud | (SIG) Cloud-centric discussion (AWS, GCP, Azure, OpenStack, etc.) | 18 | | #almalinux-devel | Developing for AlmaLinux (or a similar EL platform)? This is for you. | 19 | | #almalinux-infra | Discussion or issue reporting for AlmaLinux project infrastructure | 20 | | #almalinux-security | Security-specific discussion and support | 21 | | #almalinux-social | Off-topic banter | 22 | | #almalinux-storage | (SIG) Storage-specific discussion (GlusterFS, etc.) 23 | 24 | # Mattermost 25 | 26 | AlmaLinux operates a Mattermost instance at https://chat.almalinux.org. 27 | 28 | This instance is open to the public; contributors are highly encouraged to sign up! -------------------------------------------------------------------------------- /docs/containers/README.md: -------------------------------------------------------------------------------- 1 | # Containers on AlmaLinux 2 | 3 | In the evolving world of development and deployment, containers have become essential tools, bringing consistency, scalability, and efficiency to the forefront. At AlmaLinux, we've embraced this trend, with our Cloud Special Interest Group (Cloud SIG) playing a pivotal role in aligning our offerings with the needs of the community. 4 | 5 | **Docker Images**: Our Docker images are optimized for a seamless deployment experience, mirroring the reliability and performance that AlmaLinux is known for. Ideal for developers who want the stability of AlmaLinux within the Docker environment. 6 | 7 | **OCI Images**: The Open Container Initiative (OCI) lays down the standards for modern container technologies. AlmaLinux's OCI images uphold these standards, ensuring compatibility and smooth operation with various container tools and orchestration platforms. 8 | 9 | :::tip 10 | If you are looking for AlmaLinux OS Kitten 10 images, please, visit the [AlmaLinux OS Kitten 10](/development/almalinux-os-kitten-10) page. 11 | ::: 12 | 13 | Dive into the future of application deployment with AlmaLinux's tailored container solutions. 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /docs/development/AWS_AMIS_kitten_10.md: -------------------------------------------------------------------------------- 1 | Distribution|Version|Region|AMI ID|Arch 2 | -|-|-|-|- 3 | AlmaLinux OS Kitten |10.20241224.0 |af-south-1 |ami-003a025a7b759591f |x86_64 4 | AlmaLinux OS Kitten |10.20241225.0 |af-south-1 |ami-089536ad9cfa2762b |aarch64 5 | AlmaLinux OS Kitten |10.20241224.0 |ap-east-1 |ami-0e84ede0c1b1e74d2 |x86_64 6 | AlmaLinux OS Kitten |10.20241225.0 |ap-east-1 |ami-0b939d067185f41f0 |aarch64 7 | AlmaLinux OS Kitten |10.20241224.0 |ap-northeast-1 |ami-0738091b1d7871c73 |x86_64 8 | AlmaLinux OS Kitten |10.20241225.0 |ap-northeast-1 |ami-0f66b5b1f80f092f2 |aarch64 9 | AlmaLinux OS Kitten |10.20241224.0 |ap-northeast-2 |ami-03380ebc953c38d98 |x86_64 10 | AlmaLinux OS Kitten |10.20241225.0 |ap-northeast-2 |ami-065eb5560d6e283e2 |aarch64 11 | AlmaLinux OS Kitten |10.20241224.0 |ap-northeast-3 |ami-0cf2e7964872a3a67 |x86_64 12 | AlmaLinux OS Kitten |10.20241225.0 |ap-northeast-3 |ami-081a4f93f4f8fa004 |aarch64 13 | AlmaLinux OS Kitten |10.20241224.0 |ap-south-1 |ami-0ab2253ec171baac1 |x86_64 14 | AlmaLinux OS Kitten |10.20241225.0 |ap-south-1 |ami-00b12d74d68dc00f5 |aarch64 15 | AlmaLinux OS Kitten |10.20241224.0 |ap-south-2 |ami-00641f75248a08352 |x86_64 16 | AlmaLinux OS Kitten |10.20241225.0 |ap-south-2 |ami-0ffb87d239d7dc340 |aarch64 17 | AlmaLinux OS Kitten |10.20241224.0 |ap-southeast-1 |ami-04bbd153560f8fd86 |x86_64 18 | AlmaLinux OS Kitten |10.20241225.0 |ap-southeast-1 |ami-0d409e6caa503a61f |aarch64 19 | AlmaLinux OS Kitten |10.20241224.0 |ap-southeast-2 |ami-0ea66d346ec913568 |x86_64 20 | AlmaLinux OS Kitten |10.20241225.0 |ap-southeast-2 |ami-0f8cf346225214c94 |aarch64 21 | AlmaLinux OS Kitten |10.20241224.0 |ap-southeast-3 |ami-0b4968c6132843d8a |x86_64 22 | AlmaLinux OS Kitten |10.20241225.0 |ap-southeast-3 |ami-06a47a5852c4af3e5 |aarch64 23 | AlmaLinux OS Kitten |10.20241224.0 |ap-southeast-4 |ami-0f777298d3966b133 |x86_64 24 | AlmaLinux OS Kitten |10.20241225.0 |ap-southeast-4 |ami-0bb909dbb3ba9f4d1 |aarch64 25 | AlmaLinux OS Kitten |10.20241224.0 |ap-southeast-5 |ami-0d072216791288e41 |x86_64 26 | AlmaLinux OS Kitten |10.20241225.0 |ap-southeast-5 |ami-0c3ecd395fbca6d04 |aarch64 27 | AlmaLinux OS Kitten |10.20241224.0 |ca-central-1 |ami-0aff3a555d8a3617f |x86_64 28 | AlmaLinux OS Kitten |10.20241225.0 |ca-central-1 |ami-07a9d8cf652b4f10a |aarch64 29 | AlmaLinux OS Kitten |10.20241224.0 |ca-west-1 |ami-0f677373f33018843 |x86_64 30 | AlmaLinux OS Kitten |10.20241225.0 |ca-west-1 |ami-07f027e6e5413f174 |aarch64 31 | AlmaLinux OS Kitten |10.20241224.0 |eu-central-1 |ami-0a0bbf4c848af2af1 |x86_64 32 | AlmaLinux OS Kitten |10.20241225.0 |eu-central-1 |ami-0f693a683dbf1fd95 |aarch64 33 | AlmaLinux OS Kitten |10.20241224.0 |eu-central-2 |ami-067ea5dc64cd842e8 |x86_64 34 | AlmaLinux OS Kitten |10.20241225.0 |eu-central-2 |ami-061acc19719b8de9d |aarch64 35 | AlmaLinux OS Kitten |10.20241224.0 |eu-north-1 |ami-02d5195aaa645b2d9 |x86_64 36 | AlmaLinux OS Kitten |10.20241225.0 |eu-north-1 |ami-0ce0022d29435f7e9 |aarch64 37 | AlmaLinux OS Kitten |10.20241224.0 |eu-south-1 |ami-06972e3fe5a2a3c06 |x86_64 38 | AlmaLinux OS Kitten |10.20241225.0 |eu-south-1 |ami-0056c2304a516ba2c |aarch64 39 | AlmaLinux OS Kitten |10.20241224.0 |eu-south-2 |ami-0d43dc74e2b37823b |x86_64 40 | AlmaLinux OS Kitten |10.20241225.0 |eu-south-2 |ami-0fe51d7b3799f8dec |aarch64 41 | AlmaLinux OS Kitten |10.20241224.0 |eu-west-1 |ami-0a51dfd9da2585fa9 |x86_64 42 | AlmaLinux OS Kitten |10.20241225.0 |eu-west-1 |ami-0cfe6d89937612e41 |aarch64 43 | AlmaLinux OS Kitten |10.20241224.0 |eu-west-2 |ami-057a53259cd38c906 |x86_64 44 | AlmaLinux OS Kitten |10.20241225.0 |eu-west-2 |ami-0dba1f2228979b999 |aarch64 45 | AlmaLinux OS Kitten |10.20241224.0 |eu-west-3 |ami-0aa77731591467751 |x86_64 46 | AlmaLinux OS Kitten |10.20241225.0 |eu-west-3 |ami-08a0055efacbfb16d |aarch64 47 | AlmaLinux OS Kitten |10.20241224.0 |il-central-1 |ami-00f26edc250adae88 |x86_64 48 | AlmaLinux OS Kitten |10.20241225.0 |il-central-1 |ami-0901ccb68a3cf54dd |aarch64 49 | AlmaLinux OS Kitten |10.20241224.0 |me-central-1 |ami-0e8c9587f56a85764 |x86_64 50 | AlmaLinux OS Kitten |10.20241225.0 |me-central-1 |ami-09292d27c9646fd98 |aarch64 51 | AlmaLinux OS Kitten |10.20241224.0 |me-south-1 |ami-0a47275eb70b949ab |x86_64 52 | AlmaLinux OS Kitten |10.20241225.0 |me-south-1 |ami-09f6dd7d23e1efe3b |aarch64 53 | AlmaLinux OS Kitten |10.20241224.0 |sa-east-1 |ami-0fc36909859e24d67 |x86_64 54 | AlmaLinux OS Kitten |10.20241225.0 |sa-east-1 |ami-056f7c4b1f8b6508c |aarch64 55 | AlmaLinux OS Kitten |10.20241224.0 |us-east-1 |ami-0bcea1e66829fec5b |x86_64 56 | AlmaLinux OS Kitten |10.20241225.0 |us-east-1 |ami-0707e89f669cb9128 |aarch64 57 | AlmaLinux OS Kitten |10.20241224.0 |us-east-2 |ami-09006d9b022cf83bf |x86_64 58 | AlmaLinux OS Kitten |10.20241225.0 |us-east-2 |ami-0cf26cfee77587998 |aarch64 59 | AlmaLinux OS Kitten |10.20241224.0 |us-west-1 |ami-0dd6bcb992f81e9dd |x86_64 60 | AlmaLinux OS Kitten |10.20241225.0 |us-west-1 |ami-00acb53be0d9b83f8 |aarch64 61 | AlmaLinux OS Kitten |10.20241224.0 |us-west-2 |ami-02b15cbc99b36723b |x86_64 62 | AlmaLinux OS Kitten |10.20241225.0 |us-west-2 |ami-0ececb1dbad990839 |aarch64 63 | -------------------------------------------------------------------------------- /docs/development/AlmaLinux-Build-System.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'AlmaLinux Build System' 3 | --- 4 | 5 | ###### last updated: 2024-10-28 6 | 7 | # AlmaLinux Build System 8 | 9 | ## About AlmaLinux Build System 10 | 11 | [AlmaLinux Build System](https://build.almalinux.org/) is designed to handle processes of: 12 | * Building rpm packages for multiple supported architectures and distribution versions. 13 | * Testing packages. 14 | * Signing packages. See more on the [Signing packages](/development/private-keys/package-signing) page. 15 | * Releasing packages. 16 | * Ensuring that packages and their sources are reliably using [SBOM](/documentation/sbom-guide). 17 | * Providing [Errata](/documentation/errata). 18 | 19 | ## AlmaLinux OS source packages 20 | 21 | AlmaLinux OS source code including [modified packages](/development/Modified-packages) is stored and managed in Git repositories on [git.almalinux.org](https://git.almalinux.org/explore/repos). 22 | 23 | AlmaLinux OS Team and community work on these repositories to submit changes, fix bugs, and introduce new features. The AlmaLinux Build System is then used to pull the latest changes from these repositories and build the updated packages. 24 | 25 | ## AlmaLinux Build System Structure 26 | 27 | 28 | 29 | * The Build System [Master Service](https://github.com/AlmaLinux/albs-web-server) provides an API that UI and CLI tools use to build, test, sign and release the packages. 30 | * The sources to build the AlmaLinux OS packages are taken from the AlmaLinux [git server](https://git.almalinux.org/), which are either synchronized directly from the CentOS git server, or updated manually by the AlmaLinux packagers. All the package sources that are used to build AlmaLinux OS packages are notarized commit by commit, and this information is stored in our [immudb](/documentation/sbom-guide) instance. 31 | * The [Build Node](https://github.com/AlmaLinux/albs-node) continuously asks the Master Service for new tasks to build packages from the provided git references. The built packages will be marked as verified only if the git references used to build the packages have been notarized. Built packages and build logs (or artifacts) are stored in the Artifact Storage (PULP), which only keeps notarized artifacts, this is, trusted and verified artifacts. 32 | * [Test System](https://github.com/AlmaLinux/alts) receives Test Tasks to test built packages from Artifact Storage. The Test System tests packages via Test Nodes (eg. Docker or OpenNebula with different architectures) and store test artifacts (test logs) in Artifact Storage. 33 | * [Sign Server](https://github.com/AlmaLinux/albs-sign-node) receives sign tasks to sign packages with the corresponding PGP key. The Sign Server retrieves the unsigned packages, verifies that the packages are notarized, and signs them. Signed packages are then notarized again, storing this information in immudb and then saving the signed packages in the Artifact Storage. 34 | * Release System receives release tasks to upload signed packages to public repositories. 35 | * Each step involved in the build process is notarized and stored in immudb using a unique hash (immudb hash). This process ensures that traceability is guaranteed and that the information generated throughout the build process and stored in immudb can be used later on to generate SBOM documents. 36 | 37 | ## More guides and details 38 | 39 | If you are interested in learning how to build AlmaLinux OS packages, please check the [Packaging guidelines](/development/Packaging) and [Building packages guide](/documentation/building-packages-guide). 40 | 41 | Details and guides on how the AlmaLinux Build System works and how to use it can be found in the [AlmaLinux Build System Wiki](https://github.com/AlmaLinux/build-system/wiki). 42 | 43 | ## Reporting Issues 44 | 45 | All issues should be reported to the [Build System](https://github.com/AlmaLinux/build-system/issues) repository. A [kanban board](https://github.com/orgs/AlmaLinux/projects/2) is used for the Build System project to track the progress. 46 | 47 | ## Contribute and Get Help 48 | 49 | AlmaLinux Build System is open for community contributions. You can contribute to the codebase, submit patches, and use community product repositories to build and release packages. You can find more on the [Build System SIG](/sigs/Build-System) page. 50 | 51 | Join the ~SIG/Build System [chat channel](https://chat.almalinux.org/almalinux/channels/build-system) for any talk and assistance. 52 | -------------------------------------------------------------------------------- /docs/development/Packaging.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Packaging' 3 | --- 4 | # AlmaLinux packaging guideline 5 | 6 | 7 | ## Upstream packages modification 8 | 9 | Here is a (mostly complete) list of reasons to modify an upstream package: 10 | 11 | * debranding. 12 | * removing upstream-specific dependencies (e.g. subscription-manager). 13 | * fixing upstream bugs if necessary. 14 | 15 | 16 | We have a convention to add the `.alma` postfix to the end of the modified 17 | packages "Release" field. For example, an upstream `sos-3.9.1-6.el8` package 18 | will become `sos-3.9.1-6.el8.alma` after debranding. This will help us 19 | distinguish our packages from upstream ones, especially if a machine was 20 | converted to AlmaLinux. 21 | 22 | All modified package sources should be uploaded to a corresponding repository 23 | in the AlmaLinux Git [git.almalinux.org](https://git.almalinux.org/explore/repos) into branches for modified sources - `a8` and `a9`. 24 | -------------------------------------------------------------------------------- /docs/documentation/epel-and-rpmfusion.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Installing EPEL and RPM Fusion" 3 | --- 4 | 5 | # Installing EPEL and RPM Fusion 6 | 7 | This guide describes how to install _Extra Packages for Enterprise Linux (EPEL)_ and _RPM Fusion_, two software repositories that contain software that is not included by AlmaLinux (like codecs). 8 | 9 | :::warning 10 | These third-party software repositories may not be supported by AlmaLinux's [ELevate Project](/elevate/). 11 | ::: 12 | 13 | ## Step 1: Install EPEL. 14 | Installing EPEL is required for RPM Fusion. 15 | 1. Follow the instructions [described here](/repos/Extras) to install EPEL. 16 | 17 | 18 | ## Step 2: Install (and verify) the RPM Fusion GPG keys 19 | Downloading and verifying the RPM Fusion GPG keys ensures that the packages you install are from RPM Fusion and not altered (by accident or by malicious intent). 20 | 1. Download the _distribution-gpg-keys_ package. 21 | ```bash 22 | $ sudo dnf install distribution-gpg-keys 23 | ``` 24 | - If you get a prompt to import a GPG key, compare the key you recived to [Fedora's package signing keys](https://fedoraproject.org/security/). Make sure the key on the webpage is the correct EPEL version as the one described on the userid, and make sure the fingerprints match. 25 | 2. Import the RPM Fusion keys with `rpmkeys` 26 | ```bash 27 | # RPM Fusion (free packages) 28 | $ sudo rpmkeys --import /usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-free-el-$(rpm -E %rhel) 29 | # RPM Fusion (nonfree packages) 30 | $ sudo rpmkeys --import /usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-nonfree-el-$(rpm -E %rhel) 31 | ``` 32 | 3. (Optional) Check that the GPG keys match the one on the [RPM Fusion keys page](https://rpmfusion.org/keys). (It is in the section labeled "Currently Used Keys".) Use the commands below to show the keys that were imported and compare them to the one in RPM Fusion. 33 | ```bash 34 | # RPM Fusion (free packages) 35 | $ gpg --show-keys --with-fingerprint /usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-free-el-$(rpm -E %rhel) 36 | # RPM Fusion (nonfree packages) 37 | $ gpg --show-keys --with-fingerprint /usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-nonfree-el-$(rpm -E %rhel) 38 | ``` 39 | 40 | ## Step 3: Install RPM Fusion 41 | Enter the command below. 42 | ```bash 43 | $ sudo dnf --setopt=localpkg_gpgcheck=1 install https://mirrors.rpmfusion.org/free/el/rpmfusion-free-release-$(rpm -E %rhel).noarch.rpm https://mirrors.rpmfusion.org/nonfree/el/rpmfusion-nonfree-release-$(rpm -E %rhel).noarch.rpm 44 | ``` 45 | If the installation fails, this may mean that the GPG keys imported earlier do not match the signiture of the RPM Fusion repositories. If this occurs, retry step 2.3 to see if you have the correct GPG keys. 46 | -------------------------------------------------------------------------------- /docs/documentation/errata.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Security Errata" 3 | --- 4 | 5 | # AlmaLinux Errata 6 | 7 | ### About Errata 8 | 9 | Errata are package updates like some enhancements and features, bug fixes and security patches. These updates can be found at [errata.almalinux.org](https://errata.almalinux.org/) as a list of errata advisories. 10 | 11 | ![image](/images/errata_feed.png) 12 | 13 | Advisories are published text to help users get the information that errata provide and their impact. 14 | There are three types of advisories: 15 | 16 | * ALSA - AlmaLinux Security Advisory - considered the most important type as it contains security fixes 17 | * ALBA - AlmaLinux Bug Advisory - contains bug fixes 18 | * ALEA - AlmaLinux Enhancement Advisory - contains enhancements and new features 19 | 20 | These advisories are ranked by severity: Critical, Important, Moderate and Low. 21 | 22 | Besides type and severity details, each advisory includes some description, references, a list of updated packages and the release date. 23 | 24 | ![image](/images/errata_example.png) 25 | 26 | 27 | ### How to access errata 28 | 29 | * You can find updateinfo.xml files in repos and mirrors. Or run the following command to see the list of advisories as an output: 30 | 31 | ``` 32 | dnf updateinfo --list 33 | ``` 34 | 35 | * Recommended to use *.json* files with updated schema: 36 | * [errata.full.json](https://errata.almalinux.org/8/errata.full.json) for AlmaLinux 8 37 | * [errata.full.json](https://errata.almalinux.org/9/errata.full.json) for AlmaLinux 9 38 | * *.json* files with deprecated schema: 39 | * [errata.json](https://errata.almalinux.org/8/errata.json) for AlmaLinux 8 40 | * [errata.json](https://errata.almalinux.org/9/errata.json) for AlmaLinux 9 41 | * details about OVAL files can be found at [OVAL streams](https://wiki.almalinux.org/documentation/oval-streams.html) AlmaLinux Wiki page 42 | 43 | ### Mailing list 44 | 45 | You can subscribe to the AlmaLinux errata [mailing list](https://lists.almalinux.org/mailman3/lists/security.lists.almalinux.org/) to receive notifications about errata package releases. 46 | -------------------------------------------------------------------------------- /docs/documentation/guides.md: -------------------------------------------------------------------------------- 1 | # Documentation | Security Guides 2 | 3 | In this section of the wiki, we emphasize AlmaLinux OS security through: 4 | 5 | - **OpenSCAP**: Comprehensive guides on evaluating system security configurations. 6 | - **OVAL**: Standardized definitions for AlmaLinux to consistently assess vulnerabilities. 7 | - **SBOM**: Resources on tracking software components for transparency. 8 | - **Security Errata**: Regular updates on the latest security patches and updates. 9 | 10 | # About Our Security Mindset 11 | 12 | For AlmaLinux OS Project ensuring its security is paramount for several reasons: 13 | 14 | - **Trust:** Users and organizations need to trust that the OS isn't compromised, ensuring the safety of their data and applications. 15 | - **Stability**: Security vulnerabilities can lead to system instability. A secure OS is generally a more stable OS. 16 | - **Data Integrity**: Protecting the OS from unauthorized access ensures the integrity of the data it holds. 17 | - **Threat Landscape**: Linux-based systems, due to their widespread use especially in server environments, are continuous targets for attackers. Keeping them secure is an ongoing necessity. 18 | - **Reputation**: AlmaLinux aims to be a reliable RHEL fork. Maintaining a strong security posture is essential for its reputation and adoption. 19 | - **Compliance**: Many organizations are subject to regulatory standards that mandate specific security controls and measures. A secure OS helps these organizations achieve and maintain compliance. 20 | 21 | -------------------------------------------------------------------------------- /docs/documentation/kickstart-guide.md: -------------------------------------------------------------------------------- 1 | ## Kickstart Installation (Unattended Installation) 2 | 3 | Kickstart is used to perform unattended installation with predefined set of parameters 4 | 5 | There are multiple ways of starting a kickstart installation, for details check out [pykickstart docs](https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-12-starting-a-kickstart-installation) 6 | 7 | ### Customization 8 | Best way to start is to perform an installation in a virtual machine then take `/root/anaconda-ks.cfg` as the base and modify it, it contains selected options during the installation 9 | 10 | All commands that can be used in kickstart are listed [here](https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-3-kickstart-commands-in-red-hat-enterprise-linux) 11 | 12 | You can host the kickstart files using preinstalled python http server `python -m http.server` and then add `inst.ks=http://:/kickstart.cfg` to grub during boot 13 | 14 | ### Examples 15 | #### KDE Desktop 16 | Example using KDE Desktop with preinstalled CRB and EPEL repositories preinstalled 17 | 18 | ``` 19 | # use graphical installer 20 | graphical 21 | 22 | # add base repositories with mirrors 23 | repo --name="alamalinux9-baseos" --mirrorlist="https://mirrors.almalinux.org/mirrorlist/9/baseos" 24 | repo --name="alamalinux9-appstream" --mirrorlist="https://mirrors.almalinux.org/mirrorlist/9/appstream" 25 | 26 | # add epel repo with mirrors 27 | repo --name="epel9-everything" --mirrorlist="https://mirrors.fedoraproject.org/mirrorlist?repo=epel-9&arch=x86_64" 28 | 29 | # add CRB with mirrors 30 | repo --name="CRB" --mirrorlist="https://mirrors.almalinux.org/mirrorlist/9/crb/" 31 | 32 | # use internet install 33 | url --url="https://repo.almalinux.org/almalinux/9/BaseOS/x86_64/kickstart/" 34 | 35 | # set hostname (link is the first device that is up) 36 | network --device=link --bootproto=dhcp --hostname="localhost" 37 | 38 | # set locale and keyboard layout 39 | keyboard --xlayouts='us' 40 | lang en_US.UTF-8 41 | 42 | # packages or groups to install 43 | %packages 44 | # exclude select applications 45 | -kamera 46 | -akregator 47 | -kate 48 | 49 | # repos used in kickstart arent saved afterwards 50 | epel-release 51 | 52 | # install kde desktop environmental group 53 | @^kde-desktop-environment 54 | 55 | # install virtual machine guest additions group 56 | @guest-agents 57 | %end 58 | 59 | # enable first boot agent 60 | firstboot --enable 61 | 62 | # set timezone and use UTC 63 | timezone America/New_York --utc 64 | 65 | # disable root account 66 | rootpw --lock 67 | 68 | # create user with multiple groups and password in plaintext 69 | user --groups="wheel,input" --name user --password="temp" 70 | 71 | # repo command adds a repository only to the installer so add CRB to installed system too 72 | %post 73 | #!/bin/sh 74 | dnf config-manager --set-enabled crb 75 | %end 76 | ``` 77 | -------------------------------------------------------------------------------- /docs/documentation/oval-streams.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "AlmaLinux OS OVAL streams" 3 | --- 4 | 5 | # AlmaLinux OS OVAL streams 6 | 7 | The supported AlmaLinux OS versions and their public OVAL streams are listed below: 8 | 9 | ## AlmaLinux OS 8 10 | 11 | 12 | 13 | 14 | ## AlmaLinux OS 9 15 | 16 | 17 | 18 | 19 | --- 20 | Join the [Community Chat](https://chat.almalinux.org/) if you want to help and contribute or get any assistance. 21 | 22 | -------------------------------------------------------------------------------- /docs/elevate/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "About ELevate project" 3 | --- 4 | 5 | ###### last updated: 2025-04-03 6 | 7 | # About the project 8 | 9 | The ELevate project is an initiative to support upgrades between major versions of RHEL-derivatives. 10 | 11 | The [Leapp utility](https://leapp.readthedocs.io) and a few [patches](https://github.com/AlmaLinux/leapp-repository/commits/almalinux) are used to perform in-place upgrades from CentOS 7 and Enterprise Linux (EL) 8, and between EL8 and EL9 systems. 12 | 13 | The [Red Hat Upgrade Tool](https://github.com/upgrades-migrations/redhat-upgrade-tool.git) is used to perform in-place upgrades between CentOS 6 and CentOS 7. 14 | 15 | ## Available migration paths 16 | 17 | :::tip 18 | Please note, the ELevate project is designed to perform one-step upgrades. If you wish to perform an upgrade from CentOS7, you need to split the process. Please check the [ELevating CentOS7 to AlmaLinux 9](/elevate/ELevating-CentOS7-to-AlmaLinux-9.md) guide for more information. 19 | ::: 20 | 21 | The ELevate project supports a number of 3rd party repositories: 22 | * EPEL support is currently available for upgrades to AlmaLinux OS only. 23 | * Docker CE - for all supported operating systems. 24 | * MariaDB - for all supported operating systems. 25 | * Microsoft Linux Package Repositories - for all supported operating systems. 26 | * nginx - for all supported operating systems. 27 | * PostgreSQL - for all supported operating systems. 28 | * Imunify - for upgrades to EL 8. 29 | * KernelCare - for all supported operating systems. 30 | :::tip 31 | You can contribute to the project and add more 3rd party repositories support. See more on the [Contribute](/elevate/Contribution-guide) page. 32 | ::: 33 | 34 | Currently, the following upgrade paths are available: 35 | 36 | ![image](/images/ELevate.svg) 37 | 38 | \* - upgrading from Scientific Linux 7 to AlmaLinux 8 requires a workaround. Please, see more in the [known issues](/elevate/ELevate-frequent-issues).
39 | \** - upgrading to Oracle Linux 9 is available with the [Oracle Leapp utility](https://blogs.oracle.com/linux/post/upgrade-oracle-linux-8-to-oracle-linux-9-using-leapp) and will not be supported by ELevate project.
40 | \*** - upgrades to AlmaLinux OS 10 (beta) and CentOS 10 are available as ELevate Testing. Upgrade to AlmaLinux OS Kitten 10 is available as ELevate NG. 41 | 42 | ## How to upgrade 43 | 44 | Various guides cover the update steps depending on the upgrade type: 45 | * The [ELevate Quickstart Guide](/elevate/ELevate-quickstart-guide) covers the upgrade steps using the Leapp utility version with 3rd party repositories support and provides the Demo video. 46 | * The [ELevate CentOS 7 to AlmaLinux 9 Guide](/elevate/ELevating-CentOS7-to-AlmaLinux-9) covers a two-stage process to upgrade a CentOS 7 machine to AlmaLinux OS 9. 47 | * The [ELevate CentOS 6 to CentOS 7 Guide](/elevate/ELevating-CentOS6-to-CentOS7) covers steps to be performed to upgrade CentOS 6 machines to CentOS 7. 48 | * The [ELevate Offline Guide](/elevate/ELevate-offline-guide) covers the upgrade steps on air-gapped machines. 49 | 50 | ## How to Contribute 51 | 52 | ELevate is developed and built as a tool for the whole ecosystem, not just AlmaLinux. ELevate supports upgrading to/from other distributions and is open for all to contribute to and enhance. You can find more information and FAQ on [almalinux.org/elevate](https://almalinux.org/elevate) and [Migration SIG](/sigs/Migration). 53 | 54 | If are interested in contributing to the project, please check: 55 | * The [ELevate Contribution Guide](/elevate/Contribution-guide) covers the contribution processes to add a 3rd party repository support or testing. 56 | * The [ELevate NG Guide](/elevate/ELevate-NG-testing-guide) covers the upgrade steps using the next Leapp tool version, new features, bug fixes, etc. 57 | * The [ELevate Testing Guide](/elevate/ELevate-testing-guide) covers the steps for upgrade processes that are in testing. 58 | 59 | You can get any help on [AlmaLinux Chat on Mattermost](https://chat.almalinux.org). 60 | -------------------------------------------------------------------------------- /docs/gsoc.md: -------------------------------------------------------------------------------- 1 | # Google Summer of Code 2 | 3 | AlmaLinux is proud to participate in Google's Summer of Code. Please find some details below regarding submitting proposals. 4 | 5 | ## Application Process 6 | 7 | 1. Join our [GSoC Chat Channel](https://chat.almalinux.org/almalinux/channels/gsoc). 8 | 2. Introduce yourself and tell us a little bit of your background and interests. 9 | 3. Let us know what languages, projects or frameworks you have experience or would like to work in. 10 | 4. Have you ever contributed to Open Source before? 11 | 5. What would you like to gain out of this experience? 12 | 13 | ## Ideas 14 | 15 | 1. Enhancements to the [ELevate](https://almalinux.org/elevate) project. ELevate was introduced as a project to allow in place migrations between major versions of RHEL-derivative distribution. The project has proven wildly popular with thousands of migrations completed successfully. Currently the project support 7.x->8.x. As part of this project you would working under the mentorship of our ELevate team members and release engineering to include support for additional versions such as 8.x->9.x and potentially 6.x->7.x. Also, depending on progress, maybe supporting additional package repositories. **Skill Level: Intermediate** **You should know or will learn RPM, dnf, yum, python, bash**. 16 | 17 | 2. Work on security update scripts. As part of this project you will work with our release engineering and security teams to help automate the processing of security update-related information, such as having processing scripts based on certain content or keywords (for example by CVE) and scripts to automatically post errata and updates to to mailing lists. **Skill Level: Easy** **You should know or will learn RPM, dnf, yum, python, bash**. 18 | 19 | 3. Clean up of `countme` scripts and integrate with upstream. AlmaLinux introduced `dnf countme` in December of 2021. As part of this project you will work with our Infrastructure team to help clean up the data and work upstream with the [Fedora Project](https://fedoraproject.org) to have our work integrated upstream. **Skill Level: Easy** **You should know or will learn dnf, yum and python**. 20 | 21 | 4. Custom Distro Spin tool. We always get requests from users and vendors to include a custom package or some custom software within the distribution for their own use or release. As part of this project you will help create a tool which will allow AlmaLinux users to create a custom respins/isos/LiveCDs. **Skill Level: Advanced-Intermediate** **You should know or will learn RPM, dnf, yum, python, bash**. 22 | 23 | 5. Propose your own project! We're open to ideas. 24 | 25 | ## Application 26 | 27 | Once you've chosen an idea submit the application/proposal including all requirements at the Google Summer of Code Site. 28 | -------------------------------------------------------------------------------- /docs/installation/vagrant-boxes.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Vagrant Boxes' 3 | --- 4 | 5 | ###### last updated: 2025-01-06 6 | 7 | # Vagrant Boxes 8 | 9 | AlmaLinux offers official AlmaLinux OS images for Vagrant Boxes. Images are delivered by the AlmaLinux [Cloud SIG](https://wiki.almalinux.org/sigs/Cloud.html). 10 | 11 | The following [AlmaLinux OS 9](https://portal.cloud.hashicorp.com/vagrant/discover/almalinux/9) and [AlmaLinux OS 8](https://portal.cloud.hashicorp.com/vagrant/discover/almalinux/8) images are available on HCP Vagrant Registry: 12 | | Vagrant Box| AlmaLinux OS 9 | AlmaLinux OS 8 | 13 | | --- | --- | --- | 14 | | Libvirt | Intel/AMD (x86_64) | Intel/AMD (x86_64) | 15 | | VirtualBox | Intel/AMD (x86_64) | Intel/AMD (x86_64) | 16 | | Hyper-V | Intel/AMD (x86_64) | Intel/AMD (x86_64) | 17 | | VMware | Intel/AMD (x86_64)
ARM64 (AArch64) | Intel/AMD (x86_64) | 18 | | Parallels | ARM64 (AArch64) | - | 19 | 20 | :::tip 21 | If you are looking for AlmaLinux OS Kitten images, please, visit the [AlmaLinux OS Kitten page](/development/almalinux-os-kitten-10). 22 | ::: 23 | 24 | ## Contribute and Get Help 25 | 26 | If you are interested in contributing or need any assistance, check the [SIG/Cloud](/sigs/Cloud) wiki page and join the *~SIG/Cloud* chat channel in [Mattermost](https://chat.almalinux.org/almalinux/channels/sigcloud) chat channel on [chat.almalinux.org](https://chat.almalinux.org). 27 | 28 | ## Changelog 29 | 30 | ### General updates 31 | **2024-12-23** 32 | 33 | All the boxes have been migrated to the [HCP Vagrant Registry](https://portal.cloud.hashicorp.com/vagrant/discover/almalinux). 34 | 35 | ### AlmaLinux OS version **9.5.20241203** 36 | 37 | * New packages were added: 38 | - `langpacks-en`: Adds `en_US.UTF-8` setting it as a default locale. 39 | - `tcpdump`: A command-line tool for monitoring network traffic. 40 | - `tuned`: Tunes system settings dynamically. Which uses `virtual-guest` profile to optimize the virtual machine performance. 41 | - `nfs-utils`: Built-in capability for mounting Network File System (NFS) type of Vagrant synced folders. 42 | - `cifs-utils`: Built-in capability for mounting Server Message Block (SMB) type of Vagrant synced folders. 43 | - `rsync`: Built-in capability for Rsync type of Vagrant synced folders. 44 | 45 | #### Provider specific changes: 46 | 47 | * virtualbox 48 | * Built in VirtualBox 7.1.4, with Guest Additions included in the same version. 49 | 50 | * vmware_desktop 51 | - Switch from BIOS to UEFI boot on x86_64. 52 | - Use VMXNET Generation 3 (VMXNET3) as the network adapter, as it is the latest, offers the best performance, and is compatible with the AlmaLinux OS kernel. 53 | - Upgrade the VMware virtual machine hardware version from 9 to 21, which is the latest. Since all desktop VMware products are now free, adopting the latest version will be faster, eventually encouraging users to utilize all the features of the latest hardware version. 54 | -------------------------------------------------------------------------------- /docs/migration/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'AlmaLinux Migration Projects' 3 | --- 4 | 5 | ###### last updated: 2025-04-03 6 | 7 | # AlmaLinux Migration Projects 8 | 9 | AlmaLinux offers two projects for migrating your machine, each designed for specific migration paths. 10 | 11 | See the general overviews of options to select the tool/project that best fits your requirements. 12 | 13 | ## AlmaLinux Migration Tool 14 | 15 | [AlmaLinux Migration Tool](https://github.com/AlmaLinux/almalinux-deploy) can be used to convert your EL8 or EL9 machine to the corresponding version. 16 | 17 | The tool supports the following migration paths: 18 | 19 | ![image](/images/migration.svg) 20 | 21 | See the [Migration Guide](/documentation/migration-guide) for the conversion steps. 22 | 23 | ## AlmaLinux ELevate Project 24 | 25 | The ELevate project is an initiative to support migrations between major versions of RHEL-derivatives. 26 | 27 | The [Leapp utility](https://leapp.readthedocs.io) and a few [patches](https://github.com/AlmaLinux/leapp-repository/commits/almalinux) are used to perform in-place migrations between CentOS 7 and Enterprise Linux (EL) 8, and between EL8 and EL9 systems. 28 | 29 | The [Red Hat Upgrade Tool](https://github.com/upgrades-migrations/redhat-upgrade-tool.git) is used to perform in-place migration between CentOS 6 and CentOS 7. 30 | 31 | :::tip 32 | Please note, the ELevate project is designed to perform one-step upgrades. If you wish to perform an upgrade from CentOS7, you need to split the process. Please check the [ELevating CentOS7 to AlmaLinux 9](/elevate/ELevating-CentOS7-to-AlmaLinux-9.md) guide for more information. 33 | ::: 34 | 35 | The ELevate project supports a number of 3rd party repositories: 36 | * EPEL support is currently available for upgrades to AlmaLinux OS only. 37 | * Docker CE - for all supported operating systems. 38 | * MariaDB - for all supported operating systems. 39 | * Microsoft Linux Package Repositories - for all supported operating systems. 40 | * nginx - for all supported operating systems. 41 | * PostgreSQL - for all supported operating systems. 42 | * Imunify - for upgrades to EL 8. 43 | * KernelCare - for all supported operating systems. 44 | 45 | :::tip 46 | You can contribute to the project and add more 3rd party repositories support. See more on the [Contribute](/elevate/Contribution-guide) page. 47 | ::: 48 | 49 | Currently, the following upgrade paths are available: 50 | 51 | ![image](/images/ELevate.svg) 52 | 53 | \* - upgrading from Scientific Linux 7 to AlmaLinux 8 requires a workaround. Please, see more in the [known issues](/elevate/ELevate-frequent-issues).
54 | \** - upgrading to Oracle Linux 9 is available with the [Oracle Leapp utility](https://blogs.oracle.com/linux/post/upgrade-oracle-linux-8-to-oracle-linux-9-using-leapp) and will not be supported by ELevate project. 55 | See the [ELevate](/elevate/) section for the update steps.
56 | \*** - upgrades to AlmaLinux OS 10 (beta) and CentOS 10 are available as ELevate Testing. Upgrade to AlmaLinux OS Kitten 10 is available as ELevate NG. 57 | -------------------------------------------------------------------------------- /docs/release-notes/8.3-beta.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: '8.3 Beta' 3 | --- 4 | # AlmaLinux 8.3 Beta release notes 5 | 6 | The release code name: Purple [Manul](https://en.wikipedia.org/wiki/Pallas%27s_cat). 7 | 8 | CloudLinux is proud to present the beta version of AlmaLinux. After roughly a month and a half from the announcement, here is a 1:1 RHEL binary compatible replacement for your RHEL-based systems. 9 | 10 | This is for the community and by the community, you're the soul of Linux. Thank you for your interest and suggestions so far, keep them coming. 11 | 12 | :::warning 13 | Use this version to thoroughly test your workloads and report any unintended features (ie, bugs) you may find, it will help make AlmaLinux better. 14 | ::: 15 | 16 | ## Installation instructions 17 | 18 | There are three installation ISO images available: 19 | 20 | `AlmaLinux-8.3-beta-1-x86_64-boot.iso` - a single network installation CD image that downloads packages over the Internet. 21 | 22 | `AlmaLinux-8.3-beta-1-x86_64-minimal.iso` - a minimal self-containing DVD image that makes possible offline installation. 23 | 24 | `AlmaLinux-8.3-beta-1-x86_64-dvd1.iso` - a full installation DVD image that contains mostly all AlmaLinux packages. We don't really recommend using it unless you need to set up and use AlmaLinux on a machine without internet access. 25 | 26 | Download a preferable ISO image and verify its checksum. Here is an example for GNU/Linux: 27 | 28 | ```bash 29 | # download and import the AlmaLinux public key 30 | $ wget https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux 31 | $ gpg --import RPM-GPG-KEY-AlmaLinux 32 | 33 | # download a checksums list 34 | $ wget https://repo.almalinux.org/almalinux/8.3-beta/isos/x86_64/CHECKSUM 35 | 36 | # verify the checksums list, we are looking for “Good signature” 37 | $ gpg --verify CHECKSUM 38 | gpg: Signature made Thu 28 Jan 2021 11:39:12 PM MSK 39 | gpg: using RSA key 51D6647EC21AD6EA 40 | gpg: Good signature from "AlmaLinux " [unknown] 41 | gpg: WARNING: This key is not certified with a trusted signature! 42 | gpg: There is no indication that the signature belongs to the owner. 43 | Primary key fingerprint: 5E9B 8F56 17B5 066C E920 57C3 488F CF7C 3ABB 34F8 44 | Subkey fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA 45 | 46 | # download the network install ISO 47 | $ wget https://repo.almalinux.org/almalinux/8.3-beta/isos/x86_64/AlmaLinux-8.3-beta-1-x86_64-boot.iso 48 | 49 | # calculate the downloaded ISO SHA256 checksum 50 | $ sha256sum AlmaLinux-8.3-beta-1-x86_64-boot.iso 51 | d15be406f417e81382b46a54d87dff01c8ca770c847c18703f19146587b61a1f AlmaLinux-8.3-beta-1-x86_64-boot.iso 52 | 53 | # compare it with expected checksum, it should be the same 54 | $ cat CHECKSUM | grep -E 'SHA256.*AlmaLinux-8.3-beta-1-x86_64-boot.iso' 55 | SHA256 (AlmaLinux-8.3-beta-1-x86_64-boot.iso) = d15be406f417e81382b46a54d87dff01c8ca770c847c18703f19146587b61a1f 56 | ``` 57 | 58 | If you decided to use the `AlmaLinux-8.3-beta-1-x86_64-boot.iso` image, you 59 | will need to provide this `https://repo.almalinux.org/almalinux/8.3-beta/BaseOS/x86_64/kickstart/` 60 | repository as the Installation Source: 61 | 62 | ![installation source](./almalinux-install-source.png) 63 | 64 | If you are going to install a non-minimal environment, you will need to add 65 | the AppStream repository to the additional repositories: 66 | `https://repo.almalinux.org/almalinux/8.3-beta/AppStream/x86_64/os/`. 67 | 68 | There are no extra Installation Sources required if you decided to go with 69 | `AlmaLinux-8.3-beta-1-x86_64-minimal.iso` or 70 | `AlmaLinux-8.3-beta-1-x86_64-dvd1.iso` images. 71 | 72 | 73 | ## How to set up a usb key to install AlmaLinux 74 | 75 | ```bash 76 | $ dd if=AlmaLinux-8.3-beta-1-x86_64-boot.iso of=/dev/sdX 77 | ``` 78 | 79 | Where sdX is your usb device. 80 | 81 | 82 | ## Known issues 83 | 84 | * Our libreport/abrt packages aren’t integrated with the bugs.almalinux.org 85 | bug-tracker yet, so a user will have to submit a crash report manually. 86 | Issue: [almbz#2](https://bugs.almalinux.org/view.php?id=2). 87 | * The “perl:5.30” module support is incomplete in the beta release, it will 88 | be finished in the stable. 89 | * We don’t have the latest “jmc” and “maven” module versions. They will be 90 | updated later. 91 | * The “satellite-5-client” module is located in the BaseOS repository instead 92 | of the AppStream. Issue: [almbz#4](https://bugs.almalinux.org/view.php?id=4). 93 | * There is no support for Secure Boot in the beta release. Issue: 94 | [almbz#3](https://bugs.almalinux.org/view.php?id=3). 95 | * The debuginfo repositories are empty and will be populated in a couple of 96 | days after the beta release. 97 | -------------------------------------------------------------------------------- /docs/release-notes/8.3.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: '8.3' 3 | --- 4 | # AlmaLinux 8.3 release notes 5 | 6 | Distributed kernel version: 4.18.0-240. 7 | 8 | ## Installation instructions 9 | 10 | There are three installation ISO images available: 11 | 12 | `AlmaLinux-8.3-x86_64-boot.iso` - a single network installation CD image 13 | that downloads packages over the Internet. 14 | 15 | `AlmaLinux-8.3-x86_64-minimal.iso` - a minimal self-containing DVD image 16 | that makes possible offline installation. 17 | 18 | `AlmaLinux-8.3-x86_64-dvd1.iso` - a full installation DVD image that 19 | contains mostly all AlmaLinux packages. 20 | 21 | Select a mirror listed on the 22 | [mirrors.almalinux.org](https://mirrors.almalinux.org/) website (please, 23 | don't use the `repo.almalinux.org` host directly) and download a suitable ISO 24 | image from the `8.3/isos/x86_64/` directory, for example: 25 | 26 | ```bash 27 | $ wget https://mirror.interserver.net/almalinux/8.3/isos/x86_64/AlmaLinux-8.3-x86_64-boot.iso 28 | ``` 29 | 30 | Download and import the AlmaLinux public key: 31 | 32 | ```bash 33 | $ wget https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux 34 | $ gpg --import RPM-GPG-KEY-AlmaLinux 35 | ``` 36 | 37 | Download and verify a checksums list: 38 | 39 | ```bash 40 | $ wget https://repo.almalinux.org/almalinux/8.3/isos/x86_64/CHECKSUM 41 | 42 | # we are looking for “Good signature” 43 | $ gpg --verify CHECKSUM 44 | gpg: Signature made Fri 19 Feb 2021 03:04:44 PM MSK 45 | gpg: using RSA key 51D6647EC21AD6EA 46 | gpg: Good signature from "AlmaLinux " [unknown] 47 | gpg: WARNING: This key is not certified with a trusted signature! 48 | gpg: There is no indication that the signature belongs to the owner. 49 | Primary key fingerprint: 5E9B 8F56 17B5 066C E920 57C3 488F CF7C 3ABB 34F8 50 | Subkey fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA 51 | ``` 52 | 53 | Verify the downloaded ISO image checksum: 54 | 55 | ```bash 56 | # calculate the downloaded ISO SHA256 checksum 57 | $ sha256sum AlmaLinux-8.3-x86_64-boot.iso 58 | 08fd99fab31277ea3710bfc1ccb8a7229522af5d3987d5b062739cb0dc3b5e3e AlmaLinux-8.3-x86_64-boot.iso 59 | 60 | # compare it with expected checksum, it should be the same 61 | $ cat CHECKSUM | grep -E 'SHA256.*AlmaLinux-8.3-x86_64-boot.iso' 62 | SHA256 (AlmaLinux-8.3-x86_64-boot.iso) = 08fd99fab31277ea3710bfc1ccb8a7229522af5d3987d5b062739cb0dc3b5e3e 63 | ``` 64 | 65 | If you decided to use the `AlmaLinux-8.3-x86_64-boot.iso` image, you will 66 | need to provide the `8.3/BaseOS/x86_64/kickstart/` repository from the 67 | selected mirror as the Installation Source. 68 | 69 | There are no extra Installation Sources required if you decided to go with 70 | either minimal or dvd ISO images. 71 | 72 | 73 | ## Upgrade instructions 74 | 75 | Upgrade the almalinux-release package to the 8.3-3.el8 version from the beta 76 | or rc repositories: 77 | 78 | ```bash 79 | $ dnf clean all && dnf upgrade -y almalinux-release 80 | ``` 81 | 82 | the new package contains updated repository URLs so that you can just run: 83 | 84 | ```bash 85 | $ dnf upgrade -y 86 | ``` 87 | 88 | to update the rest of the packages. 89 | 90 | 91 | ## Changelog 92 | 93 | * The Minimal ISO now proposes to install only environments that can be 94 | installed from it ([almbz#14](https://bugs.almalinux.org/view.php?id=14)). 95 | 96 | 97 | ## Known issues 98 | 99 | * There is no SecureBoot support in this release 100 | ([almbz#3](https://bugs.almalinux.org/view.php?id=3)). We are doing our 101 | best to have it in a stable release. 102 | * The mirrors support implemented with help of the DNF fastestmirror plugin 103 | that is known to be a bit "quirky". We are going to switch to 104 | geo-location-based mirror selection in the stable version. 105 | -------------------------------------------------------------------------------- /docs/release-notes/8.4-beta.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: '8.4 Beta' 3 | --- 4 | # AlmaLinux 8.4 Beta Release Notes 5 | 6 | ## Beta Release 7 | 8 | :::warning 9 | This is a **BETA** release and should not be used for production installations. The provided upgrade instructions should not be used on production machines, unless you don't mind if something breaks. ;) 10 | ::: 11 | 12 | ## Providing Feedback and Getting Help 13 | 14 | Please report any issues you may encounter during tests on the [AlmaLinux Bug Tracker](https://bugs.almalinux.org/). Additionally, if you feel like providing feedback, talking about anything or asking any questions you might want to check out [#AlmaLinux on FreeNode IRC](https://webchat.freenode.net/#almalinux), [The AlmaLinux Forums](https://forums.almalinux.org/c/84-beta/5) and[The AlmaLinux Community on Reddit](https://reddit.com/r/almalinux). 15 | 16 | ## Changelog 17 | 18 | * **Secure Boot is now fully supported** ([almbz#3](https://bugs.almalinux.org/view.php?id=3)) 19 | * Added new module streams: 20 | * Python 3.9 21 | * SWIG 4.0 22 | * Subversion 1.14 23 | * Redis 6 24 | * PostgreSQL 13 25 | * MariaDB 10.5 26 | 27 | * Compiler Updates: 28 | * GCC Toolset 10 29 | * LLVM Toolset 11.0.0 30 | * Rust Toolset 1.49.0 31 | * Go Toolset 1.15.7 32 | 33 | 34 | 35 | ## Installation instructions 36 | 37 | There are three installation ISO images available: 38 | 39 | `AlmaLinux-8.4-beta-1-x86_64-boot.iso` - a single network installation CD image 40 | that downloads packages over the Internet. 41 | 42 | `AlmaLinux-8.4-beta-1-x86_64-minimal.iso` - a minimal self-containing DVD image 43 | that makes possible offline installation. 44 | 45 | `AlmaLinux-8.4-beta-1-x86_64-dvd.iso` - a full installation DVD image that 46 | contains mostly all AlmaLinux packages. 47 | 48 | You can select a mirror closest to your geographic area listed on the [mirrors.almalinux.org](https://mirrors.almalinux.org) website. A local mirrors will be a lot quicker than using ```repo.almalinux.org``` directly. Then, download a suitable ISO image from the 8.4-beta/isos/x86_64/ directory of your source, for example: 49 | 50 | 51 | ```bash 52 | $ wget https://mirror.interserver.net/almalinux/8.4-beta/isos/x86_64/AlmaLinux-8.4-beta-1-x86_64-boot.iso 53 | ``` 54 | 55 | Download and import the AlmaLinux public key: 56 | 57 | ```bash 58 | $ wget https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux 59 | $ gpg --import RPM-GPG-KEY-AlmaLinux 60 | ``` 61 | 62 | Download and verify a checksums list: 63 | 64 | ```bash 65 | $ wget https://repo.almalinux.org/almalinux/8.4-beta/isos/x86_64/CHECKSUM 66 | 67 | # we are looking for “Good signature” 68 | $ gpg --verify CHECKSUM 69 | gpg: Signature made Thu Apr 29 11:34:13 2021 UTC 70 | gpg: using RSA key 51D6647EC21AD6EA 71 | gpg: Good signature from "AlmaLinux " [unknown] 72 | gpg: WARNING: This key is not certified with a trusted signature! 73 | gpg: There is no indication that the signature belongs to the owner. 74 | Primary key fingerprint: 5E9B 8F56 17B5 066C E920 57C3 488F CF7C 3ABB 34F8 75 | Subkey fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA 76 | ``` 77 | 78 | Verify the downloaded ISO image checksum: 79 | 80 | ```bash 81 | # calculate the downloaded ISO SHA256 checksum 82 | $ sha256sum AlmaLinux-8.4-beta-1-x86_64-boot.iso 83 | e0e50a5db9cccfa70eaba9b4465e3e727ebed689f1a30dbbd7fcfa6046f05890 AlmaLinux-8.4-beta-1-x86_64-boot.iso 84 | 85 | # compare it with expected checksum, it should be the same 86 | $ cat CHECKSUM | grep -E 'SHA256.*AlmaLinux-8.4-beta-1-x86_64-boot.iso' 87 | SHA256 (AlmaLinux-8.4-beta-1-x86_64-boot.iso) = e0e50a5db9cccfa70eaba9b4465e3e727ebed689f1a30dbbd7fcfa6046f05890 88 | ``` 89 | 90 | If you decide to use the `AlmaLinux-8.4-beta-1-x86_64-boot.iso` image, you will 91 | need to provide the `8.4-beta/BaseOS/x86_64/kickstart/` repository from the 92 | selected mirror as the Installation Source. 93 | 94 | There are no extra Installation Sources required if you decided to go with 95 | either the minimal or DVD ISO images. 96 | 97 | 98 | ## Upgrade Instructions 99 | 100 | **Please do not use these update instructions on production machines, unless you don't mind if something breaks.** ;) 101 | 102 | Upgrade the almalinux-release package to the 8.4-1.el8 version from the beta 103 | repositories: 104 | 105 | ```bash 106 | $ dnf install -y https://repo.almalinux.org/almalinux/almalinux-release-latest-8-beta.x86_64.rpm 107 | $ dnf clean all 108 | ``` 109 | 110 | the new package contains updated repository URLs so that you can just run: 111 | 112 | ```bash 113 | $ dnf upgrade -y 114 | ``` 115 | 116 | to update the rest of the packages. 117 | 118 | 119 | ## Known issues 120 | 121 | * The mirrors support implemented with help of the DNF fastestmirror plugin is known to be a bit "quirky". We are going to switch to geolocation-based mirror selection in the 8.4 stable version. 122 | * The python39-devel:3.9 module is not available in beta and will be added in stable. 123 | -------------------------------------------------------------------------------- /docs/release-notes/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Release Notes" 3 | --- 4 | 5 | ###### last updated: 2025-05-27 6 | 7 | # AlmaLinux Release Notes 8 | 9 | These are AlmaLinux Release Notes listed with Release Version, General Availability Date, Codename, Kernel Version. 10 | 11 | ### AlmaLinux OS 10 12 | 13 | Version 10 will have active support until 31 May 2030, and security support until 31 May 2035. Each minor version reaches end of life when the new version is released. 14 | 15 | | Release | Codename | Beta Date | Release Date | Kernel | Supported Architectures | 16 | |---|---|---|---|---|---| 17 | | [10.0](/release-notes/10.0) | Purple Lion | 10 Dec 2024 | 27 May 2025 | 6.12.0-55.9.1 | x86_64, x86_64_v2, aarch64, ppc64le, s390x | 18 | 19 | ### AlmaLinux OS 9 20 | 21 | Version 9 will have active support until 31 May 2027, and security support until 31 May 2032. Each minor version reaches end of life when the new version is released. For example, AlmaLinux OS 9.2 reached end of life with the release of AlmaLinux OS 9.3. 22 | 23 | | Release | Codename
[Why cats?](/FAQ.html#why-does-the-almalinux-codename-include-cats) | Beta Date | Release Date | Kernel | Supported Architectures | 24 | |---|---|---|---|---|---| 25 | | [9.6](/release-notes/9.6) | Sage Margay | 08 Apr 2025 | 20 May 2025| 5.14.0-570.12.1 | x86_64, aarch64, ppc64le, s390x | 26 | | [9.5](/release-notes/9.5) | Teal Serval | 15 Oct 2024 | 18 Nov 2024 | 5.14.0-503.11.1 | x86_64, aarch64, ppc64le, s390x | 27 | | [9.4](/release-notes/9.4) | Seafoam Ocelot | 15 Apr 2024 | 06 May 2024 | 5.14.0-427.13.1 | x86_64, aarch64, ppc64le, s390x | 28 | | [9.3](/release-notes/9.3)| Shamrock Pampas Cat | 26 Oct 2023 | 13 Nov 2023 | 5.14.0-362.8.1 | x86_64, aarch64, ppc64le, s390x | 29 | | [9.2](/release-notes/9.2) | Turquoise Kodkod | 27 Apr 2023 | 10 May 2023 | 5.14.0-284.11.1 | x86_64, aarch64, ppc64le, s390x | 30 | | [9.1](/release-notes/9.1) | Lime Lynx | 02 Nov 2022 | 16 Nov 2022 | 5.14.0-162.6.1 | x86_64, aarch64, ppc64le, s390x | 31 | | [9.0](/release-notes/9.0) | Emerald Puma | 19 Apr 2022 | 26 May 2022 | 5.14.0-70.13.1 | x86_64, aarch64, ppc64le, s390x | 32 | 33 | ### AlmaLinux OS 8 34 | 35 | Version 8 will have active support until 31 May 2024, and security support until 31 May 2029. Each minor version reaches end of life when the new version is released. For example, AlmaLinux OS 8.9 reached end of life with the release of AlmaLinux OS 8.10. 36 | 37 | | Release | Codename
[Why cats?](/FAQ.html#why-does-the-almalinux-codename-include-cats) | Beta Date | Release Date | Kernel | Supported Architectures | 38 | |---|---|---|---|---|---| 39 | | [8.10](/release-notes/8.10) | Cerulean Leopard | 17 Apr 2024 | 28 May 2024 | 4.18.0-553 | x86_64, aarch64, ppc64le, s390x | 40 | | [8.9](/release-notes/8.9) | Midnight Oncilla | 2 Nov 2023 | 21 Nov 2023 | 4.18.0-513.5.1 | x86_64, aarch64, ppc64le, s390x | 41 | | [8.8](/release-notes/8.8) | Sapphire Caracal | 21 Apr 2023 | 18 May 2023 | 4.18.0-477.10.1 | x86_64, aarch64, ppc64le, s390x | 42 | | [8.7](/release-notes/8.7) | Stone Smilodon | 25 Oct 2022 | 10 Nov 2022 | 4.18.0-425.3.1 | x86_64, aarch64, ppc64le, s390x | 43 | | [8.6](/release-notes/8.6) | Sky Tiger | 06 May 2022 | 12 May 2022 | 4.18.0-372.9.1 | x86_64, aarch64, ppc64le, s390x | 44 | | [8.5](/release-notes/8.5) | Arctic Sphynx | 13 Oct 2021 | 12 Nov 2021 | 4.18.0-348 | x86_64, aarch64, ppc64le | 45 | | [8.4](/release-notes/8.4) | Electric Cheetah | 20 Apr 2021 | 26 May 2021 | 4.18.0-305 | x86_64, aarch64 | 46 | | [8.3](/release-notes/8.3) | Purple Manul | 1 Feb 2021 | 30 Mar 2021 | 4.18.0-240 | x86_64 | 47 | 48 | ### AlmaLinux OS Kitten 10 49 | ###### Note: Our kitten is not related to [this one](https://www.sandia.gov/ccr/software/kitten-lightweight-kernel/) :D 50 | 51 | AlmaLinux OS Kitten 10 active support will match the end of CentOS Stream 10. 52 | 53 | | Release | Codename
[Why cats?](/FAQ.html#why-does-the-almalinux-codename-include-cats) | Release Date | Kernel | Supported Architectures | 54 | |---|---|---|---|---| 55 | | [Kitten 10](/release-notes/kitten-10) | Lion Cub | 22 Oct 2024 | 6.11.0-25 | x86_64, x86_64_v2, aarch64, ppc64le, s390x | 56 | 57 | 58 | **Run the following commands to find:** 59 | * your AlmaLinux release 60 | 61 | ``` 62 | cat /etc/almalinux-release 63 | ``` 64 | 65 | * your kernel version 66 | 67 | ``` 68 | uname -a 69 | ``` 70 | -------------------------------------------------------------------------------- /docs/release-notes/almalinux-install-source.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/docs/release-notes/almalinux-install-source.png -------------------------------------------------------------------------------- /docs/repos/AlmaLinux.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'AlmaLinux Repositories' 3 | --- 4 | # AlmaLinux Repositories 5 | 6 | Information about the main AlmaLinux repositories and how to install them can be found on this page. 7 | 8 | | Repository | Description | How to Enable on AlmaLinux 8 | How to Enable on AlmaLinux 9 | 9 | | --- | --- | --- | --- | 10 | | BaseOS | Content in the BaseOS repository is intended to provide a core set of the underlying OS functionality that provides the foundation for all installations. | Enabled by default | Enabled by default | 11 | | AppStream | Content in the AppStream repository includes additional user space applications, runtime languages, and databases in support of the varied workloads and use cases. | Enabled by default | Enabled by default | 12 | | Extras | Content in the extras repository includes packages that are not available in RHEL. They are mostly release packages for additional repos like EPEL, ELRepo or the various CentOS SIGs. | Enabled by default | Enabled by default | 13 | | High Availability | The High Availability add-on provides on-demand failover services between nodes within a cluster | # dnf config-manager --set-enabled ha | # dnf config-manager --set-enabled highavailability | 14 | | Plus | This repository contains packages that replace a core component via patched functionality. Packages have a .plus added to their version tag. These are not tested nor available in the upstream product. | # dnf config-manager --set-enabled plus | # dnf config-manager --set-enabled plus | 15 | | PowerTools/CRB | The PowerTools repository contains additional packages for use by developers. This repository is also known as the "CodeReady Builder" repository used on RHEL.| # dnf config-manager --set-enabled powertools | # dnf config-manager --set-enabled crb | 16 | | Real Time (RT) | The Real Time repository is designed to be used on well-tuned systems for applications with extremely high determinism requirements. Kernel system tuning offers the vast majority of the improvement in determinism. | # dnf config-manager --set-enabled rt | # dnf config-manager --set-enabled rt | 17 | | Real Time for NFV (NFV) | The Real Time for NFV repository can be used to virtualize network services, such as routers, firewalls, and load balancers, that have traditionally been run on proprietary hardware. | # dnf config-manager --set-enabled nfv | # dnf config-manager --set-enabled nfv | 18 | | ResilientStorage | The Resilient Storage add-on enables a shared storage or clustered file system to access the same storage device over a network through a pool of data that is available to each server in the group. | # dnf config-manager --set-enabled resilientstorage | # dnf config-manager --set-enabled resilientstorage | 19 | | SAP | The SAP repository provides additional software components necessary to run SAP NetWeaveror SAP Kernel on AlmaLinux | # dnf config-manager --set-enabled sap | # dnf config-manager --set-enabled sap | 20 | | SAPHANA | The SAPHANA repository is tailored to the needs of SAP workloads such as S/4HANA and SAP HANA platform. | # dnf config-manager --set-enabled saphana | # dnf config-manager --set-enabled saphana | 21 | | Testing | Content in the Testing repository includes updates that require additional testing before they are released to stable repositories. **Please, note, that it's *NOT* recommended to install packages from the Testing repo on production machines.** | # dnf install almalinux-release-testing | # dnf install almalinux-release-testing | 22 | | Devel | Content in the Devel repo includes packages that are not normally provided in the base nor extra repositories, but needed for build-time dependencies of other packages. **Devel is *NOT* meant to satisfy runtime dependencies or for long term use on general purpose machines.**| # dnf install almalinux-release-devel | # dnf install almalinux-release-devel | 23 | 24 | AlmaLinux has a [Vault](http://repo.almalinux.org/vault/) repository that provides packages and isos for previous AlmaLinux OS versions. Also, the Vault repository contains 32-bit packages for the latest stable version to build. Vault and other AlmaLinux repositories are available on [repo.almalinux.org](http://repo.almalinux.org/). 25 | -------------------------------------------------------------------------------- /docs/repos/CentOS.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'CentOS SIGs Repositories' 3 | --- 4 | 5 | ###### last modified: 2024-06-12 6 | 7 | # CentOS SIGs Repositories 8 | 9 | CentOS Special Interest Groups (SIGs) are smaller groups within the CentOS community that focus on a small set of issues, in order to either create awareness or to focus on development along a specific topic. SIGs are often very popular and used quite frequently by the community. AlmaLinux has decided to make upstream CentOS SIGs usable from within AlmaLinux for the community's benefit. We encourage contributors interested in SIG development to work upstream and submit contributions there. 10 | 11 | :::warning 12 | Since CentOS 8 Stream has reached its End-Of-Life, corresponding CentOS SIGs packages for AlmaLinux OS 8 are no longer valid and have been removed from the list. 13 | ::: 14 | 15 | ## Cloud SIG 16 | 17 | The [Cloud SIG](https://wiki.centos.org/SpecialInterestGroup/Cloud) focuses on issues around running Cloud Infrastructure / Hypervisor 18 | for on-premise clouds as well as supports other SIGs and projects looking to consume some of the shared resources around on-premise cloud infra. 19 | 20 | | Package | How to Enable on AlmaLinux 9 | 21 | | --- | --- | 22 | | OpenStack Antelope | # dnf install centos-release-openstack-antelope | 23 | | OpenStack Bobcat | # dnf install centos-release-openstack-bobcat | 24 | | OpenStack Caracal | # dnf install centos-release-openstack-caracal | 25 | | OpenStack Client Xena | # dnf install centos-release-openstackclient-xena | 26 | | OpenStack Yoga | # dnf install centos-release-openstack-yoga | 27 | | Openstack Zed | # dnf install centos-release-openstack-zed | 28 | | okd-4.13 | # dnf install centos-release-okd-4.13 | 29 | | okd-4.14 | # dnf install centos-release-okd-4.14 | 30 | | okd-4.15 | # dnf install centos-release-okd-4.15 | 31 | | okd-4.16 | # dnf install centos-release-okd-4.16 | 32 | 33 | 34 | ## Messaging SIG 35 | 36 | The [Messaging SIG](https://wiki.centos.org/SpecialInterestGroup/Messaging) provides a unique source for messaging-related packages. 37 | 38 | | Package | How to Enable on AlmaLinux 9 | 39 | | --- | --- | 40 | | Rabbit 3.8 | # dnf install centos-release-rabbitmq-38 | 41 | 42 | ## Network Functions Virtualization SIG 43 | 44 | The [Network Functions Virtualization SIG](https://wiki.centos.org/SpecialInterestGroup/NFV) provides a stack that will serve as a platform for the deployment and testing of virtual network functions. 45 | 46 | | Package | How to Enable on AlmaLinux 9 | 47 | | --- | --- | 48 | | Openvswitch 2.x
OVN 20.12.x | # dnf install centos-release-nfv-openvswitch | 49 | 50 | ## Operational Tooling SIG 51 | 52 | The [Ops Tools SIG](https://wiki.centos.org/SpecialInterestGroup/OpsTools) provides logging, monitoring and other operational tools for operators, system administrators, devops and developers doing infrastructure engineering on content based on CentOS Linux and related distributions. 53 | 54 | | Package | How to Enable on AlmaLinux 9 | 55 | | --- | --- | 56 | | collectd 5.x | # dnf install centos-release-opstools | 57 | 58 | ## Storage SIG 59 | 60 | The [Storage SIG](https://wiki.centos.org/SpecialInterestGroup/Storage) focuses on deploying CentOS/AlmaLinux as a storage node. 61 | 62 | | Package | How to Enable on AlmaLinux 9 | 63 | | --- | --- | 64 | | Ceph 16 Pacific | # dnf install centos-release-ceph-pacific | 65 | | Ceph 17 Quincy | # dnf install centos-release-ceph-quincy | 66 | | Ceph 18 Reef | # dnf install centos-release-ceph-reef | 67 | | GlusterFS 9 |# dnf install centos-release-gluster9 | 68 | | GlusterFS 10 | # dnf install centos-release-gluster10 | 69 | | GlusterFS 11 | # dnf install centos-release-gluster11 | 70 | | NFS Ganesha 4 | # dnf install centos-release-nfs-ganesha4 | 71 | | NFS Ganesha 5 | # dnf install centos-release-nfs-ganesha5 | 72 | | Samba 4.14 | # dnf install centos-release-samba414 | 73 | | Samba 4.15 | # dnf install centos-release-samba415 | 74 | | Samba 4.16 | # dnf install centos-release-samba416 | 75 | | Samba 4.17 | # dnf install centos-release-samba417 | 76 | | Samba 4.18 | # dnf install centos-release-samba418 | 77 | | Samba 4.19 | # dnf install centos-release-samba419 | 78 | | Samba 4.20 | # dnf install centos-release-samba420 | 79 | 80 | ## Virtualization SIG 81 | 82 | The [Virtualization SIG](https://wiki.centos.org/SpecialInterestGroup/Virtualization) aims to deliver a user consumable full stack for virtualization technologies. This includes delivery, deployment, management, update and patch application (for full lifecycle management) of the baseline platform when deployed in sync with a technology curated by the Virt-SIG. 83 | 84 | | Package | How to Enable on AlmaLinux 9 | 85 | | --- | --- | 86 | | oVirt 4.5 | # dnf install centos-release-ovirt45 | 87 | -------------------------------------------------------------------------------- /docs/repos/Extras.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Extra Repositories' 3 | --- 4 | # Extra Repositories 5 | 6 | ## EPEL 7 | 8 | Extra Packages for Enterprise Linux or [EPEL](https://fedoraproject.org/wiki/EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux. 9 | EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. 10 | 11 | | Repository | How to Enable | 12 | | --- | --- | 13 | | EPEL and CRB | # dnf install epel-release | 14 | 15 | For more detailed information see the [EPEL Quickstart Guide](https://docs.fedoraproject.org/en-US/epel/). 16 | 17 | :::tip 18 | During the installation process, you might get a prompt to install a GPG key. Compare the key to the "Primary key fingerprint" (see ["Verify the downloaded ISO image checksum:"](../documentation/installation-guide.md#iso-verification)) and if the fingerprints match, type "y" to continue. 19 | ::: 20 | 21 | :::tip 22 | Most EPEL packages require packages from PowerTools/CRB repository as dependencies. Run the suitable command to enable the PowerTools/CRB repository: 23 | 24 | **AlmaLinux OS 8** 25 | 26 | ``` 27 | dnf config-manager --set-enabled powertools 28 | ``` 29 | 30 | **AlmaLinux OS 9** 31 | ``` 32 | dnf config-manager --set-enabled crb 33 | ``` 34 | ::: 35 | 36 | ## The ELRepo Project 37 | 38 | [The ELRepo Project](http://elrepo.org) focuses on hardware related packages to enhance your experience with Enterprise Linux. This includes filesystem drivers, graphics drivers, network drivers, sound drivers, webcam and video drivers. Newer kernels, `kernel-ml` and `kernel-lt`, are also available. 39 | 40 | | Repository | How to Enable | 41 | | --- | --- | 42 | | ELRepo | # dnf install elrepo-release | 43 | 44 | ## RPM Fusion 45 | [RPM Fusion](https://rpmfusion.org/) provides software that RHEL and other Enterprise Linux distributions do not ship (like software codecs). 46 | 47 | | Repository | How to Enable | 48 | | --- | --- | 49 | | RPM Fusion | See _[Installing EPEL and RPM Fusion](/documentation/epel-and-rpmfusion)_ | 50 | -------------------------------------------------------------------------------- /docs/repos/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Repositories" 3 | --- 4 | 5 | # Repositories 6 | 7 | A repository stores software packages on a remote server that are used for installing and updating on Linux systems. 8 | 9 | Any repository that is intended for RHEL or CentOS can be used in AlmaLinux. As a part of the project, besides AlmaLinux repositories, you may also use CentOS SIGs, EPEL, the ELRepo Project and Synergy repositories 10 | with the following instructions: 11 | 12 | * [AlmaLinux](/repos/AlmaLinux) - AlmaLinux repositories. 13 | * [CentOS SIG](/repos/CentOS) - CentOS SIG's repositories. 14 | * [Extras](/repos/Extras) - Extra repositories such as EPEL and the ELRepo Project. 15 | * [Synergy](/repos/Synergy) - Repository for any RHEL-compatible distribution with packages that are not present in RHEL or EPEL yet but were requested by the Community. 16 | -------------------------------------------------------------------------------- /docs/repos/Synergy.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Synergy Repository" 3 | --- 4 | 5 | # Synergy Repository 6 | 7 | ## About 8 | Synergy repository contains packages that are not present in RHEL or EPEL yet but were requested by the Community for the Community. 9 | This repository can be considered a pre-EPEL repo, since the AlmaLinux OS Foundation, as a member of the EL community, will make every effort to get packages into EPEL so that they become widely available on all RHEL-compatible distributions. 10 | The release package of the Synergy repository also allows you to use it not only with AlmaLinux, but with any RHEL-compatible distribution, see the instructions below. 11 | 12 | :::tip Package removal policy 13 | Please, **note**, that as soon as a package is in EPEL or RHEL, it will be removed from the Synergy repository. 14 | ::: 15 | 16 | ## Enabling the repository 17 | 18 | Synergy repository can be enabled for AlmaLinux OS and for other distros in EL-ecosystem like RHEL, CentOS, Rocky Linux, etc. 19 | 20 | To enable the Synergy repository on AlmaLinux machines run the following command: 21 | ``` 22 | dnf install -y almalinux-release-synergy 23 | ``` 24 | 25 | To enable the Synergy repository on any RHEL-compatible distribution run the following command: 26 | ``` 27 | dnf install -y https://repo.almalinux.org/almalinux/almalinux-release-synergy-latest-$(rpm -E %rhel).noarch.rpm 28 | ``` 29 | 30 | :::tip Enabling PowerTools/CRB repository 31 | Please, note, that enabling the Synergy repository will also automatically enable EPEL and PowerTools/CRB repositories if epel-release provided by your distribution is recent enough. If you still don't have PowerTools/CRB enabled you should run the following: 32 | ``` 33 | dnf update -y epel-release 34 | crb enable 35 | ``` 36 | ::: 37 | :::warning Distributions without epel-release package 38 | If your distribution doesn't provide `epel-release` package you'll get a dependency error during `almalinux-release-synergy` package install. In this case use the following command to enable the Synergy repository: 39 | ``` 40 | dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-$(rpm -E %rhel).noarch.rpm \ 41 | https://repo.almalinux.org/almalinux/almalinux-release-synergy-latest-$(rpm -E %rhel).noarch.rpm 42 | ``` 43 | ::: 44 | 45 | Available packages can also be found on [repo.almalinux.org](https://repo.almalinux.org/): 46 | * [AlmaLinux OS 8](https://repo.almalinux.org/almalinux/8/synergy/) 47 | * [AlmaLinux OS 9](https://repo.almalinux.org/almalinux/9/synergy/) 48 | 49 | You can use the closest [mirror](https://mirrors.almalinux.org/isos.html) for faster access. 50 | 51 | ## Request a package 52 | 53 | A package can be requested via [Packaging chat channel](https://chat.almalinux.org/almalinux/channels/engineeringpackaging) in Mattermost. 54 | To be included in the Synergy repository, a package must meet the following criteria: 55 | - The package must not be in the RHEL repositories (including additional repositories like RT, NFV, SAP, etc.) 56 | - The package must not be in the EPEL repository 57 | - The package must not update, replace, or conflict with packages from RHEL and EPEL 58 | - The package developer does not maintain a YUM/DNF repository for RHEL-compatible distributions 59 | 60 | -------------------------------------------------------------------------------- /docs/series/README.md: -------------------------------------------------------------------------------- 1 | # Howto Series: AlmaLinux Tutorials 🚀 2 | 3 | Welcome to our Howto series on AlmaLinux! In this series, we provide comprehensive guides and tutorials to help you learn and master various aspects of AlmaLinux. Whether you are interested in Nginx or system-related topics, we've got you covered. 4 | 5 | ## Nginx Series 6 | 7 | The Nginx series focuses on all things related to Nginx web server. From installation to configuration, security, and optimization, you will find step-by-step guides to help you deploy and manage a powerful web server on AlmaLinux. 8 | 9 | Browse the articles in the Nginx series: 10 | 11 | - [A01](nginx/NginxSeriesA01.md) ❯ Beginner's Guide 12 | - [A02 R8](nginx/NginxSeriesA02R8.md) ❯ AlmaLinux 8.x Installation Examples 13 | - [A02 R9.1](nginx/NginxSeriesA02R91.md) ❯ AlmaLinux 9.1 Installation Examples 14 | - [A02 R9.2](nginx/NginxSeriesA02R92.md) ❯ AlmaLinux 9.2 Installation Examples 15 | - [A03](nginx/NginxSeriesA03.md) ❯ Default Configuration Guide 16 | - [A04](nginx/NginxSeriesA04P1.md) ❯ Secure Nginx Deployment 17 | 18 | ## System Series 19 | 20 | **The vision:** (In near future) The System series covers a wide range of system-related topics on AlmaLinux. This guides will help you enhance your system administration skills and ensure the stability and security of your AlmaLinux environment. 21 | 22 | Explore the articles in the System series: 23 | 24 | - [A01](system/SystemSeriesA01.md) ❯ Application Streams 25 | - [A02](system/SystemSeriesA02.md) ❯ Firewalld: A Beginner's Guide 26 | - [A03](system/SystemSeriesA03.md) ❯ NVIDIA Driver Installation Guide 27 | - [A03 R8](system/SystemSeriesA03R8.md) ❯ NVIDIA Driver: Installation on 8.x 28 | - [A03 R9](system/SystemSeriesA03R9.md) ❯ NVIDIA Driver: Installation on 9.x 29 | - [A04](system/SystemSeriesA04.md) ❯ Snapd Installation Guide 30 | - [A05](system/SystemSeriesA05.md) ❯ Multimedia Codecs Installation Guide 31 | 32 | Dive into our Howto series and unlock the full potential of AlmaLinux. Happy hacking! 🐧💻🚀 33 | 34 | ---- 35 | 36 | ##### Trademark Notices 37 | :::warning 38 | 39 | **AlmaLinux** is a registered trademark of AlmaLinux OS Foundation. 40 | 41 | **Linux®** is a registered trademark of Linus Torvalds in the U.S. and other countries. 42 | 43 | **macOS** are trademarks of Apple Inc., registered in the U.S. and other countries. 44 | 45 | **NVIDIA** is a registered trademark of NVIDIA Corporation in the U.S. and other countries. 46 | 47 | **Red Hat** is a registered trademark of Red Hat, Inc. or its subsidiaries in the United States and other countries. 48 | 49 | **Windows** is a registered trademark of Microsoft Corporation in the United States and other countries. 50 | 51 | All other trademarks are the property of their respective owners. 52 | ::: 53 | -------------------------------------------------------------------------------- /docs/series/nginx/README.md: -------------------------------------------------------------------------------- 1 | # AlmaLinux Nginx Series 2 | 3 | Welcome! 4 | ---- 5 | The articles in the series guide you through the installation, configuration, security, and management of your Nginx server. 6 | 7 | **Article List** 8 | ---- 9 | 10 | - [A01](NginxSeriesA01.md) ❯ Beginner's Guide 11 | - [A02 R8](NginxSeriesA02R8.md) ❯ AlmaLinux 8.x Installation Examples 12 | - [A02 R9.1](NginxSeriesA02R91.md) ❯ AlmaLinux 9.1 Installation Examples 13 | - [A02 R9.2](NginxSeriesA02R92.md) ❯ AlmaLinux 9.2 Installation Examples 14 | - [A03](NginxSeriesA03.md) ❯ Default Configuration Guide 15 | - [A04](NginxSeriesA04P1.md) ❯ Secure Nginx Deployment 16 | -------------------------------------------------------------------------------- /docs/series/system/README.md: -------------------------------------------------------------------------------- 1 | # AlmaLinux System Series 2 | 3 | Welcome! 4 | ---- 5 | This series will guide you through the installation, configuration, security, and management of your server. 6 | 7 | **Article List** 8 | ---- 9 | - [A01](SystemSeriesA01.md) ❯ Application Streams 10 | - [A02](SystemSeriesA02.md) ❯ Firewalld: A Beginner's Guide 11 | - [A03](SystemSeriesA03.md) ❯ NVIDIA Driver Installation Guide 12 | - [A04](SystemSeriesA04.md) ❯ Snapd Installation Guide 13 | - [A05](SystemSeriesA05.md) ❯ Multimedia: Install Media Codecs 14 | - [A06](SystemSeriesA06.md) ❯ Multimedia Codecs & Libraries for VFX Workstation Installation Guide 15 | - [A07](SystemSeriesA07.md) ❯ Change from Wayland to Xorg Installation Guide 16 | - [A08](SystemSeriesA08.md) ❯ Earlyoom (Out of Memory) Installation Guide 17 | - [A09](SystemSeriesA09.md) ❯ Journalctl Persistent Installation Guide 18 | - [A10](SystemSeriesA10.md) ❯ Chrony Installation Guide 19 | 20 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA04.md: -------------------------------------------------------------------------------- 1 | # A04 ❯ Snapd Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐☆☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2023-06-07 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 |
9 | 10 | ## 🌟 Introduction 11 | 12 | The snap packages for AlmaLinux can be found in the Extra Packages for Enterprise Linux (EPEL) repository. :package: 13 | 14 | ## Enable EPEL repo :minidisc: 15 | If you haven’t done it yet, enable the EPEL repository for your AlmaLinux system: 16 | ``` 17 | sudo dnf install epel-release 18 | sudo dnf upgrade 19 | ``` 20 | 21 | ## Install :hammer_and_wrench: 22 | 23 | :::tip 24 | :information_source: 25 | Important for cloud images users! 26 | 27 | Before proceeding with the installation of snapd, it’s important to install the `kernel-modules` package as these type of images come with limited number of modules. This package includes SquashFS, a compressed read-only file system for Linux, which is necessary for the snapd functionality. 28 | :::tip 29 | 30 | Install the `kernel-modules`, using the following command: 31 | ``` 32 | sudo dnf install kernel-modules 33 | ``` 34 | 35 | With the EPEL repository and kernel-modules added to your AlmaLinux installation, you can now install the snapd package: :inbox_tray: 36 | 37 | ``` 38 | sudo dnf install snapd 39 | ``` 40 | 41 | ## Set up :gear: 42 | 43 | Next, instruct systemd to enable the unit providing the snapd communication socket: 44 | 45 | ``` 46 | sudo systemctl enable --now snapd.socket 47 | ``` 48 | 49 | Then, enable classic snap support, create a symbolic link it requires: 50 | 51 | ``` 52 | sudo ln -s /var/lib/snapd/snap /snap 53 | ``` 54 | 55 | ### Last installation step :checkered_flag: 56 | 57 | To make sure the paths for snapd are updated correctly, you just need to re-login. Reboot will work too. :arrows_counterclockwise: 58 | 59 | Congratulations, snapd is now installed and fully operational! :tada: 60 | 61 | ### Optional: for Desktop Users :desktop_computer: 62 | 63 | If you’re using a desktop environment, consider installing the Snap Store app (https://forum.snapcraft.io/t/installing-the-snap-store-app/10077) 🛍️ 64 | 65 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA05.md: -------------------------------------------------------------------------------- 1 | # A05 ❯ Multimedia Codecs Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐☆☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2024-06-11 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 | 9 | 10 | ## Add EPEL: 11 | 12 | ```Bash 13 | sudo dnf -y install epel-release 14 | sudo dnf makecache 15 | ``` 16 | 17 | ## Enable CRB: 18 | ```Bash 19 | sudo dnf config-manager --set-enabled crb 20 | ``` 21 | 22 | ## Add RPMFusion: 23 | Starting from step 2, follow [Installing EPEL and RPM Fusion](/documentation/epel-and-rpmfusion/). 24 | 25 | ## Install multimedia codecs: 26 | 27 | ```bash 28 | sudo dnf -y group install multimedia 29 | sudo dnf -y install ffmpeg ffmpeg-libs ffmpeg-devel mpv 30 | ``` 31 | 32 | ## Extra Audio packages 33 | ```bash 34 | sudo dnf -y group install sound-and-video 35 | ``` 36 | 37 | ## Play a DVD 38 | ```Bash 39 | sudo dnf -y install libdvdcss 40 | ``` 41 | 42 | ## Install mediaplayers like VLC, MPV or Celluloid from RPMFusion 43 | ```bash 44 | sudo dnf install vlc 45 | sudo dnf install mpv 46 | sudo dnf install celluloid # Simple GTK+ frontend for mpv 47 | ``` 48 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA06.md: -------------------------------------------------------------------------------- 1 | # A06 ❯ Multimedia Codecs & Libraries for VFX Workstation Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐⭐☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2024-02-02 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 | 9 | 10 | These packages have been needed for multiple software, such has "Thinkbox Deadline" and were either backported, requested, or discovered as alternatives for AlmaLinux 9 for users migrating from enterprise Linux 8. 11 | 12 | # Enable CRB: 13 | ```Bash 14 | sudo dnf config-manager --set-enabled crb 15 | ``` 16 | # Add EPEL9: 17 | 18 | ```Bash 19 | sudo dnf -y install epel-release 20 | ``` 21 | 22 | # Add RPMFusion: 23 | ```Bash 24 | sudo dnf install -y --nogpgcheck https://mirrors.rpmfusion.org/free/el/rpmfusion-free-release-$(rpm -E %rhel).noarch.rpm 25 | ``` 26 | 27 | # Add almalinux-release-devel: 28 | ```Bash 29 | sudo dnf almalinux-release-devel 30 | ``` 31 | 32 | # Add almalinux Extras: 33 | ```Bash 34 | sudo dnf config-manager --set-enabled extras 35 | ``` 36 | 37 | # Update System Packages : 38 | ```Bash 39 | sudo dnf update -y 40 | ``` 41 | 42 | # Reboot to apply updates : 43 | ```Bash 44 | sudo reboot 45 | ``` 46 | 47 | # Network Share essentials : 48 | ```Bash 49 | sudo dnf install samba -y 50 | sudo dnf insall cifs-utils -y 51 | sudo dnf install nfs-utils -y 52 | ``` 53 | 54 | # Packages groups essentials : 55 | ```Bash 56 | sudo dnf groupinstall Workstation -y 57 | sudo dnf groupinstall "Development Tools" -y 58 | sudo dnf groupinstall "RPM Development Tools" -y 59 | sudo dnf groupinstall "System Tools" -y 60 | ``` 61 | 62 | # Install multimedia codecs: 63 | ```bash 64 | sudo dnf -y groupinstall multimedia --with-optional 65 | sudo dnf -y install ffmpeg 66 | sudo dnf -y install x264 67 | sudo dnf -y install x264-devel 68 | sudo dnf -y install SDL2 69 | sudo dnf -y install ffmpeg-devel 70 | ``` 71 | # Install multimedia codecs **(Required if using Thinkbox Deadline)**: 72 | ```bash 73 | sudo dnf -y install libcrypto.so.1.1 74 | ``` 75 | 76 | # Libraries and codec needed for VFX software : 77 | ```bash 78 | sudo dnf -y install ncurses-compat-libs 79 | sudo dnf -y install gstreamer1-libav 80 | sudo dnf -y install libnsl 81 | sudo dnf -y install vulkan 82 | sudo dnf -y install libglvnd-devel 83 | sudo dnf -y install mesa-libGL 84 | sudo dnf -y install mesa-libGLU 85 | sudo dnf -y install gstreamer1-libav 86 | sudo dnf -y install libnsl 87 | sudo dnf -y install xmessage 88 | ``` 89 | 90 | # Fix for locale language not being applied with GDM : 91 | ```bash 92 | sudo localectl set-locale LANG=en_US.UTF-8 93 | ``` 94 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA07.md: -------------------------------------------------------------------------------- 1 | # A07 ❯ Change from Wayland to Xorg Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐☆☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2024-02-02 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 | 9 | In some case Wayland may interfere with software installed and require Xorg instead. This is the way to rollback to Xorg. 10 | 11 | # Open the terminal on the host machine. 12 | 13 | # Gain administrative privileges by using the sudo command: 14 | ```Bash 15 | sudo su 16 | ``` 17 | 18 | # Navigate to the /etc/gdm/ directory: 19 | ```Bash 20 | cd /etc/gdm/ 21 | ``` 22 | 23 | # Open the custom.conf file in a text editor of your choice. For example, you can use the nano editor: 24 | ```Bash 25 | Ensure that these lines are within the block that starts with # {mark} ANSIBLE MANAGED BLOCK. 26 | sudo nano custom.conf 27 | ``` 28 | 29 | # Find or add the following lines to the file: 30 | ```Bash 31 | WaylandEnable=false 32 | DefaultSession=gnome-xorg.desktop 33 | ``` 34 | 35 | # Save the changes and exit the text editor. If you are using nano, you can press Ctrl + X, then press Y to confirm changes, and finally press Enter to exit. 36 | 37 | # Restart the system or the display manager for the changes to take effect. 38 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA08.md: -------------------------------------------------------------------------------- 1 | # A08 ❯ Earlyoom (Out of Memory) Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐☆☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2024-02-02 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 | 9 | EarlyOOM project can be found here: [https://github.com/rfjakob/earlyoom](https://github.com/rfjakob/earlyoom) 10 | 11 | ## Install EarlyOOM: 12 | ```bash 13 | sudo dnf install earlyoom -y 14 | ``` 15 | 16 | ## Configure EarlyOOM to start at boot: 17 | ```bash 18 | sudo systemctl enable earlyoom 19 | ``` 20 | 21 | ## Configure Earlyoom Parameters: 22 | 23 | Open the terminal on the host machine. 24 | 25 | ## Gain administrative privileges by using the sudo command: 26 | ```bash 27 | sudo su 28 | ``` 29 | 30 | ## Open the /etc/default/earlyoom file in a text editor of your choice. For example, you can use the nano editor: 31 | ```bash 32 | sudo nano /etc/default/earlyoom 33 | ``` 34 | 35 | ## Find or add the following lines to the file: 36 | ```bash 37 | EARLYOOM_ARGS="-m 10 -s 75 -r 3600 --avoid '(^|/)(init|Xorg|ssh|gnome)$'" 38 | ``` 39 | Save the changes and exit the text editor. If you are using nano, you can press Ctrl + X, then press Y to confirm changes, and finally press Enter to exit. 40 | 41 | **Please note that these are the options that worked in my case and may not work for all specific cases. Please refer to the command options for EarlyOOM:** 42 | ```bash 43 | User 44 | Command line options 45 | earlyoom v1.6.2-34-g75a8852-dirty 46 | Usage: ./earlyoom [OPTION]... 47 | 48 | -m PERCENT[,KILL_PERCENT] set available memory minimum to PERCENT of total 49 | (default 10 %). 50 | earlyoom sends SIGTERM once below PERCENT, then 51 | SIGKILL once below KILL_PERCENT (default PERCENT/2). 52 | -s PERCENT[,KILL_PERCENT] set free swap minimum to PERCENT of total (default 53 | 10 %). 54 | Note: both memory and swap must be below minimum for 55 | ``` 56 | Reference: [https://github.com/rfjakob/earlyoom](https://github.com/rfjakob/earlyoom) 57 | 58 | ## Set the owner and group of the file to root: 59 | ```bash 60 | chown root:root /etc/default/earlyoom 61 | ``` 62 | 63 | ## Set the file permissions to 0644: 64 | ```bash 65 | chmod 0644 /etc/default/earlyoom 66 | ``` 67 | 68 | # Notify the system about the changes made by restarting the earlyoom service: 69 | ```bash 70 | systemctl restart earlyoom 71 | ``` 72 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA09.md: -------------------------------------------------------------------------------- 1 | # A09 ❯ Journalctl Persistent Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐☆☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2024-02-02 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 | 9 | Jounalctl Man page: https://man7.org/linux/man-pages/man1/journalctl.1.html 10 | 11 | # Check if the journal directory exists: 12 | ```bash 13 | stat /var/log/journal 14 | ``` 15 | 16 | # Create the journal directory if it doesn't exist: 17 | ```bash 18 | mkdir -p /var/log/journal 19 | ``` 20 | 21 | # Configure systemd journal settings: 22 | **Edit the /etc/systemd/journald.conf file using a text editor like nano or vi. Ensure the following content is set:** 23 | ```bash 24 | # This file is part of systemd. 25 | # 26 | # systemd is free software; you can redistribute it and/or modify it 27 | # under the terms of the GNU Lesser General Public License as published by 28 | # the Free Software Foundation; either version 2.1 of the License, or 29 | # (at your option) any later version. 30 | # 31 | # Entries in this file show the compile time defaults. 32 | # You can change settings by editing this file. 33 | # Defaults can be restored by simply deleting this file. 34 | # 35 | # See journald.conf(5) for details. 36 | 37 | [Journal] 38 | #Storage=auto 39 | #Compress=yes 40 | #Seal=yes 41 | #SplitMode=uid 42 | #SyncIntervalSec=5m 43 | #RateLimitIntervalSec=30s 44 | #RateLimitBurst=10000 45 | SystemMaxUse=200M 46 | SystemKeepFree=100M 47 | SystemMaxFileSize=20M 48 | SystemMaxFiles=10 49 | #RuntimeMaxUse= 50 | #RuntimeKeepFree= 51 | #RuntimeMaxFileSize= 52 | #RuntimeMaxFiles=100 53 | #MaxRetentionSec= 54 | #MaxFileSec=1month 55 | #ForwardToSyslog=no 56 | #ForwardToKMsg=no 57 | #ForwardToConsole=no 58 | #ForwardToWall=yes 59 | #TTYPath=/dev/console 60 | #MaxLevelStore=debug 61 | #MaxLevelSyslog=debug 62 | #MaxLevelKMsg=notice 63 | #MaxLevelConsole=info 64 | #MaxLevelWall=emerg 65 | #LineMax=48K 66 | ``` 67 | 68 | **This file can be modified to your preference, please see the Man page for all possible options: https://man7.org/linux/man-pages/man1/journalctl.1.html 69 | 70 | # Ensure the systemd-journald service is running: 71 | ```bash 72 | systemctl start systemd-journald 73 | ``` 74 | 75 | # Restart systemd-journald: 76 | ```bash 77 | systemctl restart systemd-journald 78 | ``` 79 | 80 | **After enabling persistent Journalctl, the files will be in a rolling state up to the maximum size specfied and in the location specified** 81 | -------------------------------------------------------------------------------- /docs/series/system/SystemSeriesA10.md: -------------------------------------------------------------------------------- 1 | # A10 ❯ Chrony Installation Guide 2 | ℹ️ This article is part of AlmaLinux [System Series](/series/). 3 |
4 | | 💡 | Experience Level | ⭐☆☆☆☆ | 5 | |--- | --------- | --------| 6 | | 📆 | Last modified | 2024-02-02 | 7 | | 🔧 | Tested by
↳ version \| platform \| date | NOT TESTED YET | 8 | 9 | Chrony Man page: https://chrony-project.org/ 10 | 11 | ## Install Chrony: 12 | ```bash 13 | dnf install chrony -y 14 | ``` 15 | 16 | # Configure Chrony conf file: 17 | ## Edit the /etc/chrony.conf file using a text editor like nano or vi. 18 | Ensure the following content is set: 19 | ```bash 20 | # chrony.conf 21 | # Use Google's NTP server 22 | server time.google.com iburst 23 | 24 | # Local clock as a fallback source 25 | server 127.127.1.0 iburst 26 | 27 | # Set the time zone 28 | rtcsync 29 | 30 | maxdistance 16.0 31 | 32 | # Driftfile 33 | driftfile /var/lib/chrony/drift 34 | 35 | # Allow larger adjustments to the system clock 36 | makestep 1.0 3 37 | 38 | # Leap seconds configuration 39 | leapsec tz right/UTC 40 | 41 | # Adjust the following line to allow systems in the XXX.XXX.XXX.XXX/XX subnet to access this client. 42 | # Ensure to modify the XXX.XXX.XXX.XXX/XX part based on your network configuration. 43 | allow XXX.XXX.XXX.XXX/XX 44 | 45 | # Logging 46 | log tracking measurements statistics 47 | logdir /var/log/chrony 48 | ``` 49 | For more details on configuring Chrony, you can refer to the Configuration Reference for the version of [Chrony Documentation](https://chrony-project.org/documentation.html) that matches the version you have installed. 50 | 51 | 52 | # Restart Chrony service: 53 | ```bash 54 | systemctl restart chronyd 55 | ``` 56 | -------------------------------------------------------------------------------- /docs/sigs/Atomic.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Atomic SIG" 3 | --- 4 | # Atomic SIG 5 | 6 | The purpose of the Atomic SIG is to explore atomic Linux technologies like bootc, to develop a modern AlmaLinux-based immutable desktop system, and to enable others to build upon our tooling. In short, the purpose of this SIG is to expand AlmaLinux's role in the atomic desktop space. 7 | 8 | ## How to Join 9 | 10 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 11 | 12 | **Where we chat** 13 | 14 | We use [Mattermost](https://chat.almalinux.org/almalinux/channels/sigatomic) for communication. 15 | 16 | **Where and when we meet** 17 | 18 | We do not currently hold regular meetings, but work asynchronously in Mattermost to accomplish our goals. 19 | 20 | ## Activities, projects, and deliverables 21 | 22 | * Base desktop bootc image and ISO installer based on [Cloud SIG](https://wiki.almalinux.org/sigs/Cloud.html)'s bootc images starting with AlmaLinux 10. 23 | * Templates/automation/examples to guide downstream extension/customization of the base image 24 | * A workstation distribution that is opinionated, modern, and polished, based on the previous deliverables 25 | 26 | ### Help wanted 27 | 28 | Contributions take all kinds of shapes and sizes, and we welcome everyone! If you have expertise or time and would like to help us out, please get in touch! 29 | 30 | ## SIG members 31 | 32 | * [Isaac Beverly](mailto:imbev@protonmail.com) - SIG lead 33 | * Chat: [@imbev](https://chat.almalinux.org/almalinux/messages/@imbev) 34 | * Github: [imbev](https://github.com/imbev) 35 | * [Alex Iribarren](mailto:alex@almalinux.org) - SIG lead 36 | * Chat: [@alex.iribarren](https://chat.almalinux.org/almalinux/messages/@alex.iribarren) 37 | * Github: [alexiri](https://github.com/alexiri/) 38 | * [James Reilly](mailto:jreilly1821@gmail.com) - SIG lead 39 | * Chat: [@jreilly1821](https://chat.almalinux.org/almalinux/messages/@jreilly1821) 40 | * Github: [hanthor](https://github.com/hanthor) 41 | * [Cameron Knauff](mailto:cameron@stillhq.io) 42 | * Chat: [@cameron](https://chat.almalinux.org/almalinux/messages/@cameron) 43 | * Github: [PizzaLovingNerd](https://github.com/PizzaLovingNerd) 44 | 45 | ## Additional information for SIG application approval 46 | 47 | We hope to be able to start quickly and have at least the base image ready by Q3 2025. 48 | 49 | We will require the creation of: 50 | * An Atomic SIG channel on chat.almalinux.org 51 | * Several git repositories under an AlmaLinux namespace at GitHub 52 | * Several OCI repositories under an AlmaLinux namespace at DockerHub and Quay.io 53 | * (Optional) Access to [openQA](https://openqa.almalinux.org/) to test our images before release 54 | -------------------------------------------------------------------------------- /docs/sigs/Core.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Core SIG" 3 | --- 4 | 5 | ######last updated: 2024-04-22 6 | 7 | # Core SIG 8 | 9 | The Core team is responsible for the AlmaLinux OS distribution itself. This includes, but is not limited to building new distribution versions, delivering updates, core tooling development, and maintenance. 10 | 11 | ## How to Join 12 | 13 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 14 | 15 | **Where we chat** 16 | 17 | The Core SIG uses the [SIG/Core](https://chat.almalinux.org/almalinux/channels/sigcore) chat channel for communication. 18 | 19 | **Where and when we meet** 20 | 21 | We meet on Google Meet every other Tuesday at 16:00 UTC. If you would like to join, join the chat and ask for an invite! 22 | 23 | ## Activities, projects, and deliverables 24 | 25 | * The AlmaLinux OS distribution. 26 | * The mirrors infrastructure: [AlmaLinux/mirrors](https://github.com/AlmaLinux/mirrors). 27 | * The migration script: [AlmaLinux/almalinux-deploy](https://github.com/AlmaLinux/almalinux-deploy/). 28 | * Bug reports processing: [bugs.almalinux.org](https://bugs.almalinux.org/). 29 | 30 | 31 | ### Help wanted 32 | 33 | * Technical writers for working on announcements, security bulletins, wiki 34 | articles and so on. 35 | * RPM packagers/maintainers. 36 | * Bug reports processing: collecting information, reproducing, escalating to 37 | developers, communicating upstream, etc. 38 | * Design and automate test scenarios: Ansible, [Bats](https://github.com/bats-core/bats-core), 39 | Bash, CI/CD, [Testinfra](https://testinfra.readthedocs.io/en/latest/), 40 | [Packer](https://packer.io/), Python, AWS, Azure, etc. 41 | * Bash and Python developers for working on distribution tooling. 42 | * Python, PostgreSQL developers for working on our monitoring/build systems 43 | and other projects. 44 | 45 | If you can help, please join us at [Core SIG on Mattermost](https://chat.almalinux.org/almalinux/channels/sigcore) 46 | 47 | ## SIG members 48 | 49 | * [Andrew Lukoshko](mailto:alukoshko@almalinux.org) - The AlmaLinux OS Lead Architect. 50 | * Chat login: [alukoshko](https://chat.almalinux.org/almalinux/messages/@alukoshko) 51 | * GitHub profile: [andrewlukoshko](https://github.com/andrewlukoshko) 52 | * [Jack Aboutboul](mailto:jack@almalinux.org) - The AlmaLinux OS community manager. 53 | * Chat login: [themayor](https://chat.almalinux.org/almalinux/messages/@themayor) 54 | * GitHub profile: [jaboutboul](https://github.com/jaboutboul) 55 | * [Eduard Abdullin](mailto:eabdullin@almalinux.org) - The release and automation engineer. 56 | * Chat login: [eabdullin](https://chat.almalinux.org/almalinux/messages/@eabdullin) 57 | * GitHub profile: [eabdullin1](https://github.com/eabdullin1) 58 | * [Stepan Oksanichenko](mailto:soksanichenko@cloudlinux.com) - The software developer and automation engineer. 59 | * Chat login: [stepan_oksanichenko](https://chat.almalinux.org/almalinux/messages/@stepan_oksanichenko) 60 | * GitHub profile: [soksanichenko](https://github.com/soksanichenko) 61 | * [Simon John](mailto:sjohn@almalinux.org) - Security Standards Architect. 62 | * Chat login: [sej7278](https://chat.almalinux.org/almalinux/messages/@sej7278) 63 | * GitHub profile: [sej7278](https://github.com/sej7278) 64 | -------------------------------------------------------------------------------- /docs/sigs/HPCandAI.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "HPC and AI SIG" 3 | --- 4 | # HPC and AI SIG 5 | 6 | AlmaLinux is the ideal Linux choice for HPC and AI applications, and the HPC and AI SIG is here to help you make the most of it. We are a group of HPC and AI experts who use AlmaLinux to power our projects and share our knowledge with the AlmaLinux community. We promote the benefits of AlmaLinux for HPC and AI, provide guidance and support for AlmaLinux users in HPC and AI, and represent the interests and needs of the HPC and AI community within AlmaLinux. Join us today and discover how AlmaLinux can boost your HPC and AI performance and productivity. 7 | 8 | ## How to Join 9 | 10 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 11 | 12 | **Where we chat** 13 | 14 | * [SIGHPCAI](https://chat.almalinux.org/almalinux/channels/sighpc--ai) on [chat.almalinux.org](https://chat.almalinux.org) 15 | * [HPC and AI on the AlmaLinux Forum](https://forums.almalinux.org/c/sigs/hpc/31) 16 | * [HPC and AI Mailing List](https://lists.almalinux.org/mailman3/lists/hpc-ai-sig.lists.almalinux.org/) 17 | 18 | **Where and when we meet** 19 | 20 | The HPC and AI SIG gathers quarterly as a group for open discussion. The HPC and AI SIG also occasionally presents on HPC and AI-related topics and hosts community gatherings at HPC and AI-related events. Quarterly meetings and other events are announced via the [HPC and AI Mailing List](https://lists.almalinux.org/mailman3/lists/hpc-ai-sig.lists.almalinux.org/). 21 | 22 | ## Activities, projects, and deliverables 23 | 24 | * AlmaLinux System Series guidance on deploying AlmaLinux in HPC and AI environments. 25 | * Example configuration files for deploying Slurm and other HPC software on AlmaLinux: [AlmaLinux/sig-hpcai](https://github.com/AlmaLinux/sig-HPCAI). 26 | 27 | ### Help wanted 28 | 29 | Contributions take all kinds of shapes and sizes, and we welcome everyone! If you have expertise or time and would like to help us out, we welcome contributions to our activities, projects, and deliverables above. We also welcome community members to present on topics related to their use of AlmaLinux for HPC or AI. 30 | 31 | ## SIG members 32 | 33 | * [Hayden Barnes](mailto:hayden.barnes@hpe.com) - Senior Open Source Community Manager for AI Software, [Determined AI](https://www.determined.ai/) and [Pachyderm](https://www.pachyderm.com/), [HPE](https://www.hpe.com/) 34 | * Chat login: [@hayden-barnes](https://chat.almalinux.org/almalinux/messages/@hayden-barnes) 35 | * GitHub profile: [sirredbeard](https://github.com/sirredbeard) 36 | * [Peter Grossoehme](mailto:peter.grossoehme@megware.com) - Chief Operating Officer, [MEGWARE](http://www.megware.com) 37 | * Chat login: [@peter.grossoehme](https://chat.almalinux.org/almalinux/messages/@peter.grossoehme) 38 | * [Markus Hilger](mailto:markus.hilger@megware.com), HPC Engineer, [MEGWARE](http://www.megware.com) 39 | * Chat login: [@markus.hilger](https://chat.almalinux.org/almalinux/messages/@markus.hilger) 40 | * GitHub profile: [Obihoernchen](https://github.com/Obihoernchen) 41 | * [Zacarias Benta](mailto:zacarias@lip.pt) - IT Engineer, [Laboratory of Instrumentation and Experimental Particle Physics (LIP)](https://ciencias.ulisboa.pt/en/lip) 42 | * Chat login: [@zacarias](https://chat.almalinux.org/almalinux/messages/@zacarias) 43 | * GitHub profile: [@zbenta](https://github.com/zbenta) 44 | 45 | ## Additional information for SIG application approval 46 | 47 | * We would like to hold our first quarterly meeting in April 2024. 48 | * We will require the creation of: 49 | * An HPC and AI SIG channel on chat.almalinux.org 50 | * An HPC and AI SIG mailing list 51 | * An HPC and AI SIG repo on GitHub 52 | * We do not anticipate any infrastructure or financial resources. 53 | -------------------------------------------------------------------------------- /docs/sigs/Infrastructure.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Infrastructure SIG" 3 | --- 4 | # Infrastructure SIG 5 | 6 | The infrastructure team is responsible for maintaining the servers and services that keep AlmaLinux online and accessible to end users. 7 | 8 | ## How to Join 9 | 10 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 11 | 12 | **Where we chat** 13 | 14 | The Infrastructure SIG uses the [Infrastructure](https://chat.almalinux.org/almalinux/channels/infrastructure) chat channel and the [Infrastructure mailing list](https://lists.almalinux.org/mailman3/lists/infra.lists.almalinux.org/) for communication. 15 | 16 | **Where and when we meet** 17 | 18 | We don't currently hold regular meetings, but work asynchronously in mattermost to accomplish our goals. 19 | 20 | ## Activities, projects, and deliverables 21 | 22 | * [Infrastructure Ansible Playbook](https://github.com/almalinux/infra-ansible) 23 | * Mirror infrastructure: [AlmaLinux/mirrors](https://github.com/AlmaLinux/mirrors) 24 | * Official mirrors: 25 | * Official rsync mirror: https://rsync.repo.almalinux.org 26 | * Azure Mirrors: 27 | [East US](https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/eastus.azure.repo.almalinux.org.yml), 28 | [West US](https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/westus2.azure.repo.almalinux.org.yml), 29 | [Southeast Asia](https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/southeastasia.azure.repo.almalinux.org.yml), 30 | [Germany West/Central](https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/germanywestcentral.azure.repo.almalinux.org.yml) 31 | * [AWS CloudFront Mirror](https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/aws.repo.almalinux.org.yml) 32 | * [repo.almalinux.org](https://github.com/AlmaLinux/mirrors/blob/master/mirrors.d/repo.almalinux.org.yml) 33 | * [AlmaLinux Account Services](https://accounts.almalinux.org) 34 | * [Mattermost Chat](https://chat.almalinux.org) 35 | * [Mailing Lists](https://lists.almalinux.org) 36 | * Infrastructure Monitoring System (Zabbix) 37 | * DNS 38 | * Servers/basic infrastructure for all other services including but not limited to: 39 | * [almalinux.org](https://almalinux.org) 40 | * [wiki](https://wiki.almalinux.org) 41 | * [git](https://git.almalinux.org) 42 | * [Package Evolution Service (PES)](https://pes.almalinux.org) 43 | * [Bug Reports](https://bugs.almalinux.org) 44 | 45 | 46 | ### Help wanted 47 | 48 | * Building Ansible playbooks for maintaining internal infrastructure: https://github.com/almalinux/infra-ansible 49 | * much, much more. 50 | 51 | If you would like to help, please join us at [Infrastructure channel](https://chat.almalinux.org/almalinux/channels/infrastructure) 52 | 53 | ## SIG members 54 | 55 | * [Jonathan Wright](mailto:jonathan@almalinux.org) - Infrastructure Team Lead. 56 | * Chat login: [jonathan](https://chat.almalinux.org/almalinux/messages/@jonathan) 57 | * GitHub profile: [jonathanspw](https://github.com/jonathanspw) 58 | * [Andrew Lukoshko](mailto:alukoshko@almalinux.org) - AlmaLinux OS Lead Architect. 59 | * Chat login: [alukoshko](https://chat.almalinux.org/almalinux/messages/@alukoshko) 60 | * GitHub profile: [andrewlukoshko](https://github.com/andrewlukoshko) 61 | * [Stepan Oksanichenko](mailto:soksanichenko@cloudlinux.com) - Package Evolution Service & Mirror Service Developer. 62 | * Chat login: [stepan_oksanichenko](https://chat.almalinux.org/almalinux/messages/@stepan_oksanichenko) 63 | * GitHub profile: [soksanichenko](https://github.com/soksanichenko) 64 | * [Elkhan Mammadli](mailto:elkhan@almalinux.org) - AlmaLinux OS Cloud Engineer, Cloud & Virt Team Lead. 65 | * Chat login: [lkhn](https://chat.almalinux.org/almalinux/messages/@lkhn) 66 | * GitHub profile: [LKHN](https://github.com/LKHN) 67 | * [Vasiliy Kleschov](mailto:vkleschov@almalinux.org) - Build System Team Lead. 68 | * Chat login: [korulag](https://chat.almalinux.org/almalinux/messages/@korulag) 69 | * GitHub profile: [Korulag](https://github.com/Korulag) 70 | * [Cody Robertson](mailto:crobertson@almalinux.org) 71 | * Chat login: [codyr](https://chat.almalinux.org/almalinux/messages/@codyr) 72 | * GitHub profile: [codyro](https://github.com/codyro) 73 | -------------------------------------------------------------------------------- /docs/sigs/LiveMedia.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Live Media SIG" 3 | --- 4 | # Live Media SIG 5 | 6 | The Live Media Team is responsible for AlmaLinux OS Live Media. 7 | 8 | ## How to Join 9 | 10 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 11 | 12 | **Where we chat** 13 | 14 | The Live Media SIG uses the [SIG/LiveMedia](https://chat.almalinux.org/almalinux/channels/siglivemedia) chat channel for communication. 15 | 16 | **Where and when we meet** 17 | 18 | We do not currently hold regular meetings, but work asynchronously in mattermost to accomplish our goals. 19 | 20 | ## Activities, projects, and deliverables 21 | 22 | * ISO images download link: [repo.almalinux.org/almalinux/8/live/x86_64](https://repo.almalinux.org/almalinux/8/live/x86_64/). 23 | * Build scripts and configuration files: [AlmaLinux/sig-livemedia](https://github.com/AlmaLinux/sig-livemedia). 24 | 25 | ### Help wanted 26 | 27 | * Technical writers for working on documentation. 28 | * Design and automate test scenarios. 29 | 30 | If you can help, please join us at [Live Media SIG on Mattermost](https://chat.almalinux.org/almalinux/channels/siglivemedia) 31 | 32 | ## SIG members 33 | 34 | * [Eduard Abdullin](mailto:eabdullin@almalinux.org) - Works on Live Media build scripts and configuration files. 35 | * Chat login: [eabdullin](https://chat.almalinux.org/almalinux/messages/@eabdullin) 36 | * GitHub profile: [eabdullin1](https://github.com/eabdullin1) 37 | * [Elkhan Mammadli](mailto:elkhan.mammadli@protonmail.com) - Works on Live Media build scripts and automation. 38 | * Chat login: [lkhn](https://chat.almalinux.org/almalinux/messages/@lkhn) 39 | * GitHub profile: [LKHN](https://github.com/LKHN) 40 | * [Yuriy Kohut](mailto:ykohut@almalinux.org) - Works on Live Media build scripts and configuration files. 41 | * Chat login: [ykohut](https://chat.almalinux.org/almalinux/messages/@ykohut) 42 | * GitHub profile: [yuravk](https://github.com/yuravk) 43 | * [Andrew Lukoshko](mailto:alukoshko@almalinux.org) - The AlmaLinux OS Lead Architect. 44 | * Chat login: [alukoshko](https://chat.almalinux.org/almalinux/messages/@alukoshko) 45 | * GitHub profile: [andrewlukoshko](https://github.com/andrewlukoshko) 46 | -------------------------------------------------------------------------------- /docs/sigs/Marketing.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Marketing SIG" 3 | --- 4 | # Marketing SIG 5 | 6 | The Marketing team is responsible for AlmaLinux marketing and outreach efforts. Marketing is often an overlooked or eschewed term in open source, but without marketing efforts it's a whole lot harder for your audience to find you. We try to make it easy for the users who need a free enterprise linux distribution to find us. 7 | 8 | ## How to Join 9 | 10 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 11 | 12 | **Where we chat** 13 | 14 | We use the [~Marketing](https://chat.almalinux.org/almalinux/channels/marketing) channel for communication on the AlmaLinux mattermost server. 15 | 16 | **Where/how we meet** 17 | 18 | Meetings are every other Thursday on Google Meet at 9pm UTC. Join the Marketing channel on [chat.almalinux.org](https://chat.almalinux.org/almalinux/channels/marketing) and ask benny for the meeting invite! Our meeting notes are kept in [Google drive](https://docs.google.com/document/d/1OK8mQSU-EucCT-VdFVOd87BECmVSXIKXkG7uhLubs9o/edit#heading=h.9ynhotw081jk). 19 | 20 | ## Activities, projects, and deliverables 21 | 22 | Properties that we are responsible for: 23 | 24 | * [almalinux.org](https://almalinux.org) 25 | * [shop.almalinux.org](https://shop.almalinux.org) 26 | * [events.almalinux.org](https://events.almalinux.org) 27 | 28 | We also provide content for other properties as needed by other SIGs. 29 | 30 | Other efforts that we manage: 31 | 32 | * Event plans 33 | * Outreach efforts 34 | * Social media management 35 | * Press efforts 36 | 37 | ### Help wanted 38 | 39 | Contributions take all kinds of shapes and sizes, and we welcome everyone! If you have expertise or time and would like to help us out, here are a few things that need help soon, and a place where you can find more information. 40 | 41 | * Mastodon automation - we use Sprout Social for scheduling ahead of time right now, but it doesn't work with mastodon! 42 | * Event management and staffing -- help us expand the number of events we can join by helping us staff events local to you! 43 | * Content writers -- especially for the blog and social media 44 | * Website maintainers -- our Hugo migration is complete, but we need to clean it up 45 | * Graphic designers -- we have sticker ideas, but they aren't nearly as pretty as they could be! 46 | * Website translations -- accepted through [Weblate](https://hosted.weblate.org/projects/almalinux/website-backend/), automatically sent to the website repo for merging in. To contribute, take a look at the ["Help translating site"](/Help-translating-site.html) guide. 47 | 48 | We have tons of ideas and bugs on the [website repo](https://github.com/AlmaLinux/almalinux.org) and on [GitHub Projects](https://github.com/orgs/AlmaLinux/projects/5/views/1). 49 | 50 | ## SIG members 51 | 52 | These members share responsibilities between and among each other. 53 | 54 | * [benny Vasquez](mailto:benny@almalinux.org) - SIG leader 55 | * [Jack Aboutboul](mailto:jack@almalinux.org) - Member 56 | * [Jonathan Wright](mailto:jonathan@almalinux.org) - Member 57 | * [Cody Robertson](mailto:crobertson@almalinux.org) - Member 58 | 59 | We also have a variety of folks who help us with PR, social media, and website maintenance through submissions to chat or just PRs to the [website repo](https://github.com/AlmaLinux/almalinux.org). 60 | 61 | # Marketing accounts 62 | 63 | Here is where we track the different accounts that marketing uses, and who has admin rights for them. 64 | 65 | ### Various marketing-adjacent accounts 66 | 67 | * [Canva](https://canva.com) - we have a free Pro teams account - benny has admin/owner rights 68 | 69 | ### Social Media Accounts 70 | 71 | We currently have a number of social media accounts that are managed by the SIG members. 72 | 73 | #### Active accounts 74 | 75 | These accounts are actively monitored, updated, and managed by the SIG on a regular basis. 76 | 77 | * [Mastodon (on fosstodon.org)](https://fosstodon.org/@almalinux) - password in Vaultwarden 78 | * [Twitter (x)](https://twitter.com/almalinux) - password in Vaultwarden 79 | * [Facebook](https://www.facebook.com/AlmaLinux/) - password in Vaultwarden 80 | * [LinkedIn](https://www.linkedin.com/company/almalinuxos/) - benny and Jack have 'owner' rights 81 | 82 | #### Inactive (placeholder) accounts 83 | 84 | These accounts are only in place to keep the name owned by us, and to point folks to our active accounts. 85 | 86 | * [Youtube](https://www.youtube.com/@almalinux6891) - benny and Jack have 'owner' rights 87 | * [BlueSky](bsky.app/almalinux) - password in Vaultwarden 88 | -------------------------------------------------------------------------------- /docs/sigs/Migration.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Migration SIG" 3 | --- 4 | 5 | ###### last updated: 2024-04-22 6 | 7 | # Migration SIG 8 | 9 | The Migration team is responsible for two migration projects - the migration tool and the ELevate project, including documentation and upgrades. See the [Migration](/migration/) section for more details. 10 | 11 | ### AlmaLinux Migration Tool 12 | 13 | The [migration tool](/documentation/migration-guide) is used to convert an EL8 or EL9 machine. 14 | 15 | The tool supports the following migration paths: 16 | 17 | ![image](/images/migration.svg) 18 | 19 | ### AlmaLinux ELevate project. 20 | 21 | The ELevate project is an initiative to support migrations between major versions of RHEL-derivatives. See the [ELevate](/elevate/) section for more details and the update steps. 22 | 23 | The project supports the following migration paths: 24 | 25 | ![image](/images/ELevate.svg) 26 | 27 | \* - migration to CentOS Stream 9 is currently in process and will be available later.
28 | \** - migration to Oracle Linux 9 is available with the [Oracle Leapp utility](https://blogs.oracle.com/linux/post/upgrade-oracle-linux-8-to-oracle-linux-9-using-leapp) and will not be supported by ELevate project. 29 | 30 | ## How to Join 31 | 32 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 33 | 34 | **Where we chat** 35 | 36 | The Migration SIG uses the [SIG/Migration](https://chat.almalinux.org/almalinux/channels/migration) chat channel for communication. 37 | 38 | **Where and when we meet** 39 | 40 | We do not currently hold regular meetings, but work asynchronously in mattermost to accomplish our goals. 41 | 42 | ## Activities, projects, and deliverables 43 | 44 | * AlmaLinux Leapp patches at: [AlmaLinux/leapp-repository](https://github.com/AlmaLinux/leapp-repository/tree/almalinux). Consider this is not a separated forked project. 45 | * Static data files for Leapp utility: [AlmaLinux/leapp-data](https://github.com/AlmaLinux/leapp-data) 46 | * CentOS 6 to CentOS 7 upgrade tool: [AlmaLinux/redhat-upgrade-tool](https://github.com/AlmaLinux/redhat-upgrade-tool). 47 | 48 | ### Help wanted 49 | 50 | * Adding more 3rd party repositories support 51 | * Testing various configurations 52 | * Developing scripts for populating unsupported kernel modules and pci ids lists 53 | * Feedback and bug reports 54 | 55 | If you can help, please join us at [Migration SIG on Mattermost](https://chat.almalinux.org/almalinux/channels/migration). 56 | 57 | ## SIG members 58 | 59 | * [Stepan Oksanichenko](mailto:soksanichenko@cloudlinux.com) - Package Evolution Service developer. 60 | * Chat login: [stepan_oksanichenko](https://chat.almalinux.org/almalinux/messages/@stepan_oksanichenko) 61 | * GitHub profile: [soksanichenko](https://github.com/soksanichenko) 62 | * [Yuriy Kohut](mailto:ykohut@almalinux.org) - ELevate Project engineer. 63 | * Chat login: [ykohut](https://chat.almalinux.org/almalinux/messages/@ykohut) 64 | * GitHub profile: [yuravk](https://github.com/yuravk) 65 | * [Andrew Lukoshko](mailto:alukoshko@almalinux.org) - The AlmaLinux OS Lead Architect. 66 | * Chat login: [alukoshko](https://chat.almalinux.org/almalinux/messages/@alukoshko) 67 | * GitHub profile: [andrewlukoshko](https://github.com/andrewlukoshko) 68 | -------------------------------------------------------------------------------- /docs/sigs/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Special interest groups" 3 | --- 4 | 5 | # Special interest groups 6 | 7 | Special interest groups (SIGs) are teams within the AlmaLinux OS community that are focused on specific topics. Each SIG has its own channel on our [Mattermost](https://mattermost.com/) chat server [chat.almalinux.org](https://chat.almalinux.org/), but may communicate and work in different ways. Each SIG's details are found in the pages below. 8 | 9 | The following SIGs are already established: 10 | 11 | * [Atomic](/sigs/Atomic) - The AlmaLinux Atomic SIG 12 | * [Build System](/sigs/Build-System) - The AlmaLinux OS build system developers and maintainers. 13 | * [Certification](/sigs/Certification) - The AlmaLinux Certification SIG. 14 | * [Core](/sigs/Core) - The AlmaLinux OS distribution developers and maintainers. 15 | * [Cloud](/sigs/Cloud) - The AlmaLinux OS cloud and container images maintainers. 16 | * [HPC and AI](/sigs/HPCandAI) - The AlmaLinux High performance computing and AI SIG. 17 | * [Infrastructure](/sigs/Infrastructure) - The AlmaLinux OS infrastructure team. 18 | * [Live Media](/sigs/LiveMedia) - The AlmaLinux OS Live Media maintainers. 19 | * [Migration](/sigs/Migration) - The AlmaLinux OS Migration maintainers. 20 | * [Marketing](/sigs/Marketing) - The AlmaLinux OS Marketing SIG. 21 | 22 | 23 | # Additional Resources 24 | 25 | * [Community funding request form](https://forms.gle/tpoJUKPLGy3tY3DH9) 26 | This forms is for members of the AlmaLinux community to request specific hardware or software to support the work they're doing for the AlmaLinux project. 27 | * [Process For Creating New SIG](/sigs/ProcessForCreatingNewSIG) - AlmaLinux OS Foundation SIG Lifecycle Guidelines 28 | -------------------------------------------------------------------------------- /docs/sigs/marketing/indico.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'Managing events.almalinux.org' 3 | --- 4 | 5 | # Managing events.almalinux.org 6 | 7 | ###### last updated: May 8, 2024 8 | 9 | Our events are managed using [Indico](https://getindico.io/), the open source software created and developed at CERN. Our install, at [events.almalinux.org](https://events.almalinux.org) (documentation at [learn.getindico.io](https://learn.getindico.io/)), is kept up to date by the AlmaLinux Infra SIG, but events on it are managed by the marketing SIG. This document helps us consistently create new events to the community. 10 | 11 | # Creating different events 12 | 13 | When creating different types of events, it's important that you follow the directions below so that our community can count on events being presented in a consistent way. 14 | 15 | All events should start as unlisted events to be published after they're reviewed by the marketing SIG chair. 16 | 17 | ## Webinars 18 | 19 | 1. Navigate to the Webinars event group. 20 | 1. Create a '**Lecture**' type event from the top of the page. 21 | 1. Enter the title of the webinar, ensure the time and date are correct, and click 'Advanced' to add a description. 22 | 1. If you need to edit the event after it's created, you can. 23 | 1. Add speakers - you will have to manually enter anyone who is not already registered in Indico. (note for benny: if they register later, what happens?) 24 | 25 | After it's created, there are some more adjustments to make: 26 | 27 | 1. under **Protection**, enable public registration and click *Save* 28 | 1. under **Organisation - > Participants** set the visibility to the default of "Show only consenting participants" and click save, so that the registration form will be displayed. 29 | 1. If you're opening registration immediately, make sure you click *Start now* to open registrations. 30 | 1. Edit the form as needed by clicking *Configure* next to 'Registration Form' 31 | 1. under **Organisation - > Reminders** add a reminder relative to the event start time at 1 hour offset from the event, sent to all participants and all speakers, sent from 'noreply@almalinux.org', including the event description and a link to where the webinar will be hosted. 32 | 33 | 34 | ## SIG meetings 35 | 36 | 1. Navigate to to the [SIGs category](https://events.almalinux.org/category/1/manage/), and choose the appropriate category there for the specific SIG. 37 | 1. Create a **meeting** event, naming it appropriately for the SIG using [$freqency - $signame meeting] as the pattern (for example, Bi-weekly Marketing SIG meeting). 38 | 1. Once created, on the default settings page update the **Contact title** and **Email** to match the SIG in question's contact details. 39 | 1. Under **Timetable* click *Add new* and *Contribution* 40 | 1. use the same title as for the full event, in the description add details about the event (general agenda, where they meet, and where to get the meeting link at least). 41 | 1. Put in the time of the meeting. 42 | 1. No speakers should be set for these meetings. 43 | 44 | Leave the rest of it blank. 45 | 46 | If a schedule is set for meetings already, clone the meeting you just created to make more of them. If not, you can clone older events to set up new meetings as we move forward. 47 | 48 | ## SIG Categories 49 | 50 | 1. Navigate in the admin interface to the [SIG category](https://events.almalinux.org/category/1/manage/) 51 | 1. Ensure the name of the category includes the name of the SIG and the word SIG 52 | 1. Use this template as the description: 53 | > These meetings are held every week via $platform. If you'd like the meeting link, join the $channelname channel on chat.almalinux.org. 54 | > For more information on this SIG, see the details on the AlmaLinux Wiki: $wikipage 55 | 1. Set the **"Theme for Lectures"** to lectures, and the **"Theme for Meetings"** to *Indico style*. 56 | 1. Add an icon and SIG logo created using the [Canva template](https://www.canva.com/design/DAGEBQ_hwpk/meDfUVoUTVoyYIY1-hXaJA/edit). -------------------------------------------------------------------------------- /docs/sigs/sigproposaltemplate.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "name of SIG" 3 | --- 4 | # name of SIG 5 | 6 | [insert the SIG's purpose here] 7 | 8 | ## How to Join 9 | 10 | Joining is easy! You can show up to a meeting, pick up an issue from the list by assigning it to yourself, or ask questions in chat! Not every contributor wants to be a part of the SIG, but if you do, joining is simple. 11 | 12 | **Where we chat** 13 | 14 | We use $platform for communication. [ this should either be a link to the SIG chat room on mattermost, or the mailing list on lists.almalinux.org ] 15 | 16 | **Where and when we meet** 17 | 18 | Meetings are... [ this should be a general day/time/cadence, and indicate how one might join this meeting if they'd like, or use "We do not currently hold regular meetings, but work asynchronously in mattermost to accomplish our goals." ] 19 | 20 | ## Activities, projects, and deliverables 21 | 22 | [ this should be the thing or list of things you expect to be responsible for ] 23 | 24 | ### Help wanted 25 | 26 | Contributions take all kinds of shapes and sizes, and we welcome everyone! If you have expertise or time and would like to help us out, here are a few things that need help soon, and a place where you can find more information. 27 | 28 | [ either a list of things or a link to a project/task tracker should go here ] 29 | 30 | ## SIG members 31 | 32 | * [name](either email address or mattermost chat link) - SIG lead 33 | * [name](either email address or mattermost chat link) - member 34 | 35 | (you can also include additional information about other folks that help your SIG or are involved in some way here) 36 | 37 | ## Additional information for SIG application approval 38 | 39 | * Timeline for when you would like to get things rolling for this group, and how quickly you expect to see motion on your Activities, projects, and deliverables. 40 | * Any known resources (monetary or infrastructure) that you anticipate needing, and how they will be used. 41 | 42 | [ You can add anything additional you feel is important here as well ] 43 | -------------------------------------------------------------------------------- /images/hero.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AlmaLinux/wiki/8d605ab4a7f311f7996b8da73636efbdce04c268/images/hero.png -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "wiki.almalinux.org", 3 | "version": "0.1.0", 4 | "main": "index.js", 5 | "scripts": { 6 | "docs:dev": "vuepress dev docs", 7 | "docs:build": "vuepress build docs" 8 | }, 9 | "devDependencies": { 10 | "vuepress": "^1.9.9" 11 | } 12 | } 13 | --------------------------------------------------------------------------------