5 ms·
>Red Hat seems to be upping the limit to 240 sockets per developer as of this writing -- EDIT: I read twitter, seems it may mean number of machines as opposed
by jmclnx 3y ago
>Red Hat seems to be upping the limit to 240 sockets per developer as of this writing
-- EDIT: I read twitter, seems it may mean number of machines as opposed to open sockets. But a very confusing post.
I stopped with RHEL 2 months ago at work, I use Slackware at home.
What does that quote mean, if I get a RHEL developer license, am I limited to the number of open sockets ? That almost goes back to the per user licenses in the old UNIX Days. If I ever had to use RHEL, I would now say no just because of this.
- buzer 3y ago> am I limited to the number of open sockets I assume they mean CPU sockets.
- jmclnx 3y agoI was thinking the same, if so that is a direct line to how AIX is provisioned, limitations on use and pay more to get more. I the author of the post says, time stop RHEL support. I wonder if/when the FSF will weigh in.
- jmclnx 3y ago>TYPO: I the author of the post says I meant to say: Like the author of the post says
- yrro 3y agoIn Red Hat Subscription Management I can see that each entitlement for the "Red Hat Developer Subscription for Individuals" product is good for a system with up to 128 sockets. And you get 16 (or possibly 240, or possibly this is a bug) entitlements.
- yrro 3y agoIt's now back down to 16, aww!
- keeler 3y ago> I use Slackware at home. Slackware was my first distro decades ago, and I have lots of fond memories learning Linux with it. How is it these days? What makes it your distro of choice at home in 2023?
- systems_glitch 3y agoNot OP, but: stable, with up-to-date packages. Configuration and maintenance does not change drastically between versions (there's a paper manual, it's on its second revision). I can be heads-down on something for months and not run updates, and then run them and they apply fine and don't hose anything. Long support for releases, both officially and on slackbuids.org
- jmclnx 3y agoPlus, IIRC, Slackware may provide custom support for unsupported releases for a fee. >If for some reason you are unable to upgrade or handle your own security patches, limited security support may be available for a fee. From https://slackware.osuosl.org/slackware-11.0/ChangeLog.txt https://slackware.osuosl.org/slackware-11.0/ChangeLog.txt
- 2b3a51 3y agoFrom my end user perspective Slackware 15.0 works fine - up to date(ish) packages with what might be described as 'conservative' (old school) administration. For server use it might be best to have a look at the Slackware forum... https://www.linuxquestions.org/questions/slackware-14/ https://www.linuxquestions.org/questions/slackware-14/ and perhaps post a few questions once you have evaluated the basic OS. Build scripts for software outside of base is at http://slackbuilds.org/ http://slackbuilds.org/ There are various third party scripts for automating installation for software outside of the base.
- systems_glitch 3y agoSlackware ftw. Came back to Slackware on pretty much all workstations/laptops around 10 years ago. Some servers are also running it but mostly I've switched to OpenBSD.
- hhhfgshanda828 3y agoWhether machines or sockets, it doesn't matter, 240 is an insanely large amount to be given out like that. I'm flabbergasted that people are complaining about this.