We will be updating and rebooting servers to pick up the recent RHEL 9.5 release as well as to move a number of instances to Fedora 41
This outage impacts the most maintainer / contributor services for some short windows during the outage.
admin )
on 2024-11-20 21:00:00 UTC
We will be updating and rebooting servers to pick up the recent RHEL 9.5 release as well as to move a number of instances to Fedora 41
This outage impacts the most maintainer / contributor services for some short windows during the outage.
admin )
on 2024-11-20 19:34:29 UTC
You attended the F41 Online Release Watch Party!
Country-code top level domains (ccTLDs) were intended to provide domains for countries, as the name implies. But they aren’t always used for that. Sometimes they’re used as auxiliary domains: Twitter used t.co and LinkedIn used lnkd.in for shortened links in posts. Sometimes they indicate some kind of affinity: many tech websites use .io or .sh. Sometimes they’re used for humor: the queer.af Mastodon server was presumably queer as fuck. So as you figure out the best domain name for your project, should you use a ccTLD? Absolutely not!
Why? Well, the queer.af domain was shut down by the Taliban. .io should be discontinued. Tokelau’s .tk TLD became a haven for cybercriminals. Do you want to put your project’s domain in the hands of geopolitics? Or participate in what some have called digital colonialism?
With the expansion of the generic top-level domain space in 2014, there’s even less reason to use a ccTLD for your project. It’s why this site is duckalignment.academy instead of duckalignmentacade.my (not to mention the fact that my representation of Malaysia at a Model UN conference in 1999 is probably not sufficient to convince Malaysia’s registrar to give it to me).
But what if it’s too late and you’re already using a ccTLD? You probably don’t want to make a hard cutover tomorrow. This will result in a lot of broken links. If your project hosts infrastructure (like a package repository) or provides a service to users, it will result in broken applications. Using a ccTLD poses a risk that you need to manage. (See chapter 1 of Program Management for Open Source Projects for more on risk management.)
At a minimum, you should have a plan for what to do if your domain becomes unusable. But because the disruption can come quickly and take a while to fully resolve, it’s probably best if you secure a new domain now and start taking steps to migrate.
This post’s featured photo by Christian Lue on Unsplash.
The post ccTLDs are bad for your project appeared first on Duck Alignment Academy.
czanik )
on 2024-11-20 12:57:48 UTC
The official syslog-ng container image is based on Debian Stable. However, we’ve been getting requests for an RPM-based image for many years. So, I made an initial version available based on Alma Linux and now I need your feedback about it! This image uses the “init” variant of Alma Linux 9 containers as a base image. What does this mean? Well, it uses systemd service management inside, making it possible to run multiple services from a single container. While only syslog-ng is included right now, I also plan to add the syslog-ng Prometheus exporter to the image. Note that while the example command lines show Docker, I also tested it using Podman.
Read more at: https://www.syslog-ng.com/community/b/blog/posts/experimental-syslog-ng-container-image-based-on-alma-linux
admin )
on 2024-11-18 15:08:00 UTC
Welcome to the Fedora Operations Report and I hope everyone is enjoying the latest Fedora Linux release! Read on to find out more information such as important upcoming dates for F42, and a few tidbits of things happening around the project lately 
Fedora Linux 41 is here! Get the latest version of our operating system from the website and read about some of the new features you can enjoy from the Fedora magazine.
As we now have F41, that means we will have to say goodbye to F39. This release will go end of life on November 26th 2024. All bugzillas open against this release will be automatically closed.
Also with the advent of F41, that means we will now have some new elections! We will have elections in FESCo and Mindshare, and from now until 27th November – Nominations are open! Please feel free to nominate yourself, or someone you know (with their permission) who would be a great fit, and able to volunteer for 12 months. We have five seats up for election in FESCo, and one seat up for election in the Mindshare Committee.
As a reminder, the Fedora Council has moved to a once per year election, so there will be no elective seats open in Council in this cycle. The next election cycle will be post F42 release. Similarly, the EPEL Steering Committee holds elections once per year also in May, and seats on this committee come up for election on a voluntary basis.
Fedora Linux 42 is currently in development, and for the most recent set of changes planned in this release, please refer to our change set page. Our release schedule is also live, and a reminder of some key dates are below:
The changes that are currently in our community feedback period are :
For all the latest on boot-c, check out the latest bootc phttps://discussion.fedoraproject.org/t/bootc-this-week-2024-11-15/136985ost on discourse!
Our Git Forge evaluation is still active, with details of how to get access to either the GitLab or Forgejo instance can be found on this discussion thread.
The request to grant KDE Desktop Spin edition status has been approved! Congratulations to the folks involved in the KDE SIG and we look forward to seeing this option as an official edition for Fedora in the near future!
FOSDEM 2025 returns on Saturday 1st and Sunday 2nd February and the cfp is now open.
CentOS Connect also returns to Brussels on 30th and 31st January 2025. For more information on cfps and to register for the event, check out the event page.
Do you have an idea for an episode of the Fedora Podcast, or want to see what some of the upcoming episodes will be? Bookmark The IT Guy’s discussion post on planning for the podcast!
Did you know there are EPEL Office Hours? If not, check out the details on how to join and when they happen on the announcement post!
Missed the Fedora Linux 41 release watch parties? Never fear! All talks are now available on the Fedora Youtube Channel in the ‘latest’ video tab. Happy Streaming!
The post Fedora Operations Architect Report appeared first on Fedora Community Blog.
ankursinha )
on 2024-11-18 09:56:35 UTC
Photo by William White on Unsplash.
Please join us at the next regular Open NeuroFedora team meeting on Monday 02 December at 1300 UTC. The meeting is a public meeting, and open for everyone to attend. You can join us in the Fedora meeting channel on chat.fedoraproject.org (our Matrix instance). Note that you can also access this channel from other Matrix home severs, so you do not have to create a Fedora account just to attend the meeting.
You can use this link to convert the meeting time to your local time. Or, you can also use this command in the terminal:
$ date -d 'Monday, December 02, 2024 13:00 UTC'
The meeting will be chaired by @ankursinha. The agenda for the meeting is:
We hope to see you there!
ankursinha )
on 2024-11-18 09:54:44 UTC
Photo by William White on Unsplash.
Please join us at the next regular Open NeuroFedora team meeting on Monday 18 November at 1300 UTC. The meeting is a public meeting, and open for everyone to attend. You can join us in the Fedora meeting channel on chat.fedoraproject.org (our Matrix instance). Note that you can also access this channel from other Matrix home severs, so you do not have to create a Fedora account just to attend the meeting.
You can use this link to convert the meeting time to your local time. Or, you can also use this command in the terminal:
$ date -d 'Monday, November 18, 2024 13:00 UTC'
The meeting will be chaired by @ankursinha. The agenda for the meeting is:
We hope to see you there!
This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of Q3 2024. As these teams are working closely together, we will summarize the work done in one blog post by both teams.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
Purpose of these teams is to take care of day-to-day business regarding Fedora Infrastructure and Fedora Release Engineering work. It’s responsible for developing and maintaining services running in Fedora and preparing things for the new Fedora Linux release (mirrors, mass branching, new namespaces etc.).
Issue trackers
The post Infra & Releng Update Q3 2024 appeared first on Fedora Community Blog.
admin )
on 2024-11-15 16:46:32 UTC
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version 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 below the infographic.
Week: 11 – 15 November 2024
The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
The post Infra and RelEng Update – Week 46 2024 appeared first on Fedora Community Blog.
This is a summary of the work done on initiatives by the CPE Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives + day-to-day work that needs to be done. Some of the sub-teams are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
The Community Platform Engineering Team is a Red Hat team that is working exclusively on community projects. Its members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure teams. This team works on initiatives, which are projects with larger scope related to community work that needs to be done. It also investigates possible initiatives with the ARC (The Advance Reconnaissance Crew), which is formed from a subset of the Infrastructure & Release Engineering sub-team members based on the initiative that is being investigated.
Issue trackers
PDC is the Product Definition Center, running at: https://pdc.fedoraproject.org/.
However, this application which was developed internally, is no longer maintained. This codebase has been “orphaned” for a few years now and we need to find a solution for it.
We are reviewing and having a critical look on what we store in there, see what is really needed and then find a solution for its replacement.
Status: Done
Issue trackers
Documentation
Application URLs
In the last quarter of 2021, a mini-initiative was completed that finished and deployed the discourse2fedmsg application. In short, this application is a simple flask app that receives POST requests from discourse (i.e. “webhooks”) and turns them into Fedora Messages, and then sends them through to the Fedora Messaging Queue.
Webhooks are a fairly common feature in current web applications, so this proposal is to create a new web application that can reuse common parts of discourse2fedmsg and set it up to be extended to send messages from other webhook enabled apps.
This would allow us to easily add support for apps like gitlab without having to deploy and create additional flask applications for each app that gets added in the future,
Status: In Progress
Issue trackers
Documentation
This investigation is looking at the potential replacement of dist git used by Fedora and what forge would be the best candidate. It’s looking at the user stories for current dist git and if it’s possible to apply them on Forgejo or GitLab.
Status: In Progress
Documentation
If you get here, thank you for reading this. If you want to contact us, feel free to do it on Matrix.
As CPE members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure, I’m adding here links to Fedora Infra & Releng update and CentOS Infrastructure update.
The post CPE Update Q3 2024 appeared first on Fedora Community Blog.
admin )
on 2024-11-14 19:01:13 UTC
Date: Fri, Nov. 15th, 2024, three time slots to connect our global community
Register and RSVP here:
With Fedora’s tradition of celebrating each release, we’re thrilled to introduce a more inclusive format this time around: Fedora Global Watch Parties. Instead of a single release party event, Fedora’s Global Watch Parties create three time slots across APAC, EMEA, and LATAM/NA, making it easier for everyone to participate in a way that fits their schedule and time zone.
Each Watch Party is designed to be easy to join, running around 1.5 hours. This shorter format means that more Fedora users, contributors, and community members can attend, connect, and engage. It’s a perfect opportunity to meet other Fedora community members, learn more about Fedora 41, and share the excitement of the release—no matter where you are.
With the change to holding sessions across three different time zones, we’re making it easier than ever for contributors and users worldwide to attend and participate. Whether you’re joining to learn about Fedora 41’s features or to connect with others who share your passion for open-source, we want to bring our community closer together.
Pick the time slot that works best for you, grab your Fedora swag, and join us for our Fedora 41 release event. See you there!
The post Announcing the Fedora 41 Global Watch Parties appeared first on Fedora Community Blog.
rajeeshknambiar )
on 2024-11-14 12:21:29 UTC
At the International TeX Users Group Conference 2023 (TUG23) in Bonn, Germany, I presented a talk about using Metafont (and its extension Metapost) to develop traditional orthography Malayalam fonts, on behalf of C.V. Radhakrishnan and K.H. Hussain, who were the co-developers and authors. And I forgot to post about it afterwards — as always, life gets in between.
In early 2022, CVR started toying with Metafont to create a few complicated letters of Malayalam script and he showed us a wonderful demonstration that piqued many of our interest. With the same code base, by adjusting the parameters, different variations of the glyphs can be generated, as seen in a screenshot of that demonstration: 16 variations of the same character ഴ generated from same Metafont source.
Hussain, quickly realizing that the characters could be programmatically assembled from a set of base/repeating components, collated an excellent list of basic shapes for Malayalam script.
I bought a copy of ‘The Metafontbook’ and started learning and experimenting. We found soon that Metafont, developed by Prof. Knuth in the late 1970’s, generates bitmap/raster output; but its extension MetaPost, developed by his Ph.D. student John Hobby, generates vector output (postscript) which is required for opentype fonts. We also found that ‘Metatype1’ developed by Bogusław Jackowski et al. has very useful macros and ideas.
We had a lot of fun programmatically generating the character components and assembling them, splicing them, sometimes cutting them short, and transforming them in all useful manner. I have developed a new set of tools to generate the font from the vector output (SVG files) generated by MetaPost, which is also used in later projects like Chingam font.
At the annual TUG conference 2023 in Bonn, Germany, I have presented our work, and we received good feedback. There were three presentations about Metafont itself at the conference. Among others, I also had the pleasure to meet Linus Romer who shared some ideas about designing variable width reph-shapes for Malayalam characters.
The video of the presentation is available in YouTube.
The article was published in the TUGboat conference proceedings (volume 44): https://www.tug.org/TUGboat/tb44-2/tb137radhakrishnan-malayalam.pdf
Postscript (no pun intended): after the conference, I visited some of my good friends in Belgium and Netherlands. En route, my backpack with passport, identity cards, laptop, a phone and money etc. was stolen at Liège. I can’t thank enough my friends at Belgium and back at home for their unbridled care, support and help, on the face of a terrible affliction. On the day before my return, the stolen backpack with everything except the money was found by the railway authorities and I was able to claim it just in time.
I made yet another visit to the magnificent Plantin–Moretus Museum (it holds the original Garamond types!), where I myself could ink and print a metal typeset block of sonnet by Christoph Plantijn in 1575, which now hangs at the office of a good friend.
czanik )
on 2024-11-14 12:03:14 UTC
The November syslog-ng newsletter is now on-line:
It is available at https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2024-11-testing-quickwit-macports
bcotton )
on 2024-11-13 13:00:00 UTC
The 2024 Tidelift State of the Open Source Maintainer Report is full of interesting survey results and analysis, but one paragraph stood out to me in particular. One unidentified maintainer, speaking about the impact of the xz social engineering attack said this:
This incident really highlighted for me that technology is not the problem—culture is. Without authentic, trustworthy support from a real community (not merely an accidental collection of strangers who have a single common interest) this kind of thing will only continue. Security is a wetware problem first and foremost—we need to care about actual, living humans, not just certs and hashes and chains of custody.
Too often, we assume a community will naturally form around a useful thing that people care about. If we build it, they will come. That’s not true. It is true that useful and interesting projects can spontaneously collect a group of users and maybe even contributors, that doesn’t make it a community.
A community is more than a collection of individuals with a common interest; a community is a collection of individuals with a common interest and a shared sense of ownership. A community is a collection of friends (or at least acquaintances), not strangers. Not everyone who participates in a project is a part of the community.
My local baseball team is a good example. On any given night, you can expect to see 1,500–2,000 people in the stands. Some show up, root for the home team, and go home. Others show up, greet the staff by name, and make sure all of their trash gets picked up because “this is our stadium.” Neither is better; they’re just different.
To bring it back to open source projects: if you’re moderately successful, you’ll have both a community and a collection of strangers. They both help your projects, whether it’s by feedback/bug reports, code contribution, telling others about your project, or whatever else. But it’s the community that will be sustainable. Not only does community imply some degree of commitment to stick around for a while, but the bonds of friendship can make the project a more enjoyable place to be.
The post Communities aren’t an accidental collection of strangers with a common interest appeared first on Duck Alignment Academy.
Jesień Linuksowa (Linux Autumn) was held in Rybnik, Poland, October 25–27, 2024. This was the 20th occurrence of this conference organized by the Polish Linux Users Group. The presenters and audience are mostly local, with about 50 participants, but there are always some guests from neighbouring countries.
The talks this year covered the following topics, as well as other topics related to FOSS.
We also held a Fedora Linux 41 Release Party. This included a discussion of changes in the release and a cool demo of a Fedora Sway desktop.
Recordings from the talks (all in Polish) will be posted at a later point.
admin )
on 2024-11-13 08:00:00 UTC
We will switch authentication from OpenID to OIDC (OpenID Connect). There will be a short outage to do this.
admin )
on 2024-11-11 15:45:48 UTC
The Fedora Linux installer, Anaconda, has been around for 25 years!
While it’s been a reliable way to install Fedora Linux (and CentOS, RHEL, and others), many people — especially those new to Fedora — sometimes have issues with complexity and jargon.
We’re working on a major update for the way it looks and acts. Our new interface is designed to make installing Fedora Linux simpler and more user-friendly for everyone, especially newcomers.
Skip to the download instructions to try it out or read on to learn about the background of the changes and to see screenshots.
The Anaconda team implemented the current design of the GTK-based installer decades ago. It uses a “hub-and-spoke” design that can sometimes feel like jumping around sections when installing.
We wanted to rethink the installation process, to create a more streamlined experience where people are guided through the installation process step-by-step in a linear manner, so they don’t have to hunt for the right things to configure amid all the possible settings.
Instead of figuring out how to configure the system first, the goal should be to show you a set of applicable options, and then tailor the experience from there. The new interface was designed to be a “guided” experience with good defaults to help people install in different ways, right from the start. It lists possible options on how to install, instead of the longstanding method which requires dealing with technical details of the system to install.
Most typical installations should require not much more than clicking “next” a couple times, have a review page, and then installation. This will make installation not just easier for newcomers to Fedora, but also more streamlined for all of us who have used Fedora Linux for decades.
During the start of the project to re-imagine Anaconda, we identified a few different goals people have when they install Linux on their computer:
The new Web UI is designed to handle all these scenarios easily. Previously, Anaconda required some technical know-how, especially for custom installations. Now, even people unfamiliar with disk partitioning should be able to easily install Fedora, without having to refer to third-party guides or scratching their heads trying to figure out how to partition a disk.
Additionally, we’re adding more to Anaconda too: The older GTK-based Anaconda does not have an easy way to do a “recovery” reinstall which preserves data in home directories. And dual-booting with the GTK version of Anaconda is currently a bit difficult; the new Web UI version of Anaconda makes this much easier.
We’ll talk more about each method further down the page, complete with screenshots!
Anaconda has always used GTK, the “toolkit” that provides the buttons and other widgets that make up many applications and desktops on Linux. The last refresh happened over a decade ago (2013, in Fedora 18). For most of this time, Anaconda’s interface (the part of Anaconda that you see) has been tightly coupled with the backend logic. A few years ago, the Anaconda team started a major effort to modularize Anaconda, to break the code down to smaller parts, which enabled the interface to be changed independently from installation logic.
GTK 3 is still currently maintained, but it’s old and showing its age. It won’t be maintained forever. Porting to GTK 4 (and possibly GNOME’s special widget set, libadwaita) will require a lot of effort to adapt to the changes and would require a massive effort to rewrite much of the frontend, especially as Anaconda has many custom GTK widgets.
Since we’d likely have to rewrite a lot of the frontend anyway, we took another approach and have taken advantage of the modularization efforts to retool the frontend to have a web-based interface instead. The Cockpit team has been providing a web-based interface for Linux systems for managing systems for many years in the Cockpit web console, so it made sense to reuse Cockpit as a base and its web-based widget set, PatternFly, as a starting point for the next generation of Anaconda too.
By-the-way: We’re using Firefox to render the UI when you’re installing locally. (There’s no Chromium or Electron involved.)
While it’s not a native toolkit like GTK, using a web based UI does have several benefits:
We have some plans to expand the storage configuration screen, to provide more than just encryption. For example, in the future we could:
We’re also planning on adding:
The GTK version of Anaconda currently shows you a disk and you need to figure out what to do with it in order to install a system.
The new web UI version of Anaconda uses more of a top-down approach, where you decide how you’ll install on a system, based on the current system’s available storage.
While we already covered it above in a list, let’s dive more into details here, as this does change the way you interact with Anaconda quite a bit, as these are newer concepts when installing Fedora.
The most simplified method is to use the entire disk. This is perfect if you have a blank disk you’d like to install on, either on physical hardware or in a VM. It’s also a great choice if you don’t care about what’s currently on the disk and want to easily install Fedora.
Sharing a disk with another operating system makes it easy to install Fedora along side another operating system. It has a reclaim dialog to erase partitions or even resize supported partitions. If your partition is formatted in a filesystem type that is not supported, you’ll have to either delete partitions in the reclaim dialog or use an alternate tool, like GParted, before launching Anaconda. Windows installations are now encrypted by default with “BitLocker”, so if you’d like to share your computer’s hardware between Windows and Fedora Linux, you will first need to boot into Windows and resize partitions from within Windows itself to make space for Fedora.
If none of the above methods work for you, you’re able to select a flexible layout based on an existing layout on your disk. Linux systems have standard places to add storage called mounts. When using the mount point method, you can select partitions for each mount point, starting with the mandatory “root” partition at “/”, and continuing with the suggested “/boot/” mount point. Additional mount points can be added and assigned existing partitions as well, using free-form text for the names.
If your storage is not set up how you’d like it on the disk and if you don’t want to use one of the guided partition methods, then you can either use an external tool before installing Anaconda to set up partitions and volumes how you’d like, or you can use the “Storage Editor” from Anaconda’s top-right “global” menu on the storage page. This will launch a customized version of “Cockpit Storage” to let you adjust your storage on the fly, to prepare it for Anaconda. Please note, as pointed out in the warning dialog, that this acts directly on your system, unlike Anaconda itself, which queues everything up until you agree on the review screen.
And, if you already have Fedora installed and want to reinstall for any reason, existing Fedora installations have a “reinstall method” at the top. This lets you do a fresh installation and keep all the data in your home partition, instead of having to erase everything.
We’ve also put together a few screencasts to show you what it would be like to use Anaconda.
We have a test ISO you can try out! We’d love to hear from you! Try this out on a secondary machine or in a virtual machine. Do not install this on your main computer or any machine with important information.
To try out the new Web UI installer, you can set up the test ISO on either a virtual machine or real hardware. Here’s how to do each.
Virtual machine:
Physical test hardware:
While new Anaconda Web UI is almost ready for its debut in Fedora Linux 42, starting with the Workstation Live ISO, there are a few things to keep in mind:
We’re hoping to incorporate more feedback from people trying this out, so please let us know any constructive and helpful feedback you might have! Be sure to try it out in different scenarios.
We’re currently doing a “Test Week” (a week of “Test Days”) for the new Anaconda Web UI this week, from November 11 – 15. Read more on the blog post about the Anaconda Web UI Test Week and the detail of how Test Days work.
We’re looking forward to hearing all positive and/or constructive feedback. The forum post for the test week is a great place for you to share a comment! Thanks!
If you find a problem, report a bug at Bugzilla.
admin )
on 2024-11-11 08:00:00 UTC
In the ever-evolving landscape of Linux, Fedora stands out as a pioneer, continually embracing innovation while maintaining stability. One of the most significant advancements in recent releases is the introduction of systemd-homed. This feature aims to redefine how user home directories are managed. It brings a new level of efficiency and flexibility to the user experience. Let’s delve into what systemd-homed is, its benefits, and how it transforms the Fedora ecosystem.
At its core, systemd-homed is a component of the systemd suite that focuses on user home directory management. Traditional Linux systems treat user accounts and their associated data in a fairly static way with home directories typically stored in /home. In contrast, systemd-homed abstracts home directory management into a more dynamic and portable system.
systemd-homed allows user home directory storage in various formats and locations—whether on local disks, networked storage, or even in containers. This flexibility opens up new possibilities for user data management and enhances the user experience significantly.
One of the standout features of systemd-homed is the ability to create portable home directories. Users can easily move their home directories across different machines without losing any settings or data. This is especially beneficial for those who frequently switch between Workstations or Atomic desktops.
Security is paramount in today’s digital age. Encryption is an integral part of the user home directory in systemd-homed. Each home directory can be encrypted using LUKS (Linux Unified Key Setup). This ensures that sensitive data remains protected, regardless of where it resides.
System administrators will appreciate the simplified user management that comes with systemd-homed. The homectl command allows easy creation, modification, and deletion of user accounts. Administrative tasks are streamlined and the complexity often associated with traditional user management methods is reduced.
systemd-homed introduces a new way to handle user sessions. With dynamic user sessions, the system can create a tailored environment based on the user’s specific needs and configurations. This adaptability ensures that users always have a consistent and optimized experience, regardless of the machine they log into.
Fedora, known for its cutting-edge technology, has seamlessly integrated systemd-homed into its architecture. Starting with Fedora 41, administrators can easily take advantage of this feature to create users with personalized configurations. The homectl command provides a user-friendly interface for managing home directories, making it accessible even for less experienced users.
To take advantage of systemd-homed, users can begin by enabling it during the installation process or convert existing accounts afterward. The process is straightforward:
For example, to create a new user in a systemd-homed manged home directory, use the following simple command:
sudo homectl create myuser --disk-size=10G
This command not only creates the user but also allocates disk space for their home directory.
As Fedora continues to lead the way in Linux innovation, the integration of systemd-homed marks a significant step toward modernizing user management. Its features not only enhance security and portability but also simplify the overall user experience. For those looking to embrace the future of Linux, Fedora with systemd-homed is an excellent choice, blending cutting-edge technology with the reliability that users have come to expect.
Whether you’re a seasoned sysadmin or a casual user, diving into systemd-homed can redefine how you interact with your Linux environment. Embrace the change and discover the possibilities that await in the world of Fedora!
admin )
on 2024-11-08 15:04:19 UTC
The Workstation team is working on the final integration of Anaconda Web UI Installer for Fedora Linux Workstation. As a result, the Fedora Workstation Working Group and QA teams have organized a test week from Monday, Nov 11, 2024 to Monday, Nov 18, 2024. The wiki page in this article contains links to the test images you will need to participate. Please continue reading for details.
The Anaconda team would like to ask Linux users to test and share their opinion about the newest version of the Anaconda Web UI. As you might already know, the Anaconda team is working on a Web UI which should not just improve the look and feel but also make Anaconda more accessible and simplify the complex task of system installation. You can read more about the Web UI here.
The biggest overhaul is to the partitioner which has a completely changed approach to this complex topic. The new solution will guide you through the process without expecting to have years of Linux experience.
Currently, we would like to find out if this Web UI is mature enough for inclusion in Fedora 42 (only Workstation edition right now), for that we need you! Please get on board and join Fedora test days.
What is the target:
A test week is an event where anyone can help ensure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.
To contribute, you only need to be able to do the following things:
The wiki page for the Anaconda Web UI test week has a lot of good information on what and how to test. After you’ve done some testing, you can log your results in the test day web application. If you’re available on or around the days of the event, please do some testing and report your results.
admin )
on 2024-11-08 10:00:00 UTC
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic and text version 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 below the infographic.
Week: 4th November 2024 – 8th November 2024
The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
The post Infra and RelEng Update – Week 45, 2024 appeared first on Fedora Community Blog.
Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for a parallel installation, the perfect solution for such tests, and also as base packages.
RPMs of PHP version 8.3.14RC1 are available
RPMs of PHP version 8.2.26RC1 are available
The packages are available for x86_64 and aarch64.
PHP version 8.1 is now in security mode only, so no more RC will be released.
Installation: follow the wizard instructions.
Announcements:
Parallel installation of version 8.3 as Software Collection:
yum --enablerepo=remi-test install php83
Parallel installation of version 8.2 as Software Collection:
yum --enablerepo=remi-test install php82
Update of system version 8.3:
dnf module switch-to php:remi-8.3 dnf --enablerepo=remi-modular-test update php\*
Update of system version 8.2:
dnf module switch-to php:remi-8.2 dnf --enablerepo=remi-modular-test update php\*
Notice:
Software Collections (php82, php83)
Base packages (php)
czanik )
on 2024-11-07 12:31:05 UTC
Last week, I submitted syslog-ng to openSUSE Leap 16.0. While the distro is still in a pre-alpha stage, everything already works for me as expected. Well, except for syslog-ng, where I found a number of smaller problems. As such, this blog is a call for testing, both for syslog-ng on openSUSE Leap 16.0 and also for the distribution itself.
Read the rest at https://www.syslog-ng.com/community/b/blog/posts/call-for-testing-syslog-ng-in-opensuse-leap-16-0
admin )
on 2024-11-06 08:00:00 UTC
It’s almost time for the Linux Distributions DevRoom at FOSDEM again! The Distributions DevRoom is officially accepted as a full-day FOSDEM DevRoom on Sunday, 2 February 2025. Let’s dive into what we would like to see and how you can get involved! Submit your talk to FOSDEM, when you’re ready! Read on for further information.
From the FOSDEM website:
Developer rooms are assigned to self-organising groups to work together on open source projects, to discuss topics relevant to a broader subset of the community, etc.
The general idea is that a group of people get together to organize a mini-event inside the FOSDEM umbrella. The groups of folks submit a proposal to the FOSDEM organizers, and then recruit content and build a schedule for the room. Everyone involved is likely to be a volunteer, but the content is always extremely beneficial, and presented by leaders and experts on their topics.
The Distributions DevRoom will take place on Sunday, 2 February 2025 as a full-day DevRoom. It provides a unique home for the convergence of several different Linux distribution communities to share ideas and start conversations that matter to all of us. Although there are several different distributions that have different approaches to software packaging, choice of desktop environments, and various use cases, this Distributions DevRoom is a historic open forum. It is unique to FOSDEM in making a space for all of our communities to share and learn from each other.
The Fedora Project is co-organizing the Distributions DevRoom at FOSDEM to foster collaboration and innovation among the diverse Linux distribution communities. By facilitating this DevRoom, Fedora seeks to provide a space for open-source contributors and maintainers to exchange ideas, address shared challenges, and work on cross-distro interoperability. This event supports Fedora’s commitment to community-driven development, reflecting its values of openness and inclusivity. Join us to connect with fellow distribution developers, learn about pioneering projects, and contribute to shaping the future of Linux distributions.
We are looking for your most incredible talk for the Distributions DevRoom! No matter where your focus in Linux is (development, community, distribution, testing, documentation, etc.), we want to hear from you. The full CFP details can be found on the CFP email archive. For inspiration, you can even look at the schedule that we had last year!
Important Dates
Will you be at FOSDEM in 2025? The Distributions DevRoom welcomes volunteers to help with various day-of logistics for running the dev room. The list isn’t yet defined specifically, but generally we need people to do these things:
If you are interested in helping out with the Distributions DevRoom, send an introduction email to the FOSDEM distributions-devroom mailing list.
FOSDEM is a free conference that requires no registration of any kind. You just show up on the days of the event, and then attend the talks that you want to attend. It is an extremely popular event, so the talks are also recorded and posted later on the FOSDEM website.
When the Distributions DevRoom schedule is live, you’ll be able to find it on the FOSDEM website, so keep an eye out for updates!
Don’t miss the chance to connect with the Linux distribution community! Whether you’re passionate about the future of operating systems or just curious about the latest developments, the Distributions DevRoom at FOSDEM is your opportunity to engage with like-minded enthusiasts and developers. Join us for in-depth discussions, technical insights, and collaborative sessions. Be part of shaping the next wave of innovation in Linux distributions! Mark your calendar, and come ready to contribute, learn, and be inspired.
admin )
on 2024-11-05 21:45:42 UTC
Fedora 41 has been released! 
So let’s see what arrives with the new releases for the Fedora Atomic Desktops variants (Silverblue, Kinoite, Sway Atomic and Budgie Atomic).
After a long wait and a lot of work and testing, bootloader updates are finally enabled by default for Atomic Desktops.
For now, only UEFI systems will see their bootloader automatically updated on boot as it is the safest option. Automatic updates for classic BIOS systems will be enabled in the upcoming weeks.
If you encounter issues when updating old systems, take a look at the Manual action needed to resolve boot failure for Fedora Atomic Desktops and Fedora IoT Fedora Magazine article which includes instructions to manually update UEFI systems.
Once you are on Fedora 41, there is nothing more to do.
See the Enable bootupd for Fedora Atomic Desktops and Fedora IoT change request and the tracking issue atomic-desktops-sig#1.
The next major evolution for the Atomic Desktops will be to transition to Bootable Containers.
We have established a roadmap (atomic-desktops-sig#26) and for Fedora 41, we added dnf5 and bootc to the Bootable Container images of Atomic Desktops.
Those images are currently built in the Fedora infrastructure (example) but not pushed to the container registry.
The images currently available on quay.io/fedora (Silverblue, Kinoite, etc.) are mirrored from the ostree repository and thus do not yet include dnf5 and bootc.
Once releng#12142 has been completed, they will be replaced by the Bootable Container images.
In the mean time, you can take a look at the unofficial images (see the Changes in unofficial images section below).
See the DNF and bootc in Image Mode Fedora variants change request and the tracking issue atomic-desktops-sig#48.
Fedora Silverblue comes with the latest GNOME 47 release.
For more details about the changes that alongside GNOME 47, see What’s new in Fedora Workstation 41 on the Fedora Magazine and Fedora Workstation development update – Artificial Intelligence edition from Christian F.K. Schaller.
Ptyxis is a terminal for GNOME with first-class support for containers, and thus works really well with Toolbx (and Distrobox). This is now the default terminal app and it brings features such as native support for light/dark mode and user-customizable keyboard shortcuts.
See Ptyxis’ website.
Fedora Silverblue is now Wayland only by default. The packages needed for the X11 session will remain available in the repositories maintained by the GNOME SIG and may be overlayed on Silverblue systems that require them.
See the Wayland-only GNOME Workstation Media change request and the tracking issue: atomic-desktops-sig#41.
Fedora Kinoite ships with Plasma 6.2, Frameworks 6.7 and Gear 24.08.
See also What’s New in Fedora KDE 41? on the Fedora Magazine.
Kinoite Mobile is currently only provided as unofficial container images. See the Changes in unofficial images section below.
See the KDE Plasma Mobile Spin and Fedora Kinoite Mobile change request.
Fedora Sway Atomic comes with the latest 1.10 Sway release.
Nothing specific this release. The team is working on Wayland support.
Until we complete the work needed in the Fedora infrastructure to build and push official container images for the Atomic Desktops (see releng#12142), I am providing unofficial builds of those. They are built on GitLab.com CI runners, use the official Fedora packages and the same sources as the official images.
You can find the configuration and list on gitlab.com/fedora/ostree/ci-test and the container images at quay.io/organization/fedora-ostree-desktops.
With Fedora 41, we are now building two new unofficial images: Kinoite Mobile and COSMIC Atomic. They join our other unofficial images: XFCE Atomic and LXQt Atomic.
See How to make a new rpm-ostree desktop variant in Fedora? if you are interested in making those images official Fedora ones.
See the KDE Plasma Mobile Spin and Fedora Kinoite Mobile change request and the Fedora COSMIC Desktop Environment Special Interest Group (SIG) page.
If you are using the Sericea or Onyx container images, please migrate to the new Atomic names for Sericea & Onyx (sway-atomic and budgie-atomic) as we will remove the images published under the old name soon, likely before Fedora 42.
We will likely rename the official container images as well.
The polkit policy controlling access to the rpm-ostree daemon has been updated to:
See the Unprivileged updates for Fedora Atomic Desktops change request and the tracking issue atomic-desktops-sig#7.
The alternatives command (alternatives(8)) is now working on Atomic Desktops.
See the tracking issue atomic-desktops-sig#51 for more details and documentation.
Support for unlokcing a LUKS partition with the TPM is now included in the initramfs.
See the tracking issue atomic-desktops-sig#33 and the in progress documentation silverblue-docs#176.
Our friends in the Universal Blue project have prepared the update to Fedora 41 already. For Bazzite, you can find all the details in Bazzite F41 Update: New Kernel, MSI Claw Improvements, VRR Fixes, Better Changelogs, GNOME 47 & More.
For Bluefin (and similarly for Aurora), see Bluefin GTS is now based on Fedora 40.
I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA proprietary drivers, extra media codec, etc.).
We have made lot of progress since the last time, thus this section is going to be more exciting!
As I mentionned in First step towards Bootable Containers: dnf5 and bootc, the next major evolution for the Atomic Desktops will be to transition to Bootable Containers. See also the Fedora bootc documentation.
We have established a roadmap (atomic-desktops-sig#26) and we need your help to make this a smooth transition for all of our existing users.
Moving to composefs is one of the items on the roadmap to Bootable Containers. composefs is the next step for ostree based systems and will enable us to provide better integrity and security in the future.
For Fedora 41, we moved Fedora CoreOS and Fedora IoT to composefs.
For the Atomic Desktops, this is planned for Fedora 42 as we still have a few issues to resolve. See the Enabling composefs by default for Atomic Desktops change request and the tracking issue atomic-desktops-sig#35.
This fix is important for setups where the root disk is encryptd with LUKS and the user is asked a passphrase on boot. Right now, the keyboard layout is not remembered and defaults to the US QWERTY layout. Unfortunately this fix did not land in time for Fedora 41 but this will be part of the Fedora 42 installations ISOs. Help us test this by installing systems from a Rawhide ISO to confirm that this issue is fixed.
If you are impacted by this issue, see the tracking issue atomic-desktops-sig#6 for the manual workarounds.
We would like to unify the documentation for the Fedora Atomic Desktops into a single one instead of having per desktop environments docs which are mostly duplicate of one another and need to be constantly synced.
See the tracking issue atomic-desktops-sig#10.
We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users.