The Changelog: Software Development, Open Source - Dear Red Hat... (Friends)

Episode Date: July 14, 2023

Red Hat's decision to lock down RHEL sources behind a subscription paywall was met with much ire and opened opportunity for Oracle to get a smack in and SUSE to announce a fork with $10 million behind it. Few RHEL community members have been as publicly irate as Jeff Geerling, so we invited him on the show to discuss.

Welcome to Changelog and Friends, a weekly talk show about pirating open-source software. Thanks to our partners for helping us bring you awesome pods each and every week. Shout out to Fassy.com, Ply.io, and Typesense.org. Okay, let's talk. So we're here with an inflammatory enigma. It's Jeff Geerling. i read that on your twitter bio so i assume that's what you are hey jeff that actually has to do with my ibd uh internal bowel disease and i don't even remember oh boy i have crohn's disease so my doctor called me that one time but i think if you work at red hat you might uh you might agree with my doctor i thought maybe it was on point you know for the

recent current events i thought wow he has been inflaming things a little bit around here but for sure i would call it kicking hornet's nest really i feel like they put this post out there they being red hat and you responded very clearly some cases calling them dumb literally calling them dumb you know and laying out all the reasons but But like, can you explain what exactly is happening right now to kind of give some context to this conversation? Yeah, I mean, I've worked in the Red Hat ecosystem from the earliest time that I got into Linux. The first thing that I ever did in Linux was I bought Red Hat 5.2 in a CD on the

back of a book. And that was when it was Red Hat Linux. And that was when the whole enterprise thing and the licensing games and things hadn't been really started yet. And it was kind of a heady time in the Linux world. And that was when they were going from like, this is a hobbyist thing to this is a commercial thing to this is an enterprise thing. And we're fighting Microsoft and fighting all these big, huge things and Unix. So I wasn't super involved back then. I was doing graphic design more, so I was on a Mac. But as the years went on, I kept following it,

and then I got back into the ecosystem when I needed to host my graphic design things, which are nowadays web projects. I needed to host them somewhere, and CentOS was the only option. I wasn't going to spend hundreds of dollars a month or, you know, a thousand bucks a year or whatever, just to host my little blog or the little small business website or whatever. And CentOS was seen as this thing that was enterprise-y, but free. So yes, I was a freeloader, but that got me into the ecosystem. That's what does it.

I started figuring out how to automate things with Bash and how to do more Linux-y things. I found out about other Linux distros through CentOS, all this stuff. But it was my gateway drug into the Linux ecosystem where I was a Mac guy, really. And I used Windows and managed Windows NT and did a little Novell stuff at work. But I was generally a Mac guy.

And that really got me into the Linux ecosystem to the point where when Ansible came out, I was big on the Ansible train and wrote basically the book on Ansible for a long time. Besides all that, I would say that I am a contributor. I'm not completely a freeloader anymore. But when I saw the statements that were being made around this whole CentOS thing, where it's like, we took CentOS, then we killed CentOS, and we came up with CentOS Stream, kind of the words, if you reread those blog posts, the words seem very disingenuous from an interpretation of somebody who used CentOS. It's like, oh, CentOS Stream will allow you to

contribute more. It's like, well, I wasn't asking to contribute to Red Hat Linux or Red Hat Enterprise Linux. I was asking to contribute to the ecosystem. I used Fedora. I did all kinds of things. I promoted Fedora. I promoted CentOS. And I even, at a couple places where I worked, I deployed systems that had over 1,200, 1,300 Red Hat licensed systems. So, you know, it's like my gateway into that world was CentOS. So the words that they used when they said, basically, like all these users, you can just use stream. There's a reason why Rocky and Alma came up out of that mess and became so popular because so many people, especially little hosting companies, I know a ton of people who manage hosting for nonprofits or small

businesses and things, there's no way that they could use Red Hat Enterprise Linux. And they enjoyed using CentOS. So when Rocky Anomal came in, they switched to those because it's like, well, you know, you got Debian, which is usually an option or this other thing that is supported for five or 10 years. And it seems like they didn't consider that portion of the community at all when they were making these decisions. It sounds like it was completely a commercial side thing where it's like, you know, CIQ or whoever is taking customers and using free software built on top of Red Hat or rebuilt. They don't contribute anything to the ecosystem when in fact many of the employees there actually do contribute upstream. But of course, those things, we can ignore that

because all they're doing is rebuilding Red Hat. I think to me, the thing that offended me and the reason I said, are you dumb, is because it was just such a smack in the face. Like this is most of the sysadmins I know, almost all the home labbers I know who are in the Red Hat ecosystem, pretty much to a T came in through CentOS.

And when CentOS was taken away, we were all like, oh my gosh, the world is ending. But then Rocky and Alma came in and we're like, okay, we'll stay in the ecosystem. And now those are, you know, enemy number one, it seems. And the craziest thing was early on in this, I said, Red Hat, are you dumb? I really wanted to make a point. I wanted to talk to some of the people internally at Red Hat who I had worked with, like, look, this is going to blow up in your face. This is a dumb decision. You need to figure out a way to make the community not hate you. Then they came out with a second blog post that basically it implied that hobbyists and hackers would not be good for the commercial Linux ecosystem. It's like, hold on a second. That's kind of where everything comes from. Your high and mighty power, your $34 billion sale to IBM,

where did it come from? It didn't come from Microsoft and the Unixes. It came from the community of hobbyists and hackers. And then Mike McGrath clarified in a post on LinkedIn that never on their official blog or anywhere, that, oh, we don't mean you when we're talking about feelers. We just mean the rebuilds or the rebuilders. They always call them the rebuilders. And it's like, well, but I'm still in those communities. So you kind of mean me, but you also kind of don't just because

I contribute some things upstream. But in my philosophy, open source free software is about the community, the users. You don't have to contribute to be part of that. And for a lot of people, the first thing you do is just grab a project and you might change one line of code or a comment and recompile it. Like that's a step. But they're saying philosophically, their thing is if you go into it, it's like, well, CIQ was taking these contracts and starting to sell it. And it's like, well, that's a different thing. That's I'm talking open source philosophy, free software, the ecosystem, the community, they're talking about commercial things. And what I see as their end user license agreement workaround, I see that kind of like playing with

the community and kind of playing fast and loose with what brought them to where they were. Because Red Hat came out of the Linux ecosystem. Red Hat uses a kernel that is developed by other people, not just them. So you can tell I'm a little passionate about this. For sure. Rightly so. I mean, Red Hat wants to control the downstream that comes from an enterprise Linux

that is based upon RHEL, essentially. And by locking up and no longer providing these distros or their downstream to Rocky, Alma, etc. They essentially are locking out their ability to, not impossibly, but just hardly

be bug-free, bug-compatible. Which is their biggest ploy. Like, hey, we want to give you what CentOS was in an enterprise Linux free and open source way. And that's just, they want to give you what centos was in an enterprise linux free and open source way and that's just they want to control it yeah which from a ibm billion dollars you know ipo'd red hat prior to acquisition totally makes sense to as a business control but you have to take into account like you had said the community and the users and i don't know about you jeff but i'm not in the same community and only one community. I'm in many different communities. So I may, like you had said, not contribute in this way or that way, but I'm also over here, over there.

And so they don't take those multifaceted user types into play whenever they make these kind of moves. It's sort of, we want to stop CIQ. We want to stop AlmaLinux. We want to stop what Rocky's doing. But as a part of doing that, we hurt everybody else because this is what happens. Yeah. And the other part of that too, is like from the business side, as somebody who does, I don't have as much infrastructure today as I did a few years ago, back when I was consulting. But from the business side, when I see this thing with CentOS 8, they said, here's CentOS 8, it's 2019, we're going to

have 10 years of maintenance to 2029. Two years into that cycle, oh, wait a second, no, we're not anymore. It's going to be CentOS Stream, which is a different thing entirely and only gets five years of maintenance. That was like throwing a bomb into the community of thousands of users of CentOS, myself included. I had just finished migrating all of my Ansible work, all my CI environments, all my servers and things that ran that stuff over to CentOS 8. And like a week after I finished the last one, that's when that announcement came out. So that was like, bam, ouch, thanks a lot. So my trust level goes from here to like down here, right? I was consulting for Red Hat at this time, too. So I was like,, oh my gosh, this is absolutely wild.

I can't believe they did this, but I couldn't say much about it because I was consulting for Red Hat. You can't do that. Yeah, you can't poop on your employer. I don't consult for them anymore. Yeah, now you can say what you like though. You're free, Jeff, you're free. Say what you want.

So a couple of years later, rocky and alma come up out of this and people like me are like thank you for saving all this work i did to convert all my ecosystem to centos 8 now i can just move to rocky 8 red hat 9 comes out sources are still being published like they promised they would when they killed centos and we're all like okay i'm gonna upgrade to 9 so i had just gotten about halfway done with my Ansible migration to Rocky Linux 9 for all my test environments to test all my stuff for Red Hat Enterprise Linux, because I have a ton of users who do use Red Hat Enterprise Linux for my roles. So I'm halfway through this process. And it's like, okay, you know, it's hard this time,

because I'm not switching to another thing entirely. It's just changing a couple of strings here and there. Halfway through, they announce, oh, you know what? We hate downstreams. It's like, are you kidding? They're like, oh, you know, you can get free licenses. You can get 16 free developer licenses. I'm like, I have over 150 roles.

I have over 25 playbooks. Tons of these are being used by Red Hat Enterprise Linux. And you're saying I can take 16 licenses and try to integrate that with my CI environments. And then, you know, after I said that on Twitter, somebody reached out and said, Oh, we'll get you one of those infrastructure, like open source infrastructure licenses. It's like, that's not the point. Yeah. Part of the value of that was all of the people who could develop for it. And now we have problems with Apple maintainers are needing to get these

special licenses to try to get their packages built for Red Hat Enterprise Linux. It seems to me that there was something like some impetus that was probably, I don't know, maybe a VP got offended or something by one of the business contracts. Some people mentioned the NASA thing when Rocky said that,

oh, we got three NASA contracts or something for three machines. I don't think it's that, but something had to have happened that triggered this because it was a pretty sudden and B there were so many like second level effects that happened that I just like anybody that's in the ecosystem that develops for Red Hat, you would see this like, Oh, maybe let's not double down on it right now. Let's let this do a little bit. Let's figure out a better way to message this. Let's maybe help people.

They keep saying like, oh, just rebase off of stream. Well, maybe if they had announced like, you know what? We were going to do 10 years of Git sources. Now we're going to do five years and we're going to help these people rebuild off of stream. We're going to give them more options. We're going to help figure out ways to make stream more stable because they still had in their documentation,

stream is not meant for production. But those two layers of trust destroying exercises with CentOS 8 being killed, and then the sources being killed, both times early in the release cycle when everybody had started to port things, those two things make me question anything Red Hat can say about any of their products. And that's why I also am like, well, Ansible, Ansible, the community version that I use, which I don't pay for, is downstream of Ansible automation platform. If that becomes a problem, if people like me sell services for Ansible, but don't use Ansible automation platform, am I the enemy? Am I the freeloader? It's a serious question. The Ansible community is structured a little differently, so I don't have as much fear, but I do still have fear,

and I didn't have fear a few weeks ago. Now I do. What's weird to me is you said they kind of despise their downstreams, and it seems like that. If you read the TechCrunch did an article today, or maybe it was yesterday, about the SUSE angle to this, which we'll get to, I'm sure, the fork. And they had quotes from Red Hat in there.

I don't think it's from, I think it's from Gunnar Helixson, Red Hat's VP and GM for Red Hat Enterprise Linux. And in that article, they likened Alma and Rocky to AWS, which has infamously taken open source projects and provided hosted versions, kind of on top and just kind of crushing the little guy, so to speak. Right? Quote-unquote little guy. We're talking about

Elastic, which is not little, but there are littler ones who have their software basically re-hosted and provided by AWS, and a huge competitor. And Red Hat is likening Rocky Linux to AWS in that way. It's like he says they provide zero value. They're like leeches.

That's not quoting, but that's the impetus that you get. And you have to be careful every time that you mention anything like that. All of a sudden, what I've found is on LinkedIn and Twitter especially, there's tons of Red Hat employees will say, well, quote me that. Where did we say that? It's the word freeloaders. on LinkedIn and Twitter especially, there's tons of Red Hat employees will say, well, quote me that. Like, where did we say that? It's like the word freeloaders. I have heard the word freeloader used in conversation,

both working at Red Hat and afterwards, but they've never put it in a blog post. Right. But, you know, people are like, they never said freeloaders. It's like, read the words and look up the definition of freeloader. Like, you're going to see the correlation there. And then Mike put out a blog post saying, yes, we did use the word freeloader, but, you're going to see the correlation there. And then Mike put out a blog post saying,

yes, we did use the word freeloader, but we're going to stop using that. So I hate that it's a semantic game. I hate that they're playing the games at the GPL. And I hate that they're having to talk about, well, you know, if it gets to a legal battle, we'll probably win. It's like, that's not the spirit of open source.

You know, people have said, stop talking about the spirit of open source. It's all about the legal rules. It's like, no, the whole movement comes out of this idea of community, of the fact that software, the bits, are not the thing that provides value. It's the services, it's the support and things like that. And that's how people like me saw Red Hat before. But now I see that Red Hat wants to basically be a consumer of the open source code. And then they want the value stream to end with Red Hat Enterprise Linux, and they can capture all of it.

Whereas before, it hit Enterprise Linux and they let the downstreams also profit off of it, which makes the whole community better, in my opinion. But obviously the people at IBM and Red Hat who do the calculations don't see it that way anymore. Yeah, for sure. Well, I think it's a matter of scale. Profit scale, like revenue scale.

They're at a point now where they're capturing a lot of value. They're also providing a lot of value. Adam Jacob was on the show talking about how much they profit off of Kubernetes by doing what they do. Amazing. They're capturing a lot of value. But I did read that their Red Hats net revenue increases are on a downswing, like 12%, 10%, 8% the last three quarters. So you see that number going down.

They're still more profitable than they were the previous quarter. They're still positives, but they're less positive. You know, I know what you want to see that direction. That's right. Don't go down, go up. And you have pressure to capture so much more. And then you see people like Rocky Linux, maybe they say, yeah, we got a NASA contract.

And you're sitting over there thinking, well, I need more contracts. I can see where you could have that in a competitive environment. You'd be like, ah, man, they're out there capturing some value. We need to get all the value because we've got to make up for that $34 billion price tag.

We have to be valuable inside of IBM. I'm just speculating, but I can see where you would come to that. The scale is just massive. There's also a lot of people, especially Red Hat, are saying, well, IBM had nothing to do with this. And I think anybody outside of Red Hat can say that's BS. It's not sure.

IBM didn't make the decisions. But if IBM had never bought Red Hat, would this exact same decision have been made? I don't think it would be. And I don't think it would be promoted in the same way. When you buy a company for $34 billion and say, you're going to be free, you're going to be able to do what you want, I can tell you there are things that happen internally that would not happen had IBM never owned Red Hat. Not just in Enterprise Linux, but in OpenShift, in Ansible,

and in other communities. Integrations that have to be built up and ways to promote the commercial products on IBM's side. So anytime that that gets brought up, I think it is disingenuous to say, this is IBM's fault and Red Hat had nothing to do with it and Red Hat is dead. I still see Red Hat as being kind of alive inside of there, but it's not the same Red Hat that it was five, six years ago. If you had to create a perfect world for Red Hat, what should they have done? Instead of making this blog post and locking up the Git, RHEL repos and stuff like that, what do you think would have been positive from a monetary standpoint and a community standpoint? What could have they done? I think if they wanted to have their cake and eat it too, they

could have gone down this path towards what we're going to close down Red Hat Enterprise Linux sources. We're going to put them behind the paywall like they did, which is legal. And that was initially a lot of people said, oh my gosh, they're going closed source. It's like they're not closing source. They're not violating

GPL by putting the code behind the paywall. You only have to distribute the code to people you distribute the binaries to. There can be philosophical discussions on whether or not that's in the spirit. I think it is because companies can make money off of the software, but you have to provide the sources and have to not encumber those sources with any restrictions, which that's still a point of argument, I think, in the community. Define that. It's a hard part, right?

What I would say is if they wanted to do this, they should have said, you know what, we see this trend, and we're going to give these downstreams five years, let's say, to show a little more good faith. Like, it's okay to build support off things, but we don't want you to build support being bit-for-bit compatible or bug-for-bug compatible with Red Hat Enterprise Linux, which Rocky has always made that

kind of their advertising tagline. Basically, like, you guys are offending us. Let's figure out a way for you to stop offending us and still be part of this ecosystem. And we're going to give you a five-year deadline. If at the end of that, you're still doing this, we're going to do this closure. That would have still ignited a firestorm, but not a nuclear bomb.

And it comes back to that trust. After the first CentOS death to CentOS Stream, the second one happening so early in the cycle of Red Hat 9, that's where it really grates against, I think, all of our, outside of Red Hat, all of our inner, like, what are you thinking? Like, the timing of this is terrible. At least give a timeline and say, this is what we're doing. As a dumb example of this, I was pretty hot about this sometimes. And one, I put up a PR on one of my Ansible projects, basically saying, you know what, I could throw a nuke into my thing too, by making it so that all my roles fail on Enterprise Linux unless you agree to their EULA. I put it up there with a note saying,

unlike Red Hat, I'm going to do this, I'm going to throw this nuke down, but I'm not going to merge it, I'm not going to actually deploy it unless my community is okay with it. So I put it out there, and tons of people are like, this is stupid, you're an idiot, blah, blah, blah. I can't believe you'd ever do something like this. It would actually restrict our freedoms. It's like, I didn't do it though. That's the point. Like if I'm going to do

something that I see this could upset my community of users, maybe I should tell them about it first because that's the right thing to do. But they just basically threw a nuke into the downstream ecosystem coupled with the fact that there were so many in the first two or three days, there were a lot of articles. There was one in particular on LinkedIn that tore into Gregory Kurtzner, who I've never met. I've had one email with him ever. And that was after all this stuff happened.

I don't know much about him. I don't know much about his history, besides what I've read online. But they were like tearing into him, saying he's like this terrible person and CIQ is horrible and the way that Rocky was structured. Like, where did this come from? Like nobody ever asked about this. They were posting about it. And then I saw other stuff and it leads me to believe

that this was, I don't know, internally I'm thinking that there must have been some conversations with essays, with marketing, with maybe PR, I don't know, about like, here's why this is happening, but they didn't release that stuff publicly. And then there were comments on Reddit from Mike McGrath about some underhanded business decision

and he's not gonna talk about it because he doesn't wanna throw someone under the bus or whatever. I don't know. It felt very weird. The whole way that that first two or three days went especially. And then at this point,

it's Red Hat, if you talk to their VPs and see all the interviews, they're always talking about the commercial side interests and how it's bad business to let your competitors just take your stuff for free. But they don't talk at all. They address none of the trust issues, the community issues, the open source and free software philosophies. And that's, I think, the big difference that I see with the current kind of thing at Red Hat versus 10 years ago, everybody was like, Red Hat is the open company. They develop upstream. They give free stuff downstream. They are part of the community. And they still do so much. And I just hate to see some of that jeopardized because some of the great contributors

who work inside of Red Hat, some of them have emailed me and DMed me and said, hey, thanks for saying your piece because I feel some of that rage too. You know, I think some of them feel the same way, but they're not going to say it because like I said, back when I was consulting with Red Hat,

I wasn't going to throw them under the bus. But they had to feed you. Right. Yeah. Some of this we did cover with greg way back in episode 427 and it was the rise of rocky linux we haven't talked to greg or gregory since then that was 2021 it was january 2021 when rocky first came out it was really before even the the resf i forget the full uh exposure of the name the resf was just the foundation, the structure they created to essentially

ensure that Rocky was community and not Greg or a particular person. While they are board members and they have chair seats and stuff like that, they're not the only, he's not the only person that can say so. So there's tons of stuff I don't want to cover in there because he mentioned legal and all the juice basically. So the things you alluded to is covered for the most part in there from him directly about some of the history there is some bad blood in the water that goes back to centos yeah prior to red hot's acquisition of it which i think this is all from that like that conversation we have with gregory in many ways is a precursor to this

conversation because that was sort of the beginning of all the mess that came with centos that shift etc and now we're here now with sources being withheld and rocky and alma being you know in quotes the bad guys because they're just recompilers or redistributors, essentially, like you had mentioned before. Meanwhile, hanging back here is Oracle. That's right. The whole time they've been doing things 50 times worse by many people's standards. Well, Oracle is the big winner in this whole mess, isn't it? So far, at least.

Well, maybe Suze ends up being. But we should mention the Oracle's epic press release. This is like when you have, well, I don't want to draw analogies that are too strong, but this is just like when somebody comes in and just smacks somebody else when they're down, so to speak. And they did a really good job of it. I covered it in Change Dog News, as people on the pod probably heard. And I was just impressed by this press release. I just loved it. As just a person who enjoys whatever technology companies. Yeah, I mean, it's a popcorn moment for me

because I don't have a dog in this hunt at all. I mean, I have a dog in the greater open source community and I want all of us to thrive and I want people to be able to capture value and to give value away. I want everybody to do well. And I hope the best for all these entities except Oracle. No, just kidding.

Oracle too. I wish the best for them, especially after this press release, just kidding. Oracle too. I wish the best for them, especially after this press release, which did kind of be like, you know what, these people... Back up those words with some action and we'll see what happens. Yeah, exactly. If this wasn't merely a cheap shot, then this could be cool. And that was weird, Jeff. I think you said on Monday, this is the first time you find yourself agreeing with Oracle on anything. So, you know. Yeah.

As somebody who uses VirtualBox and uses Java and all these different things and has built businesses off of a lot of their technologies, I never have ever been like, man, I love Oracle. I've never said that. And I still don't. But I'm like, that was good, Oracle. That was pretty good. For sure. I want to quote Adam Jacob here on this because he tweeted this and I just was like head nodding big time.

He said, we've reached a part of the story where people who should know better are straight facing Oracle, in quotes, is a better friend to open source than Red Hat because they wrote a blog post punching their competitor. Y'all need to do better. I mean, that's a good summarization of how most should respond because, yeah, we should do better. But at the same time, that was a good dunk. There were so many lines in that that's like, man, the sarcasm is just like oozing out of that word. It was the longest single segment of ChangeLog News that I've done because I had to quote

so many parts of it. And they had like a, there was a quote inside of a quote. It's a lot of work for me to cover this and at the end of it I felt like did I just give way too much time to this I don't know let's ship it and see I do want to say that I'd love to get Edward Scriven on who penned that post I'd love to talk to someone like that that's essentially is second to none to the CEO of Oracle who wrote this post who has these opinions I'd love to get the insider view from someone like that about their plans, essentially.

SUSE has put theirs down, forking RHEL, taking investment, and hopefully having, you know, what could be, I guess, a RHEL fork, essentially for us to all standardize against

with enterprise Linux. So we'll see, but I'd love to get their take. To Oracle's credit, they do contribute a lot upstream to Linux. It's not like they their take. To Oracle's credit, they do contribute a lot upstream to Linux. It's not like they only take. Red Hat might want to paint them in that corner,

but they have done a lot. They have some great devs, but we don't expect them to be the open company. They've never advertised Oracle the open company. Red Hat always says we are the open company. Of course, now they've kind of changed that. I've noticed the past three days, I keep seeing this phrase,

we develop in the open and we are an enterprise software company. That's a completely different mindset than we are the open company. I have the open organization from Jim Whitehurst, who is not there anymore. But when you lose that mentality, that's when I think you can start saying like,

you know what, the community is not as important as the profit for the next quarter. I think that some of the people that are making these shifts are not the people that were steeped in the free software ecosystem that came up through CentOS. A lot of these people came up through enterprise, you know, they worked in other enterprise software companies, and they came with a red hat. And they're like, oh, that's cool that you have this open source stuff. It's great that you can pull in more value without having to hire all the developers for all the little random things in the Linux kernel. Sure, we do great stuff, but it's great that we can pull in a lot more. If you're Apple, you know, they rely on free BSD. If you're Microsoft, you actually did write like everything. So I saw somebody joke in

one of the articles that maybe there will be Microsoft RHEL soon. Oh, maybe. For sure. I want to give you some credit too, Jeff, because in your I'm done with Red Hat Enterprise Linux video, you did say, you kind of called this post from Oracle. You said, wouldn't it be ironic if Oracle were the ones who knocked Red Hat down a peg? Really? That's kind of what this post is. Did you have some inside info on that, Jeff? Did you

get tipped? No, not at all. So day three, I was just thinking when I was writing the script to this, I was like, I'm super angry. I want to get that across. And I also want to give people a good overview of what the situation is and where it's going from here. I saw immediately like Red Hat, it's hypocritical what they did. And I think anybody outside of Red Hat saw that, but there's a lot of people internally at Red Hat that kind of can't see that because of where they are. But I saw immediately, like, of all the companies in the world, there's only really one, like, CIQ can't.

Rocky Linux, Alma Linux, Cloud Linux, all these different groups that are doing the downstreams that are basically getting torn apart by Red Hat. None of them could come back with anything. But Oracle has bazillions of dollars. They could do something. So I mentioned, like, wouldn't it be funny? And I never thought it would happen because I was like, Oracle is...

You caught it. Maybe they were listening. And they're like, we should. Damn, we should do this. I mean, Oracle, they have so much money and they have so many contracts in their database, all this stuff, which I hated working with the few times I had to. They didn't have to say anything and they would still be the victor here compared to Red Hat

because nobody expected them to do anything amazing. But then they come out with a blog post and I'm like, yeah. Well, two things that are interesting about that. First of all, I mean, kick a guy when he's down. You know, they're just like, we're about to just come out and kick you while you're down. But then also, it's interesting in that. First of all, I mean, kick a guy when he's down, you know, they're just like, we're about to just come out and kick you while you're down. But then also it was interesting in that post how they, they referred to it almost exclusively as IBM. You know, that's why in my

news coverage, I said, you know, Oracle smacks IBM because they really did. I mean, they're talking IBM, of course, Red Hat is there, but they're really kind of blurring those lines and you can see who they're coming after. And they're really talking about, well, it's all about money and it appears like, yeah, it's hard to say it's not. They aren't wrong, but they're also not right and there are a lot of red-hatters that I personally know that I've been in conversation with outside of the Jeff Geerling hates red-hat type thing

and I think it's disingenuous to go that far that they did but on the flip side it is what it is like Ansible when I was started working with Ansible was independent then it got bought by Red Hat and then but it was still Ansible but then it was Red Hat Ansible and I started seeing some things change like some of the structure the way that it was like how are we going to allocate all our resources and getting things into the you the paid ecosystem outside of the open source area? And then now it's Red Hat Ansible automation platform by IBM is what I call it. Because there's parts of it now that it's like these resources that were focused on making Ansible a better product are now focused on making Ansible tie, Z and to the power platform and all these other things that never would have happened had IBM not bought it. So there's a point, but it's also,

I think some people overplay that point. Yeah, it is what it is. You gave you a little bit of your story about, you know, getting into Red Hat or learning about Red Hat back in the day. I wanted to share my first interaction with Red Hat. So in college, I was into Linux, but I didn't know Red Hat at first. I did run Fedora a few times, but then ended up in the Debian Ubuntu side of things. But I remember one time, I knew who Red Hat was from the hat, and Fedora and this whole thing. And Shadowman.

Yeah, exactly. And I remember one time, and I just had a disdain for Windows. I had gotten that far. I like not going to run Windows. This was 2002, back in the day. And I remember I went to Megamart, which is just a local retail or big box electronics store. I used to just cruise the software aisles, you know, back when we bought software off the shelf. In boxes?

Yeah, I would go down, like when I was, it was right next to my university and at lunch hour i'd just go there and cruise you know and i'd check out the dvds and i'd check out the software and i remember looking at all the windows you know whatever it was xp probably back then and uh then i saw a box red hat linux really cool box with a red fedora on it and the shadow man and and i knew that this was free software like i knew what red hat was i a red fedora on it and the shadow man. And I knew that this was free software. Like I knew what Red Hat was. I knew what fedora was. And I'm like, these people are selling something in a box store.

That's totally free. How cool is that? And I just loved them. I thought it was like the coolest thing ever. And I had the utmost like hacker respect for Red Hat ever since. I've just always had good vibes. Cause I'm like, you know, it takes some chutzpah or whatever it's called to just go and put a box to buy yeah in a store where you can go just go download it for free i'm like maybe they just hope nobody

knows that i don't know who would buy this box but it's cool and i like it so i've had a long time respect for red hat and still do they still put out lots of awesome stuff it's just you see the changes that happen under circumstances that we're in, and it just is what it is. People say that I hate Red Hat. I don't. The reason why I pointed these things out is because I'm like, hold on. Come back. This isn't what you said you would do.

Come back to the light side. Come back to the light side. There's a path, and they're diverging this way, and I'm like, come back this way. Yeah. And I'm willing to forgive. It's going to take a lot more after those two blog posts, after the things that employees have said on, you know, all over the place at this point, after some of the perspective shifts that I see that I would not have dreamt of five years ago. Right. But I still want to see them succeed because I mentioned in a couple of posts,

they're the too big to fail of Linux right now. If they're not backstopped, then maybe proprietary software can make inroads back in on the enterprise. if Red Hat does start failing in enterprise Linux. And there's also arguments from the other side with Kubernetes and container infrastructure and cloud-based computing that maybe none of this matters at all. Who cares about enterprise Linux? But if you look around, pretty much all clouds run on servers and the servers run an operating system

and a lot of those operating systems are one of the top three or four Linux operating systems. So look in my home lab, even the servers that run containers right now, they're all running Debian. I just finished migrating the last one off of Rocky. But it is still important. And you can't, like containers just don't magically wash away the importance of enterprise Linux. Was that migration because of this? Because you were in that migration phase?

Yes. Most of them are running Debian because it's Raspberry Pi OS which is based on Debian but I had a couple other servers that were running Rocky and I was like, forget this and I mentioned in my blog post I'm not supporting Red Hat Enterprise Linux anymore so if something starts failing on Rocky

I'll just kind of drop that support because it's not worth it to me at this point which stinks because I still have my Rocky Linux shirt this is another funny thing I'll just kind of drop that support because it's not worth it to me at this point. Yeah. Which stinks because I still, I have my Rocky Linux shirt. This is another funny thing. One Red Hat employee was like, well, you obviously you're paid by CIQ and Rocky. And I'm like, I've never, I received a t-shirt and two stickers, one of which is on my wall over there.

That's the extent of my relationship with Rocky Linux. They sent me the shirt because I use them in a video when I set up something at one point. And they're like, hey, do you want a shirt? And I'm like, sure, because I like t-shirts. I don't go to conferences as much, so I got to get t-shirts through the mail now. Yeah, got to get your swag somehow. Send it to me.

Is this something you think that Red Hat is going to walk back? Because sometimes when you fill up this big, like you said, nuclear bomb, when you do this kind of thing that does kind of cause an explosion and there's a lot of blowback, there's a lot of disdain, sometimes those decisions get walked back. I don't think so, mostly because the response I've seen after Oracle and after Seuss's blog post is, well, that's what we wanted to happen. It's like, what? I don't know what they're trying to do at this point. It doesn't make sense to me, but I'm not, I don't have an MBA. I'm not a great businessman. I don't think they're going to walk it back though. It doesn't

feel like it. What I think that they could still do without walking it back is help people with CentOS Stream more than they did. One thing that I've seen, which is ridiculous, is a lot of SAs are mentioning, well, everybody can just switch to Stream. It's like, well, your documentation says don't run it in production. So you're telling everybody, the thousands and thousands, you're telling HPC and educational markets, these hosting providers just switch to Stream,

but you're saying it's not stable enough to run in production. You've got to solve that. So solve that issue, help Rocky and Alma rebuild, you know, maybe give them some support in it to show good faith. But I don't think that's going to happen because they've basically excorciated them. I don't think that they're going to walk it back, but I still think that they could do more to make it not so bad, but I don't see any signs that that's happening. I can understand their offense to Rocky and Alma. I can understand the offense completely. Something that I've learned in my life though is whenever, and maybe they're just so big, like you said, to fail, that this isn't a concern for them, is that whenever you come to a table with a decision, with no plans to negotiate, you forfeit all opportunity to have empathy for the other side

and to essentially fine-tune things to be cohesive for everyone, not just the one-sided decision you came to the table with. And like you had said, maybe they could have given them five years to say, help us understand how you're a positive, not a negative, to our goals and the community. Are you simply just a copy of us with support, bug-for-bug compatible? say here help us understand how you're a positive not a negative to our goals in the community are you simply just a copy of us with support you know bug for bug compatible are you just a copy of us with support models that essentially is rel but not rel because if that's the case then we don't like that we think we want to limit you but they made this choice because of that it seems that

impacts everybody i think it would be in their best interest to have, like you had said, CentOS Stream be back to CentOS Waze, where it is production-ready and available to everybody, because that helps the Red Hat Enterprise Linux brand be the de facto, kind of what they have been, which is why we're all in this conversation, because they have been the Enterprise Linux standard. To me, that makes the most sense, to remain and be and solidify that standard. Not just kill off some competitors and lock down your source code to only those who subscribe, essentially. Yeah, I keep seeing this statement.

All of our code, everything in Red Hat is in CentOS Stream. It's like, well, that's not entirely true. 99%, probably more than 99% is. And in terms of the whole complete source availability, it doesn't meet that standard. But the license agreement saying you can download the sources if you have an account and you have a subscription in good standing, that does meet it. But they can't make that statement that everything is in stream because what they're trying to say is why are you doing this downstream we have this upstream which is better and it has everything it's like well if they did their work all in stream and if they

coordinated the releases especially the minor releases through stream that's one thing but they don't they kind of red hat is kind of a little bit of a fork of stream it's not a big fork but it's a downstream of stream so it's not a big fork, but it's a downstream of Stream. So it's not one-to-one identical. But they're trying to sell it as that to the press, I think. Anyone like us can kind of see through that. It's not identical. They've tried selling Stream for three or so years now,

and nobody outside of the Red Hat ecosystem, like the Red Hat Enterprise Linux subscribers themselves and Red Hat, has bought into it. I don't know how they're going to change that without changing stream and making it better. Even in a home lab, stream is not cool. If you can't run it in prod, sure, my Plex server may not be important to anybody else besides my immediate family. But I don't want it to be down.

It's production to you, man. It's production to you. It's production to me, right? Yeah, and somebody can run it. It might be more stable in Fedora, but I'm not going to run Fedora for any of my servers. I'll run it for a workstation, but not servers. As a guy who's run Debian on servers my entire career, I just wonder, why not just come on over where the water's warmer?

Jeff, it sounds like you're here now. It sounds like you enjoy it. I am. I mean, personally, I am. I respect my users, and a lot of them are still on Red Hat, Rocky Linux, Alma Linux. Right. Some are on Oracle. So I don't just want to cut them off like Red Hat likes doing. So that's why I'm like, I'm maintaining the support until it breaks. If it breaks and it's like, oh, you just need to bump

a version somewhere, that's fine. But if it breaks and it's like, oh my gosh, I have to re-architect this for Red Hat 10, I'm not going to do that. I'm going to drop the support at that point. But I've heard from tons of organizations that have everything in the Red Hat ecosystem. A lot of them don't subscribe to Red Hat because they have people that can understand it enough. They don't need the support, that kind of thing. So now they're like, well, what do we do?

You know, we could go to Debian, we could go to Rocky and hope that Rocky keeps doing their little piracy thing that's not actually piracy, because I saw the fun meme of like, I am now an open source pirate, pirate open source software. It's so funny. But yeah, that's when you know you're Epic, when you're pirating open source. But I still see a lot of those people and I want to help them as much as I can. But on the flip side, I'm happy in the Debian world. And I know that a lot of people are like, oh, you should use Nix or use this.

There's a million other distributions. Nix is hard. Sorry. Nix is hard. I can't help but admit it. It's hard. There are lots of good options. Arch.

Arch is the cool one. I switched to Arch one time in production. I got by the way enough times that I was like, I feel like I'm missing out on something with Arch. I put a new customer on Arch Linux. Literally every other server I was maintaining was Debian. I was like, I'm going to learn Arch. And then I stopped.

Not because it's not good. Their documentation is, almost every search ends up somewhere in Arch. They're great for that. Oh, yeah. It's just different enough that I'm like, why am I spending time figuring out how to do this particular thing in Arch

when I already know how to do it on the other side? So when you talk about your users, I'm not familiar with your business. Can you tell, what do you mean by that? What do you host and stuff? My downstream about your users, I'm not familiar with your business. Can you tell, like, what do you mean by that? Like, what do you host and stuff? My downstream open source users who 99.9% of them use my software never contribute back, basically. So the people who make my product, which is open source software, what it is.

Ansible is used by hundreds of thousands at this point. And my roles for Ansible and some of my collections and some of my playbooks have been downloaded at this point, billions of times. A lot of those are CI instances running tests and things, but they're used very widely, I would say. And Ansible being something that was bought by Red Hat and came out of the Red Hat ecosystem and came back into the Red Hat proper is used a lot in Red Hat. And none of my roles are certified. That's when Red Hat works with a vendor to make certified roles that are kind of blessed in the Ansible automation platform and all that.

But I can see the usage and the issues that come in and things. And there's a lot of people that use Red Hat Enterprise Linux and use my roles because my roles are decently well maintained, which you can't say for a lot of things. Not as well nowadays as they were five or six years ago. I used to run a hosting service for Apache Solar, and that was for Drupal websites, basically. And that was profitable, but also it was something that took a lot of time. And five or six OS upgrades into it and five or six architecture changes. I was moving everything to Kubernetes and I was like, you know what?

This isn't the thing that I love to do in life. So I closed off that service. And I also had another service called server check-in for uptime monitoring. Those both use those roles. And I probably used 50 or 60 roles for different things. Gotcha. And now I use about 15 or 20 of them day to day, and then 20 or 30 more. So some of the roles that I don't use as much, like I don't deploy GitLab anymore, so that

role has not gotten much love. But there's still plenty of users that use it to the point where I still maintain it enough that it will work for them. If you look at one of my roles and see I haven't committed anything to it for two years, you might want to think about forking that role, which I'm perfectly happy with. Take my work. I use the MIT license, which is much more like take everything I've ever done and steal it.

Take it from me, please. Here, take it. It's like no warranty, but that's about all. Yeah, so I've considered changing my licensing strategy to GPL just because I've seen the whole idea is based on trust. I trust that, you know, I'm going to give you all my work for free. And you could take it and profit off it, I don't care. But I trust that you'll see that this is a good thing. And you'll do some other good stuff with it, you know, or you'll contribute back, you'll send me a patch, or, you know, you'll help somebody else that uses this thing. Or you'll say like, Hey, Jeff is cool.

Like, that's, that's nice, too. Yeah. But at this point you'll say like, hey, Jeff is cool. Like that's nice too. But at this point I'm like, well, maybe I can't trust because basically all the people that want MIT licensing are corporations that don't want to deal with the poisoning of free software philosophy into their ecosystem. Right. I always picked MIT as well for two reasons.

The first one was I just wanted as many people to benefit as possible, and I just figured the freer, the freer. And I understand how that's maybe perhaps short-sighted and can definitely be argued against. But I was like, just free, as gifty as I can be, which is like, do whatever you want with it. And the other one was because I never had a project

that I felt like, this one's really good. I feel like my open source is always like, yeah, take it. Have fun, kids. Make it as easy to steal as possible so somebody will steal. Are you sure you want to take this? Go ahead, you can have it. But I didn't have any Ansible roles that were really good, which I think changes the calculus, perhaps.

Yeah, and I think that part of that, too, is my philosophy in open source comes out of, you know, I always took before I gave. And one of the first communities where I gave back finally was Drupal. And in Drupal, the whole ecosystem is completely different. Drupal is, I wouldn't say it's an order of magnitude less revenue than Red Hat itself, but it's a very substantial amount of revenue for all the companies in that ecosystem. But there's an understanding. It's just a thing because all of us came out of that.

We took and then we gave back. There's a saying, you come for the code and you stay for the community. Everybody supported each other, and it was GPLv2. And companies would build their own distributions based on it. But all those distributions, there was never a question like, oh, and you give everybody the source code. You could always build off

of everyone else's. Nobody would ever pull any tricks. Nobody would ever try to restrict it. Sometimes conversations like that would happen. I worked at one of the biggest Drupal providers out there, which is Acquia. And sometimes someone would come in and say, well, why can't we do this thing? Well, the immediate answer was because that's not in the spirit. Like we're going to kill our community if we do that. So don't. And then it's like, okay, yeah, that's not in the spirit. We're going to kill our community if we do that, so don't. And then it's like, okay, yeah, that's fine. But on the Red Hat side, a lot of people come in through enterprise software, through proprietary software companies,

and they just have never been raised with that philosophy through their open source life. They see open source as this thing, it's a feature, and it's not the feature. The software is open source, and that like this thing. It's a feature and it's not the feature. Like open source, the software is open source and that's a thing. It's not, oh, and the software comes out of this open source thing and that's cool. It's something you really don't understand if you're really in the muck of it. You know, like if you've maintained a system or deployed software or built software, like you only really understand the philosophies of open source truly if you've been in the mix.

You know, if you've been in the mix you know if you're a purveyor or an outsider to some degree just helping things move along it's kind of hard to really understand the spirit of open source if you haven't been part of hearing people stories like we have on this show for many many years and being advocates for open source because not because jared and i particularly have the kind of software you have out there used by the users you have. It's because we understand the empathy we have for our fellow developer. And we want to see their freedoms be preserved and the things they thrive for and the things they put their work into be free in the way they want it to be free.

And that's what open source really is because my street line, Jared probably shared to some degree his, but I came through WordPress into open source. The fact that K2 had CSS available and it was an open source theme, I learned what it was like to theme a website with CSS. This is back when CSS was taking over tables way, way back in the day. And that's my street line into software. I didn't go to school for it. I don't have a CS degree. I work for an IT company in bizv, which I was very good at. But I started to understand open source by way of being a user, like you had said, a taker of it, not ever

a contributor. And I'd said, as much I've given back to open source is like almost nothing in comparison to my usage of it. Maybe through this show and the things we do, we've given back. Yeah, there's no way we can repay that debt. Right. Yeah. But that's like, you don't get that unless you kind of have a version of that straight line. If you just come through proprietary software and it is like you had said, just a feature or just those users who want freedom, whatever, who cares? Then you're going to have that perspective. But if you've been in the thick of it to learn what you learn, to do what you do, or to go where you go, then you'll understand what it means to have the spirit of open source

and what it means to have free software in whatever way you want to describe free. That cuts right back to the line in that second blog post, like Red Hat, what was it they said, like, rebuilds like Rocky and Alma are a real threat to open source and one that has the potential to revert open source back into a hobbyist and hackers-only activity. It's like, all of us are hackers and hobbyists. Yes, please. Internally at Red Hat,

almost everyone I know started out as a hobbyist in Linux or in whatever, and they came into that ecosystem. So I think that they meant that as a dis, and it is in a business sense. It's like, oh my gosh, we have this professional thing. We don't want it to become a hobbyist thing anymore. That's what it was back when it was really weird

and it was on IRC and ICQ and things and Usenet. These are terrible things. It's like, well, we all see that and we're like... The good old days. Yeah, that's still true. Everything came from there. If we want to go back to that, yeah, just cut off Red Hat. This is awesome.

Yeah, I read that too, and I was like, okay, I know who's writing this because they just don't have the same perspective as I have. It's like I always gravitate towards the weird, towards the obscure, towards the hacker and the free and the cool. That's the cool stuff. They also said we had to pay our people. That was the other thing. This hobbyist, hackers only thing

and then we have to pay people. That was their reasoning essentially. Those are the two main things. We have to pay developers so we must do this. Well, really? Yeah, you do, but that's not the only way. I feel very sorry for the people who were laid off, which disproportionately

seemed to affect the open source communities. For example, opensource.com being basically cut off, the Fedora community manager being cut out. But I feel it is tough to go through layoffs. But that's after a quarter where they said that OpenShift just made a billion dollars. And profits are down, but they're still profits. And you're saying, oh my gosh, oh, please don't hate us because we got to pay our developers. It's like, well, then maybe cut

your profits a little bit. But they can't because it's a for-profit corporation and they have to please their investors and the board and all that. But it's like, you can't use that line. If they were a not-for-profit, sure. We want to pay our developers. And in the Drupal community, we have had that conversation because the Drupal Association, which is a not-for-profit, sure. We want to pay our developers. And in the Drupal community, we have had that conversation because the Drupal Association, which is a not-for-profit, has had hard decisions when times get tougher. How do we keep these developers who are working on the Drupal infrastructure employed and pay them? And so we all band together and the community contributes and we get that.

But you don't get that when you're a for-profit company advertising billions of dollars of profits in your new market segments that are leeching off the Kubernetes ecosystem. Sure, you can contribute back, but you didn't build all of Kubernetes yourselves. Yeah, no sympathy. What do you think about the future of open enterprise Linux as a standard? It has been RHEL. This change may change things. SUSE obviously said they're going to fork it. They've got an investment. Oracle put down their smack down, their little slap in the face. What do you think is going to happen with the open enterprise Linux standard going forward? Well, they say that history doesn't repeat itself, but it rhymes.

And I was not deeply involved back when the whole SEO thing happened. But that was kind of what happened back then when Red Hat Linux became Red Hat Enterprise Linux. And then eventually out of that came Fedora. And there was this movement to try to get like this community-based distribution that all these companies work together with. What was it? Novell. And I forget all the companies involved in it. But basically the same kind of thing happened.

And we're back there again. I can't predict whether Red Hat, this is like a downhill slope for Red Hat or if this is a steady state for Red Hat. I don't think it's going to increase Red Hat's revenues for the next year or two. I think maybe for a quarter or two, they might've locked in some more contracts

just from the people who read all the press and say like, oh my gosh, I'm building this stuff on Alma or Rocky. I got to stop that and move back to Red Hat because I need the support. But I don't think they're building that long-term relationship and the long-term trust. And like I said, I brought companies into Red Hat in my consulting work because I had, you know, learned on CentOS and I said, you need the support and I'm not going to be there for you. So here, use Red Hat in my consulting work because I had learned on CentOS and I said, you need the support and I'm not going to be there for you. So here, use Red Hat. And they could afford it. So they did. People like me are not going to do that. You're going to lose all of those leads, which maybe that's 10% or 12% or something. Maybe it's not a huge majority, but that's a lot of the long-term relationships are built out of that.

And they just said, nope, gone. Like that they provide no value was the words. I want to key on one thing too, because I've been watching you on YouTube for a while, Jeff, probably at least a year, maybe two years when I got into Raspberry Pi is more in pile hole and just home labby stuff. So probably several years. And I think as I've watched you, you're in that obvious hobbyist and hacker. Like you're just, you're literally tinkering and trying to like break things in most cases. Like, will this even work? Will this pile whole NAS scale? Like, will it actually be able to transmit data across the land at speeds? I think, or can you do a petabyte on a Raspberry Pi? You've done all

these crazy things. And so I think in many ways you find ways to innovate and you're in that category. And if you, I'm sure you've even helped many companies who come to you with saying, Hey, Jeff, here's my product for free. You don't have to talk about it, but if you like it, do a video. And I'm sure you've done it at least a couple of times. So you've profited those companies. You've helped them in some way, shape or form, and you're a tinkerer. And so if you PO the tinkers like you, which I'm sure there's many like you who don't have YouTube channels and don't do all the things you do, but do them in the behind the scenes. If you cut those kinds of people out from a RHEL standpoint and you don't bring customers to RHEL anymore, that is bad, right?

That's just bad. But it provides no value, no value. It's just crazy. And the other thing that I think about too, is like seeing the responses. Obviously there's a lot of red hatters. I mean, for me, if somebody attacks my family or my organization that I like being affiliated with or Drupal, let's say, I'm going to feel offended by that. That's just human nature.

So I don't take offense to their kind of lashing back out. But outside of the red hat community, I haven't ever seen someone say like, man, they did the right thing. I've seen a lot of, you know, you shouldn't be so harsh on them, but yeah, they shouldn't have done that that way. That's like as positive as I'll get. And someone mentioned this morning,

I think at this point, I try not to respond to anything because it just raises my blood pressure a little bit. And right now I'm trying to work on a video that I've been working on for six months and I just need to finish this darn thing. I started working on it when I saw the, I think somebody on YouTube reported the thing. And then I was like, there's no way that Red Hat is actually doing this. And I read the blog post and I'm like, oh my gosh, I have to say something. And

that's when I posted Red Hat. Are you dumb? I was like, that's the only words I could come up with. But there's nobody that I've met that's like, that was right. There's a few business type people who I don't know from open source, but I know from other things. They're like, why are you so angry about this? It's like, but once you explain, like, it's the open source side of things. They're like, oh, okay, I can see how you're offended. From a purely business mind, yeah, it's somebody's taking your product and basically restamping it.

Yeah, that's terrible from a business side. From a community side, the way that it was handled, the's terrible from a business side. From a community side, the way that it was handled, the way it was announced, the way it was rolled out, the way that they're responding still in things, it just smacks me the wrong way. You said you couldn't predict the future, but we have a mutual friend, somebody you quoted, Cory Doctorow. He's been on the show. He's said the word in shitification on this show before and explained it in detail. We'll link that in the show notes too for you listeners.

But he may have predicted to some degree what may happen here. He says, quote, here is how platforms die. First, they're good to their users. Then they abuse their users to make things better for their business customers. Finally, they abuse those business customers to claw back all the value for themselves. Then they die. I'm not sure if that's a prediction necessarily, but what was the show title, Jerry?

He just wrote the book on it. What is this called? Gateway Capitalism? Chokepoint. Chokepoint Capitalism. That's right. Like this is an example of, this is a chokepoint. I almost invited Corey on this show to talk with us

because I figured he'd have some angle, but he has so much to say. I thought I would like. I cited that in my video on this. And that video, I I figured he'd have some angle, but he has so much to say. I thought I would like... I cited that in my video on this. I was never going to make that video. Even after I read that thing, I was going to make my one blog post, Red Hat, are you dumb? And then after

I posted that and got so much backlash from Red Hat employees, I put I'm not going to support Red Hat and Enterprise Linux moving forward. That was going to be the end of it. But after those two things, and then that third blog post... I'm done. I was like, no, I'm going to make a video on this because they're not seeing anything. So if they had not responded in the way that they did, I would have never made the video that has half a million views. And right now is the number one video I've ever made on my

YouTube channel. Like I would have never done that. I would have never made the decision to stop supporting Red Hat Enterprise Linux. I don't know. For me, it's like this is a demarcation line and they have crossed it and they look like they're turning further that way in their response. And like I said, I still think that they could come back, but they're not right now. And all the things that I'm doing, I'm like, please come back. Like I still want to be part of that, but not as much anymore. And at this point, like I said, I've moved over to Debian for all my servers. I think I have one Red Hat 7 server

running backups right now in the cloud, and I don't like touching my backup servers, because once they're running, you don't want to touch them. So I'm just waiting until that one's done, then I'm going to move it to Debian. What do you think is going to happen, or should happen, to Rocky and Alma? What should they do as a response

to this? What are their options? I don't like the business side of what, I never knew what CIQ was, coming into all this. I knew there was Rocky Linux and Alma Linux, and they solved my problem, and that problem was, I was using CentOS for all my testing and stuff, and that went away,

and Stream was not a good replacement, so I switched to RockKey. And I could have switched to Alma. It was kind of 50-50. They both were kind of like, here's the thing, and I was trying to figure out which one is going to have the longer runway. And it seems like both have equal footing in terms of how stable they've been and how quickly they've gotten releases out and how they've adapted and things. But I mean, on the business side, I didn't know anything about CIQ until this whole thing blew up. I still don't know if they were like underhanded because like I said, I could sell support services for Ansible as long as I say I'm not Red Hat. I'm just Jeff Geerling selling support services for Ansible. I don't see anything wrong with that from a business perspective because it's a downstream thing. That is where, like, if CIQ did do all this

and was trying to get contracts selling Red Hat but not Red Hat and all that, I don't know exactly how that happened. And, you know, yeah, that seems a little shady. But on the flip side... Where'd you hear this stuff from? What post were that in? Where'd you get this information? In a bunch of posts on LinkedIn from Red Hat Solutions Architects, basically.

Can you share those links with us so we can put them in the notes? I can, yeah. And there was an InfoWorld article, I think, too, that implied as much. I think it was Matt Hesse wrote an article where I was like, did Red Hat write this or did you write this? I don't know. But yeah, I don't know where, you know, it almost seems to be like the thing that got sucked into all this. And it seems like the attacks were all against CIQ and by extension, Rocky Linux. That's what it felt like to me from all the posts that I saw on LinkedIn and from the

implications in posts on Reddit, especially by Mike McGrath, who wrote those two blog posts that are on Red Hat's blog. Alma, they seem like they still don't 100 have a path forward they said like we're in this we're going to help you we're going to do this and you know i think one one thing on the table was just going to stream and like following the major releases and switching to a five-year support plan so i don't know where they're going to go with rocky i think that they're so far it seems like they're just going to pirate open source. That's their plan.

And I think that's kind of fun because it's memeable. I'm going to steal open source software. That doesn't compute, but that is the reality that we're in at this point. I was thinking if they wanted to, I have a Red Hat subscription. If they want to burn mine, I'll download one point release point release that's fine i'll be part of that cause i love it so that's crazy you can like in not literally employ but employ folks who are willing to give you the sources give you the sources red hat burner accounts to try to steal open source code. I still think that given enough money and enough good lawyers, someone could fight the ULA restrictions.

Because the restriction basically says, you are free to do whatever you want with the open source software, the source code. But if you share it, if you exercise your right to share it, which the open source code says, you must not restrict the right to share it. If you do that, we'll end our business relationship with you. To me, that like as a Joe Blow on the street, that really sounds like coercion or intimidation. But because there's a contract versus a copyright, the copyright is the code, the contract is the EULA. Apparently, according to many legal experts I've spoken to, that's fine. It's okay to intimidate someone with your business relationship if it's just a copyright thing that,

you know, you copy the code and then we'll terminate the thing, even though the code says in its license that you can't intimidate me. It doesn't make sense and it doesn't seem moral or ethical, but apparently it's legal. And that's from every person that I've talked to in corporate open source law that I've spoken to four different people now, all of them said they're pretty sure that they're in the clear. Like they don't see any reason why this is going to be a problem. But like I said, I think if you had enough lawyers and enough money, which again, Oracle

is the only company on the planet that probably has the case and the lawyers that could back it up. I think that they're the only company that could make a challenge if they set things up where they pulled the code out of the Red Hat subscription and open sourced it. If I did it, I would just get my account terminated and then I'd be like, oh, I hate you, Red Hat, and then nothing else. And you'd be all out of money.

Yeah, I would run out of money in the first week. I guarantee it. The first day. And that's, you know, Red Hat. I think Red Hat's banking on that, that nobody would dare challenge it because it's shaky ground. But there is ground there. But it would require so much money and so much effort that nobody's going to do that.

Well, let's end on something happier, something joyous. If you want to talk about it, what's the six-month-long video you've been working on? What is it? When is it going to be out there? Have you heard of Mr. Beast? I have heard of Mr. Beast. So Network Chuck and I went to Mr. Beast's studio, and we worked on a project for his 1 to 100 video,

the one where he put ages 1 to 100 in little boxes, and they all had competitions. So if you watch that video, there's many points where they do votes, and they hit a button, and one time a guy smashes it with his elbow a few times, which is like, oh, don't do it too much. They press buttons, and then when they reveal the vote, the rooms light up different colors. Chuck and I worked on that project and I

have, there are stories, many of which I can't tell. There are stories. How many are going to make it into the video? So I actually, just before the show, I finished writing my first draft. This has been months I've been working on this. I actually used AI to transcribe all of the footage that I did into a huge document, and then I used another AI to summarize all that so that I would have the ability to know in my brain all the things I said so I could start writing a script. After months and months and having 13 hours of footage, I finally have a rough draft that is 42 minutes long, and I need to cut out at least 15 or so minutes to make it manageable. So that's my task this week is to try to get that down to like 25 minutes or so.

And then it's still going to be a slog. When's the publish date? I'm hoping in a week or two. My goal is the end of this month. So by the end of July, because I'm going to LTX. And LTX is a conference run by Linus Tech Tips, the YouTube channel. And it has a lot of the YouTube creators in the tech space, especially PC building and home labbers.

We have a home lab panel there, actually. That'll be kind of fun. That's cool. I think it'll be live streamed on float plane. I hope it'll be available afterwards, maybe on YouTube. But a lot of the home lab YouTube community will be there. Wendell from Level and Tech Tex and Patrick from Serve the Home, a bunch of other great folks.

But at LTX, I have a couple of big projects I've wanted to finish by then. So I have to finish editing this video like within a week or two so that I can work with the MrBeast folks because they've grown to the size where now they have to care about legal things. A lot of smaller YouTubers, it's like, oh, you're filming something

and there's somebody in the shot. It's not a big deal. But like with of smaller YouTubers, it's like, oh, you're filming something. There's somebody in the shot. It's not a big deal. But like with Mr. Beast, it's like, yeah, we have the shot here. You got to cut that part out. And then I got to re-edit and, you know, so I'll have to do all that stuff. So I have to finish the edit like next week so that we can re-edit by a week or two after that if I want this out by the end of the month. But I just said, I have to finish this thing.

I've been working on it. I actually spent probably 50 or 60 hours testing things after the whole thing was over to validate things that we learned while we were there. For example, static electricity, button signaling. I got a high speed camera to test some things with arcade buttons and different types of buttons that we used to validate some of the things that we found when we scaled it up to 100 rooms in a huge place. And I couldn't use Raspberry Pis because they were not in existence back then. Not anymore. I ended up using these little things called Le Potatoes,

which are like Raspberry Pis, but as you'll see when I do the video, they had their own set of problems. Le Potatoes, huh? Lay potato, yeah Well we'll have to get you back after LTX then sometime to kind of dive into some Homelab-y things. We've been looking forward to talking about Homelab stuff. I've been paying attention

to you, TechnoTim Wendell from Level1 many others of course and I love talking about that stuff and we have yet to really break the mold on talking about Homelab stuff here on any of our shows, because it's mostly around software development, infrastructure, and cloud, but not so much like your own personal cloud or things you do behind the scenes at your house. Homelab has opened my eyes to a lot of things.

I've always had a little bit of something something like one or two Raspberry Pis doing things. But when I got into it a couple years ago, I've learned so much more with deployment, what makes certain software packages easier for it applies to small business too, because you don't have a team of sysadmins, you usually got like the IT guy, or a couple IT guys and an intern. So it really opened my eyes to the ecosystem around open source software for server type things and sharing and all that versus proprietary solutions for some things. Like I, I think at this point, I don't have anything proprietary running in my rack right now. I still have a bunch of stuff on my computer, but at this point it's all open source on the rack is unify's os

proprietary nope i do not use unify so that is i thought you had like something in there no all these youtubers use unify and well i do so i have uh netgear techno tim does where i guess just him yeah but yeah i mean unify they make ubiquity makes uh great stuff yeah that's for sure but it's a expensive and I try to go cheap. And B, I feel like I learn more when I don't have my handheld as much. When you have to get into the weeds on things, I like that. It is expensive. What do you use then as your primary gateway and router and firewall?

Drop some hardware and some software. Right now it's an Asus running, what is their thing? It's not OpenWRT, the Merlin WRT or whatever, the Merlin firmware. And then I have this guy here. You can't see it if you're listening to a podcast, but I have this router box

that was recommended by Serve the Home that has four 2.5 gig ports. And that'll be replacing that. I actually did that at my office already i am building out a new office slash studio because the kids here at home too loud make recording difficult i have no idea what you're talking about so i already have one there and i'm gonna put one in here so then most of my switches are microtik because the price is right the features are good and they're quiet quiet. Quiet is big for me.

That's what Gerhard recommended, when we talked to him last. Yes, he did. Yeah, MicroTik was what he recommended. Is that easily available in the US? That was like a European brand. Most of the time they are. During the pandemic, things were wild.

I had to buy one from Europe and then switch out the power cord. But nowadays, almost all their gear is available now through resellers here in the US. Cool stuff. I'm looking forward to that video. Get her done, will you? Jeff Geerling on YouTube.

Watch all his videos. I watch not all, but some. Paid attention to some of the cleanup process you had for your new office. I'm planning to watch your all-flash NAS fight here shortly because I just love hosting data. I'm a NAS fight here shortly because I just love hosting data. I'm a sucker for ZFS. I just love hosting data.

It's like this, this is, it's called the Pocket NAS. This was built by one of those hackers and hobbyists. Like these things are cool because it drives forward open source things like Open Media Vault, which is recommended for this thing. More users means more eyes on bugs, more bug reports eventually. If you get 100 more users and one of them is a contributor,

that's awesome. Do you have any unpopular appendages, Jeff, by any chance? Besides all the ones you just shared about Red Hat? Yeah. Some of those are not quite unpopular, but popular. I mean, for me, I still like to build my own stuff a lot of times.

A lot of people use not invented here, you know, pulling all the things and rely on everything. But if you look at my Ansible roles, like most of those are based, most of my infrastructure is built on stuff I wrote, which is funny because I have tons of users. But for anyone who really wants to get into it, I would say like fork my stuff and maintain it on your own. Don't use my stuff because you can make it better for your own infrastructure,

for infrastructure especially, but for software too. I think after seeing the way that Drupal has gone and the way that other communities have gone, I kind of do see more value nowadays in building your own stuff. Even if you're redoing some things, instead of the Node.js approach where you have, like, to do a Hello World, you have 350 libraries imported. Yeah. I like that one. I'm with you. It's popular with me.

It's unpopular in some circles, the whole, like, anti-NIH. Yep. Well, it is a continuum, right? Like, it's a spectrum, right? You have dependency hell on one side, and you have NIH to the nines on the other side. And we all have to figure out where we live on that spectrum. And I'm definitely more onto the NIH side of the fence.

But you don't want to live on either extreme, because you're either just gluing together other people's code endlessly, or you're writing your own firmware for your ASUS. And maybe Red Hat, the best opportunity out of all this is we can all write our own operating systems and maintain our own Linux distros. I think that's the takeaway.

That's what they want us to do. You can't have this one anymore. Bye. Well, Jeff, hey, thank you. I know that you got this MrBeast video that you just mentioned and all these things on your shoulders. I emailed you yesterday. You said yes, so I appreciate you. You know, maybe this is the end of your rant. I don't know.

Maybe the end of all the things you had to say, or at least, you know, a— Well, it depends on who comes in to beat the dead horse tomorrow, right? First it was Oracle, then Suzy. This could just be a stepping stone on our way to somewhere else. But I appreciate you coming on, sharing your thoughts, and riffle me and Jared here on Change Looking Friends. It's been a blast. Yeah, thank you.

Bye, friends. Bye. Bye. All right, that's the Scuttlebutt for this week. Definitely check out Jeff's YouTube channel and let us know in the comments if you'd like to hear from him more on the show. Oh, and check out our YouTube as well if you haven't yet.

We post clips from all of our pods, unpopular opinions, you know, just the good stuff. Find it at youtube.com slash changelog. Thanks once again to our partners, fasty.com, fly.io, and typesense.org. And thanks as always to Breakmaster Cylinder for ensuring we have the bangin'est beats and all the biz. Coming up next week, changelog news on Monday, an awesome interview with Steve Yegi on Wednesday, and our

friends Brian Cantrell and Steve Tuck from Oxide Computer Company on Friday. That's a pretty good lineup, if I do say so myself. Okay, that's it. This one's done. But let's talk again, real soon.