Earlier quoted context omitted.
What is IBM doing with this?
They acquired RedHat
Red Hat Enterprise Linux 8 released
21–30 of 150 posts
Re: Red Hat Enterprise Linux 8 released
#22Wrote this comment a while ago for anyone wondering about this: Just installed it in a VM, changes that jumped out at me: • No Python (that you should develop against) installed out of the box. There's a /usr/libexec/platform-python (3.6) that yum (dnf) runs against, and then python2/python3 packages you can optionally install if you want to run python scripts. • Kernel 4.18 • No more ntpd, chrony only • /etc/sysconf…
Neat, but a great isolated example of the ancient software people who use RHEL have to deal with. RHEL 7 has dmesg from util-linux 2.23, the "colors by default" feature[1] first came out with 2.24 released on October 21st, 2013, which is around the time[3] the first beta of RHEL 7 came out.
1. https://github.com/karelzak/util-linux/commit/9bc2b51a06dc9c...
2. https://github.com/karelzak/util-linux/releases/tag/v2.24
3. https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#RHEL_...
Re: Red Hat Enterprise Linux 8 released
#23I have no appreciable Linux skills so forgive my naïvety with this question: In the promo vid on their site, there are a couple of people gaming. Is this alluding to the fact that you can game on RHEL or that it powers the backend of games? Just curious...
2) Steam now bundles Wine and lots of games are tested and semi-officially supported with it now, bumps the playable fraction to more like 60-70%—and you can enable it for all games with a settings checkbox, too, and more often than not it works.
Re: Red Hat Enterprise Linux 8 released
#24Wrote this comment a while ago for anyone wondering about this: Just installed it in a VM, changes that jumped out at me: • No Python (that you should develop against) installed out of the box. There's a /usr/libexec/platform-python (3.6) that yum (dnf) runs against, and then python2/python3 packages you can optionally install if you want to run python scripts. • Kernel 4.18 • No more ntpd, chrony only • /etc/sysconf…
It makes a lot of sense that OS-stuff points to a seperate Python interpreter, don't you think? I like this approach.
Re: Red Hat Enterprise Linux 8 released
#25Wrote this comment a while ago for anyone wondering about this: Just installed it in a VM, changes that jumped out at me: • No Python (that you should develop against) installed out of the box. There's a /usr/libexec/platform-python (3.6) that yum (dnf) runs against, and then python2/python3 packages you can optionally install if you want to run python scripts. • Kernel 4.18 • No more ntpd, chrony only • /etc/sysconf…
My most disliked feature. The colors in everything always clashes with both my background color (the best one for my eyes) and my vision in general. The first thing I do on any new system is to figure out how to turn of the colors. Otherwise I can't see any of the output.
Re: Red Hat Enterprise Linux 8 released
#26Earlier quoted context omitted.
It makes a lot of sense that OS-stuff points to a seperate Python interpreter, don't you think? I like this approach.
Do you think that there should be separate platform-sh interpreter for system shell scripts, and so on? That kind of strange for me. Probably difference is that shell is "complete" program, while Python is not.
Re: Red Hat Enterprise Linux 8 released
#27Earlier quoted context omitted.
It makes a lot of sense that OS-stuff points to a seperate Python interpreter, don't you think? I like this approach.
Do you think that there should be separate platform-sh interpreter for system shell scripts, and so on? That kind of strange for me. Probably difference is that shell is "complete" program, while Python is not.
Generally sticking with whatever bash your distro comes with is fine, whereas the services you deploy often depend on a particular version of python.
Re: Red Hat Enterprise Linux 8 released
#28Earlier quoted context omitted.
It makes a lot of sense that OS-stuff points to a seperate Python interpreter, don't you think? I like this approach.
Do you think that there should be separate platform-sh interpreter for system shell scripts, and so on? That kind of strange for me. Probably difference is that shell is "complete" program, while Python is not.
For the system I think it is a good idea to limit library interactions with things related to keeping the system running or booting.
Re: Red Hat Enterprise Linux 8 released
#29Wrote this comment a while ago for anyone wondering about this: Just installed it in a VM, changes that jumped out at me: • No Python (that you should develop against) installed out of the box. There's a /usr/libexec/platform-python (3.6) that yum (dnf) runs against, and then python2/python3 packages you can optionally install if you want to run python scripts. • Kernel 4.18 • No more ntpd, chrony only • /etc/sysconf…
It makes a lot of sense that OS-stuff points to a seperate Python interpreter, don't you think? I like this approach.
Re: Red Hat Enterprise Linux 8 released
#30Earlier quoted context omitted.
It makes a lot of sense that OS-stuff points to a seperate Python interpreter, don't you think? I like this approach.
Aye; this should have been done a long time ago. I wanted to say 'since the beginning' (whenever that was), but maybe there were good reasons 20 years ago that I can't recall. It probably made sense when disk space was a lot more constrained.