Fedora Leftovers

posted by Roy Schestowitz on Feb 18, 2023

• Tomasz Torcz: Migrated home server to the UEFI boot

  I've migrated my home server to boot using UEFI. It means suprising number of things:

  • I did something useful during my unplanned PTO days [...]

  • [...]I can unsubscribe from BIOS Boot SIG, as this was my last legacy-booting computer. The SIG mailing list is completely empty, apparently all the ruckus with needing BIOS booting within Fedora has no real standing.

• Fedora Community Blog: CPE Weekly Update – Week 7 2023

  This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat.

  We provide you both infographics and text versions of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details look at the infographic.

• Fedora Community Blog: Friday’s Fedora Facts: 2023-07

  Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)!

  I have weekly office hours most Wednesdays in the morning and afternoon (US/Eastern time). Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

• Fedora Magazine: Working with Btrfs – Compression

  This article will explore transparent filesystem compression in Btrfs and how it can help with saving storage space. This is part of a series that takes a closer look at Btrfs, the default filesystem for Fedora Workstation, and Fedora Silverblue since Fedora Linux 33.

  In case you missed it, here’s the previous article from this series: https://fedoramagazine.org/working-with-btrfs-snapshots

  [...]

  • Not all files compress equally well. Modern multimedia formats such as images or movies compress their contents already and don’t compress well beyond that.
  • The script performs each compression and decompression exactly once. Running it repeatedly on the same input file will generate slightly different outputs. Hence, the times should be understood as estimates, rather than an exact measurement.

  Given the numbers in my output, I decided to use the zstd compression algorithm with compression level 3 on my systems. Depending on your needs, you may want to choose higher compression levels (for example, if your storage devices are comparatively slow). To get an estimate of the achievable read/write speeds, you can divide the source archives size (about 260 MB) by the (de)compression times.

  [...]

  Conclusion

  This article detailed transparent filesystem compression in Btrfs. It is a built-in, comparatively cheap, way to get some extra storage space out of existing hardware without needing modifications.