Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts
Found the internet!
nazunalika commented on
Posted by
9 points · 13 days ago

We have a conversion script for 9 here.

nazunalika commented on
Posted by
35 points · 18 days ago

It will be ready when it's ready. We typically say to give st least a week's time before seeing the next point release. (As much as we'd like to release day off rhel or the day after, we have a round of tests and other work we do to ensure everything is in working order).

With that being said, we are finishing up secure boot builds for the kernel and once those are done, we will be passing 9.1 to our testing team for review.

nazunalika commented on
Posted by
16 points · 1 month ago

I'll start by saying I am a volunteer on the project, co-leading Release Engineering. A few of my team do work for CIQ. Even though this is the case, they are very adamant about telling vendors that special code, fixes, and so on will not be added for them in the base distribution because that violates the core principal of the distribution: bug-for-bug compatibility with RHEL.

If they want something special, a Special Interest Group (SIG) should be proposed, changes to a current SIG should be proposed if applicable, or changes should be requested to Red Hat for CentOS Stream. If a customer wants something special, they can likely get it from their chosen support venues if that support venue does support those types of requests. It won't come to Rocky Linux in any form, it would need to be on the path I explained earlier. More information SIG's can be found here.

I am very against any vendor/sponsor trying to ask us to make changes for their own use cases. I've made that clear with my team and the rest of the Rocky teams where I stand on this. Whether the member on my team is volunteer or not, we are all on the same page and push back on those types of requests.

As for Rakuten, they will likely propose their own SIG for their Open RAN or other pieces they develop/work on. It's very likely that they understand how the above works, and anything special is on them or through CIQ's support, and at the end of the day, SIG's would be there too.

Op2 points · 1 month ago · edited 1 month ago

This description sounds like a sound approach, in terms of not creating a forked version of the base product, which as you say, you can't really do anyways if you want to continue to be bug-for-bug with RHEL.I was commenting more on the dynamics where some people start making money (in this case it appears Ctrl IQ is being paid by Rakuten), and the employees that are paid request things from the volunteers, who don't get paid to do them. It might not be an issue at this stage, and may never be an issue, but it is something to watch out for.

If there ends up being many companies paying Ctrl IQ for support and services with Rocky Linux, or you start to see multiple other companies offer support and services for Rocky Linux, there would tend to be more demands and requests on the volunteers - and the volunteers may look up and see all these people making money, with them doing a bunch of work, for free. This is what i call the "chump factor", where the volunteer feels like he/she are being taken advantage of.

see more
4 points · 1 month ago

I do understand where you're coming from, and it is a valid concern. I think anyone can make cases like this, whether at the individual or project level. There are those out there who will refuse to work on a project or otherwise unless they are pain in some way. I will note that is me heavily generalizing, as every project is different.

At the end of the day, we are all volunteers and it should be understood from a community stand point that is how we operate; as volunteers to build and provide a RHEL derivative for the enterprise linux community and beyond. That's really our primary goal. However someone wants to use it, it's on them.

To address the "chump factor" and some of the points you made in your original post, I'm not entirely concerned with CIQ/Perforce/Openlogic/Whomever making a profit on providing paid support for Rocky Linux, nor am I concerned with who their partners or customers are. It doesn't bother me in the slightest. And this is why:

  • We provide a RHEL derivative as a base platform for anyone to build on or use as they see fit.

  • We're volunteers. Immediate turn around is never guaranteed and should never be expected.

  • The common user is typically the one who reports an issue. If something is seriously broken or wrong with a package or two or the distribution (that is not reproducible with RHEL), then they would likely report it through the proper channels (bug tracker, mattermost), regardless of who it is.

    • We do not fix bugs or issues in the distribution directly unless it is fixed by upstream (Red Hat) with a common updated package. Exceptions are patched/debranded packages (very few) and rocky specific packages (release, logos, others).

  • We support only what we ship in our base repositories. Third-party repositories (such as EPEL, ELRepo, RPMFusion) and SIGs typically provide useful additional content, which the community generally recommends, and can sometimes within reason support. See this page for more information. Anything else is the user and vendor's responsibility.

  • We are not responsible for the paying customers nor software that some support vendor sells/provides/builds for their customer that runs on Rocky Linux. We support what we ship, and that is it. There is no special treatment.

As an addendum: regardless of who it is, "back channel" communication is discouraged; making a bug report in the public view is highly encouraged. When a bug report is open, it opens a line of communication with us and ultimately helps both parties. The reporter will generally understand that this is all volunteer work and immediate turn around is not guaranteed.

nazunalika commented on
Posted by
Op3 points · 1 month ago

In re-reading the article and a comment I saw on another site raises some questions for me:

  1. The headine says they are switching from Red Hat to use "true open source". Not sure what that means since if Red Hat was not "true open source" then CentOS Stream, Rocky, Alma and others would not exist. So I am guessing his definition of true open source means to be able to use without having to pay anyone for it. Or what might they mean ??

  2. Will Rakuten use the standard Rocky Linux version, or will they get other features or code in working with CIQ as the article states ? And if they are paying CIQ for code changes and/or support, is that "true open source" by their definition ?

see more
1 point · 1 month ago

Honestly, I'm not sure what it means either. Perhaps they meant from a support and licensing standpoint. Perhaps they don't need everything 100% supported from CIQ, but having that support in some instances would be helpful to them. I'd imagine they may be using a standard Rocky Linux version in some instances but then extra stuff provided by CIQ in others. I'm honestly unaware, I'm just guessing as much as you.

From what I do understand, they may be looking to push for a Special Interest Group within the Rocky Linux project too. So contributions may be there in particular. Perhaps they'll also contribute upstream to CentOS Stream? It'll be interesting to see what happens as this year winds down and 2023 starts.

Here's their official announcement

nazunalika commented on
Posted by
Op2 points · 1 month ago

lol - Yes I see people saying they chose Rocky because they liked the name better. I'm running CentOS 7, I'm not the most up-to-date person. I keep rpms updated, but I know CentOS was always slow to update things, which from my reading seems to be solved moving forward with either Rocky or Alma. It seems like coin flip, which is why I am asking because the decision seems less obvious. :)

see more
1 point · 1 month ago

The good news is whichever you pick, even if you pick both, you can be assured that you will have compatibility between each other as well as RHEL. I know we have some users that use both or support both whether as a hobby or professionally. Plus both communities are fairly active, so you're in good hands either way in my opinion.

nazunalika commented on
Posted by
2 points · 1 month ago

The live images tend to have just a bit more than what the DVD installs. As you might know, the idea with the live images is you can boot it to see what it's like and install it as is without using the DVD. XFCE and KDE are a bit different in that regard as it has to be a bit more custom (last I checked there's no dnf groups to lean on like gnome on the DVD, so we have to be a bit more precise).

What I would say is if you're specifically looking for just a gnome desktop experience, you can't go wrong picking up the live image. It has a smaller download footprint than the DVD.

nazunalika commented on
Posted by
2 points · 2 months ago

Versions do not generally upgrade/rebase during a minor release's support cycle (which is 6 months). 8.7 will have cockpit 275 in November.

nazunalika commented on
Posted by
3 points · 2 months ago

You could file a request at to see if they'll branch it to epel 8 and epel 9. It might require more than just that though, I believe it needs psiconv-devel and goffice-devel, which isn't available in Rocky nor in EPEL.

User avatar
RHCE and Certified Specialist in Identity Management. IRC: [email protected]
Cake day
November 14, 2013

Moderator of these communities


6,437 members

Trophy Case (2)

Nine-Year Club

Verified Email