brandon/oam
1
0
Fork 0
mirror of https://gitea.com/mcereda/oam.git synced 2026-02-09 05:44:23 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
7c72e4e5fb5bacefb9678e414b5b6a805a8c26ae
oam/knowledge base/fedora linux.md
Michele Cereda ebb4e5febb chore: aligned docs to the template file for articles
2023-07-09 18:17:32 +02:00

2.4 KiB
Raw Blame History

Fedora GNU/Linux

Table of contents

  1. Enable the RPM Fusion repositories
  2. Broadcom Wi-Fi drivers
  3. Enable ZFS management
  4. Use DNF from behind a proxy
  5. Sources

Enable the RPM Fusion repositories

RPM Fusion provides software that the Fedora Project or Red Hat doesn't want to ship. That software is provided as precompiled RPMs for all current Fedora versions and current Red Hat Enterprise Linux or clones versions; you can use the RPM Fusion repositories with tools like yum and PackageKit.

These repositories are not available by default and need to be installed using a remote package:

# All flavours but Silverblue-based ones.
sudo dnf install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm

# Silverblue-base flavours.
sudo rpm-ostree install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm

After enabling the repositories, you can add their tainted versions for closed or restricted packages:

sudo dnf install rpmfusion-{free,nonfree}-release-tainted
sudo rpm-ostree install rpmfusion-{free,nonfree}-release-tainted

Broadcom Wi-Fi drivers

After enabling the normal and tainted RPM fusion repositores, just install the b43-firmware package.

Enable ZFS management

sudo dnf install http://download.zfsonlinux.org/fedora/zfs-release$(rpm -E %dist).noarch.rpm
sudo dnf install kernel-devel zfs
sudo systemctl start zfs-fuse.service
sudo zpool import -a

Use DNF from behind a proxy

Either:

  • add the line sslverify=0 to /etc/dnf/dnf.conf; not suggested, but a quick fix
  • add the proxie's certificate, in PEM format, to the /etc/pki/ca-trust/source/anchors/ folder and then run sudo update-ca-trust.

Sources