Discuss December 2020

discuss@lists.centos.org

157 participants
95 discussions

Current CentOS Stream already the downstream of the upcoming RH EL 8.4?
by Gianluca Cecchi 10 Dec '20

10 Dec '20

RH EL 8.3 released at the end of October 2020. Planned 8.4 would be at the end of April 2021. Now that CentOS has bridged the gap with 8.3 + updates, can we tell that what is going into Stream right now will begin to be the upcoming RH EL 8.4 and so that in the next five months we will get a real scenario of what is planned up to 2024? Thanks, Gianluca

2 1

Future of CentosPlus?
by Gerhard Schneider 10 Dec '20

10 Dec '20

Is there anything known about the future of CentosPlus after moving to a Pre-RHEL CentOS Stream? It would be of no interest to RedHat.. Gerhard Schneider -- Gerhard Schneider Institute of Lightweight Design and e-Mail: gs(a)ilsb.tuwien.ac.at Structural Biomechanics (E317) Tel.: +43 1 58801 31716 TU Wien / Vienna / Austria Fax: +43 1 58801 31799 A-1060 Wien, Gumpendorfer Straße 7 http://www.ilsb.tuwien.ac.at/~gs/

3 2

Re: [CentOS] https://blog.centos.org/2020/12/future-is-centos-stream/
by Gionatan Danti 10 Dec '20

10 Dec '20

Il 2020-12-10 18:40 Brendan Conoboy ha scritto: > Hey, you dropped Centos-devel from your reply. I'll assume that was > intentional, but if it wasn't feel free to quote any of this back > there. Hi Brendan, no, it was not intentional - I replied from the smartphone and I accidentally dropped the centos-devel list. I'll reply quoting the entire conversation to let others read your useful information. > On Thu, Dec 10, 2020 at 9:26 AM Gionatan Danti <g.danti(a)assyoma.it> > wrote: > >> Il 2020-12-10 14:35 Brendan Conoboy ha scritto: >>>> - are you going to keep stable ABI between Stream kernel >> releases, >>>> or >>>> should we expect each kernel to break 3rd party drivers/modules? >>> >>> All our kernel changes are implemented against the kernel ABI- >> there >>> is no point in time during release development when we have >> interim >>> changes in the kernel that ignore the symbols in the whitelist. >> So >>> basically if your experience of going from one minor release to >>> another has been smooth, the incremental kernels between those two >>> releases would also tend to run smooth, assuming whatever motions >>> happen with the 3rd party drivers/modules behind the scenes >> continue >>> to happen (for example, rebuilding from source). >> >> Let's forget about minor release upgrades and focus on the >> incremental >> kernel updates between point releases for a moment. Can we expect a >> stable kernel ABI for these releases, or should we expect breaking >> changes? In other words, should 3rd party kmod be constantly updated >> for >> *any* kernel released on the Stream channel, or can we expect them >> to >> keep working until a "next-release" kernel appears? >> >> Regarding symbol whitelist, I understand it as related to a single >> minor >> releases - ie: all kernels of 8.3 branch will obey it, but this can >> be >> false for kernel on, say, 8.4 >> >> Am I missing something? > > I think it's a question of nuance. In broad strokes we don't break > the kernel ABI as outlined by the whitelist starting with the first > major release. In fact, taht whitelist grows throughout the life of > the release, making the ABI more predictable. The problem you've > likely experienced is that loadable kernel modules have access to > symbols not included in the whitelist. Whether we're pushing new code > upstream or backporting new code from upstream, we endeavor to keep > symbols the same, even if they aren't on the whitelist. But if for > strong technical reasons it's better to change a symbol, that will > happen upstream, and if it wasn't part of our whitelist, it can happen > in RHEL as well. Usually these changes only require minor updates in > the loadable kernel modules, but for an end user this is the > difference between a module loading or not loading, so the impact is > glaring. > > I'm not sure how things will take shape with CentOS Stream and > external drivers, whether some gating activity wil elrepo will hold > back kernel updates until elrepo is updated, or if a SIG will form, or > some other thing. All I can say for sure is that when you have a > group of people with common problems, they will create solutions, and > we want those solutions for CentOS Stream. So we'll work it out, I'm > just not sure how yet (kABI isn't my focus, I'm simply familiar with > the dynamics because I was the overall RHEL 8 development lead). > >>>> - what/how many synchronization points are going to be with RHEL >>>> releases? >>> >>> I'm not sure I'm interpreting your question correctly, could you >>> restate? I don't want to hit you with detailed process >> information >>> only to find out I'm answering the wrong question! >> >> With Stream, all is going to change constantly. We will have any >> "sync >> point" where Stream is 100% identical to a specific RHEL point >> release? > > OK, I understand now, thanks! I don't think there will be a point > where a RHEL minor release compose will be NVR identical to a CentOS > Stream compose, though they will be pretty close. The reason for this > is that there is a period of time where we're working on 2 RHEL > releases at once: The one that is about to release, and the one that > will follow. CentOS Stream, I believe, will follow the source tree of > "the one that will follow." All the same fixes will be there, but > CentOS Stream will also get additional fixes and features not included > in the near term RHEL release. > >> Thank you for taking the time to reply. >> Regards. > > I appreciate the questions! Regards, Thank you for the clear replies. Regards. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

1 0

Update path question in connection with CentOS Stream?
by Walter H. 10 Dec '20

10 Dec '20

Hello, when someone has installed a CentOS 7.1 in the past, and did 'yum update' regularily, his/she got a CentOS 7.8 now without any reinstallation procedure or other complications; when the same wanted to update to CentOS 8 he/she had to do a new install; what happens to CentOS Stream? when some is now installing CentOS Steam and will do 'dnf update' or 'yum update' regularily in the future, what does he/she get till the "end"? is this a rolling release like Win10 which doesn't need to be reinstalled now and in future? (the fact that hardware can break is not the question) Thanks, Walter

3 2

CentOS-announce Digest, Vol 189, Issue 3
by centos-announce-request＠centos.org 10 Dec '20

10 Dec '20

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2020:5239 Important CentOS 7 firefox Security Update (Johnny Hughes) 2. CESA-2020:5235 Important CentOS 7 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 9 Dec 2020 20:21:57 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:5239 Important CentOS 7 firefox Security Update Message-ID: <20201209202157.GA1948(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:5239 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:5239 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: cb3a549fe050cd75184479500b542065e37366ce62d90769646352bf2d9798a2 firefox-78.5.0-1.el7.centos.i686.rpm 4276584eb593d2fb304ab50518d7e2c4f955abe8fc5b3d1b9f0dd053d363f298 firefox-78.5.0-1.el7.centos.x86_64.rpm Source: 3d26716ee84904cf6f57b0e9d00d84765a498c15b8f0ac649d7f49248c61dca0 firefox-78.5.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 9 Dec 2020 20:24:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:5235 Important CentOS 7 thunderbird Security Update Message-ID: <20201209202441.GA2130(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:5235 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:5235 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f57d7074e8e50a23c9a10a230c6edbd1f48bc3130046704525be72e10c371656 thunderbird-78.5.0-1.el7.centos.x86_64.rpm Source: 6d147795bfe6c18c042e338932f14bdfcde9403bec0ccbb0c9c1132545645e57 thunderbird-78.5.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 189, Issue 3 ***********************************************

1 0

Centos Developers Opinion
by Sergio Belkin 10 Dec '20

10 Dec '20

I would like to know the opinion of the CentOS developers on the decision to end CentOS. Because people already made his voice heard... What do you think? Is it a great decision and master play of business? Because you know 'devops-container-facebook-intel-thing' and "hey is the inevitable train of history? "Adapt or die?" Really? How could you explain what hundred of people around the world that already implemented CentOS 8 and helped reporting bugs, many of them cannot afford RH subscription? How could somebody trust on a company that one day happily says "if you don't like CentOS Stream, pay us?" and sents to trash a project of 16 years? Did nobody know what Red Hat was working on this? How strange is... I read you, we, the CentOS community read you, what do you think? Thanks in advance -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

1 0

Moving to CentOS 8 Stream
by Pete Biggs 10 Dec '20

10 Dec '20

It's got to be done, so may as well test it ... The FAQ says to do: dnf install centos-release-stream dnf distro-sync This I did and everything went fine. I checked before doing the distro- sync and there was a load of new Stream repos in /etc/yum.repos.d Rebooted the machine and dnf has gone back to only looking in 8.3, and the stream repos had disappeared. Looking in the logs I can see this: 2020-12-09T12:28:42Z DEBUG ---> Package centos-stream-release.noarch 8.4-1.el8 will be installed 2020-12-09T12:28:42Z DEBUG ---> Package centos-linux-release.noarch 8.3-1.2011.el8 will be obsoleted 2020-12-09T12:28:42Z DEBUG ---> Package centos-release-stream.x86_64 8.1-1.1911.0.7.el8 will be obsoleted and Installing: centos-stream-release noarch 8.4-1.el8 Stream-BaseOS 21 k replacing centos-linux-release.noarch 8.3-1.2011.el8 replacing centos-release-stream.x86_64 8.1-1.1911.0.7.el8 The centos-stream-release RPM does not contain any repo information, that was all in centos-release-stream that has been removed. So stream has deleted itself. It's not a good start. I also can't seem to get back to a sensible system and have now got a system with a mixture of CentOS 8 and CentOS 8 Stream RPMs with no way of installing the Stream repos from an RPM. I see that "subscription-manager" has been installed on this system now which it never was. Is CentOS also going to be part of that ecosystem as well? Fortunately this was a throw-away install. I hope no one has tried the instructions in the FAQ on an important machine! P.

9 15

Setting up NIS on Centos 8
by Mark LaPierre 10 Dec '20

10 Dec '20

Hey Y'all, I found this: https://www.server-world.info/en/note?os=CentOS_8&p=nis&f=1 I've been told in the past that NIS should not be used because of some supposed security issues. Can someone site any authoritative documentation concerning the security issues extant in NIS? My plan is to set up NIS and NFS on my home network server where I plan to host all the local home network /home directories. I'll use automount on all the other nodes to mount up the home directories when a user logs on. -- _ °v° /(_)\ ^ ^ Mark LaPierre ****

4 5

Learning to build applications
by H 10 Dec '20

10 Dec '20

I have managed to get through the qtmake stage of compiling the current github version of pgmodeler on CentOS 7 but make && make install fails with: make && make install cd libutils/ && ( test -e Makefile || /bin/qmake-qt5 -o Makefile /home/h/pgmodeler/libutils/libutils.pro CONFIG+=release PREFIX= BINDIR= PRIVATEBINDIR= PRIVATELIBDIR=/lib ) && make -f Makefile make[1]: Entering directory /home/h/pgmodeler/libutils' g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O2 -std=gnu++1y -Wall -W -D_REENTRANT -fPIC -DBUILDNUM=\"20201030\" -DBINDIR=\"\" -DPLUGINSDIR=\"/lib/pgmodeler/plugins\" -DPRIVATEBINDIR=\"\" -DCONFDIR=\"/share/pgmodeler/conf\" -DDOCDIR=\"/share/pgmodeler\" -DLANGDIR=\"/share/pgmodeler/lang\" -DSAMPLESDIR=\"/share/pgmodeler/samples\" -DSCHEMASDIR=\"/share/pgmodeler/schemas\" -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/libxml2 -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -Imoc -isystem /usr/include/libdrm -I/usr/lib64/qt5/mkspecs/linux-g++ -o obj/exception.o src/exception.cpp In file included from src/exception.cpp:18:0: src/exception.h:41:11: error: ‘underlying_type_t’ in namespace ‘std’ does not name a type constexpr std::underlying_type_t<Enum> enum_cast (Enum obj_type) noexcept ^ src/exception.cpp: In constructor ‘Exception::Exception(ErrorCode, const QString&, const QString&, int, Exception*, const QString&)’: src/exception.cpp:295:86: error: ‘enum_cast’ was not declared in this scope configureException(QApplication::translate("Exception",messages[enum_cast(error_code)][ErrorMessage].toStdString().c_str(),"", -1), ^ src/exception.cpp: In constructor ‘Exception::Exception(ErrorCode, const QString&, const QString&, int, std::vector<Exception>&, const QString&)’: src/exception.cpp:314:86: error: ‘enum_cast’ was not declared in this scope configureException(QApplication::translate("Exception",messages[enum_cast(error_code)][ErrorMessage].toStdString().c_str(),"",-1), ^ src/exception.cpp: In static member function ‘static QString Exception::getErrorMessage(ErrorCode)’: src/exception.cpp:371:25: error: ‘enum_cast’ was not declared in this scope if(enum_cast(error_code) < ErrorCount) ^ src/exception.cpp: In static member function ‘static QString Exception::getErrorCode(ErrorCode)’: src/exception.cpp:382:25: error: ‘enum_cast’ was not declared in this scope if(enum_cast(error_code) < ErrorCount) ^ src/exception.cpp: In static member function ‘static QString Exception::getErrorMessage(ErrorCode)’: src/exception.cpp:378:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ src/exception.cpp: In static member function ‘static QString Exception::getErrorCode(ErrorCode)’: src/exception.cpp:386:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ make[1]: *** [obj/exception.o] Error 1 make[1]: Leaving directory /home/hakan/pgmodeler/libutils' make: *** [sub-libutils-make_first-ordered] Error 2 I am a beginner when it comes to compiling applications and would appreciate suggestion how to fix the above. Thank you.

2 4

ContOS 8 is dead. Viva Rocky Linux!
by Lists 10 Dec '20

10 Dec '20

The list is swamped with news about CentOS 8 dying in a year and becoming stream Linux. IWeve been here before, folks. I remember when Red Hat Linux disappeared to become the Feodra / Red Hat Enterprise we know today, which gave birth to White Box Enterprise Linux, Scientific Linux, and CentOS. WBEL and SL slowly faded and CentOS won out. And then CentOS, eventually folding into RedHat, promised everyone that it had the support of Red Hat - now part of IBM. Well, now we're back to the big announcement: Red Hat (IBM) is going to mix it up again. And now, as before, come the clones: Rocky Linux has been announced... https://www.reddit.com/r/RockyLinux/comments/ka0qlv/ meet_rocky_linux_new_rhel_fork_by_the_original/ If history is any guide, you'll change a line somewhere in /etc/yum.d and then run yum update to switch over. That's how I switched from WBEL to SL to CentOS, way back in CentOS 3 or 4 days. (I don't even remember which one anymore) The more things change, the more they stay exactly the same... Ben

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2020