Re: [CentOS] CentOS 8 future

[Pete]

At 13 December, 2020 Simon Avery wrote:
> Reply-To: CentOS mailing list 
> 
> On Sat, 12 Dec 2020 at 23:55, edward via CentOS  wrote:
> 
> > appears facebook is running centos stream and also helping developing
> > centos.
> 
>  A small but important point of order on that statement, based on the
> article you link;
> 
> "an operating system they derive from CentOS Stream. "
> 
> So Stream is the starting point which Facebook then does "facebook things"
> to and forms their own in-house distro. They're not running Stream.

A few engineers from the OS team at fb gave a talk in brussels earlier this
year. It explains what's different from vanilla stream and what the facebook
things that go into it are:

https://www.youtube.com/watch?v=cA_Nd3crBuA

Skip to 23:30 where they start talking about stream.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Konstantin Boyandin via CentOS]

On 19.12.2020 01:46, Leon Fauster via CentOS wrote:
> Am 18.12.20 um 19:14 schrieb Matthew Miller:
>> On Fri, Dec 18, 2020 at 08:12:26AM -0500, Konstantin Boyandin via 
>> CentOS wrote:
> It's purely a developer's distro.
 Has Chris Wright ever recommended CentOS for any purpose other than
 development and testing?
>>> Will a Red Hat CTO, in his right mind, ever recommend a free clone of
>>> RHEL for any purpose other than  development and testing?
>>
>> Right... he's not "lying", he just has a different audience.
>>
>> Red Hat has definitely never ever said in any official way that CentOS 
>> Linux
>> is acceptable for production uses. And that's not going to change with
>> CentOS Stream.
>>
>> You should see people's heads spin around like a scene from a horror 
>> movie
>> when I suggest that people actually do run Fedora operating systems in
>> production!
> 
> 
> In the different threads here in the list - I noticed that everyone
> (not all in quantity) has a different definition of production and 
> development "classification". For instance RH: Their devel license
> talks about not to use it for production. I am still unsure where
> the border for that are? Running a workstation and "producing" output
> that have value for me is a production system. As also a fly radar
> HA cluster running 24/7 is a production system. Anyway, lets see
> what Q1 2021 will bring ...

A good point. I would say that production server is the one used by 
users of a service - the server which is expected to be stable, reliable 
and predictable.

So yes, the workstation I use in my everyday tasks is a production 
system for me.

-- 
Sincerely,

Konstantin Boyandin
system administrator (ProWide Labs Ltd. - IPHost Network Monitor)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Konstantin Boyandin via CentOS]

On 19.12.2020 01:14, Matthew Miller wrote:
> On Fri, Dec 18, 2020 at 08:12:26AM -0500, Konstantin Boyandin via CentOS
 wrote:
 It's purely a developer's distro.
>>> Has Chris Wright ever recommended CentOS for any purpose other than
>>> development and testing?
>> Will a Red Hat CTO, in his right mind, ever recommend a free clone of
>> RHEL for any purpose other than  development and testing?
> 
> Right... he's not "lying", he just has a different audience.

An audience from another reality, I assume.

Which makes me curious, why Chris Wright doesn't say a word on the 
subject after the announce of CentOS imminent shutdown? I would admire 
to read his words of "now that we decided to shut down CentOS Linux..."

> Red Hat has definitely never ever said in any official way that CentOS
 Linux
> is acceptable for production uses. And that's not going to change with
> CentOS Stream.

(sigh) CentOS was and still is used successfully on production servers 
all over the globe. Those are facts. Whatever Red Hat thinks or advises 
doesn't change the facts. They would never recommended a *free* clone of 
RHEL for production use, even if it would be 100 times more  stable.

> You should see people's heads spin around like a scene from a horror movie
> when I suggest that people actually do run Fedora operating systems in
> production!

I was using Fedora on production servers, so what?

Finally, I choose to use on production something that requires less 
attention on yearly basis. So Fedora moved on to development systems, 
and CentOS/other distributions with long support are now on production ones.

If people are happy with Fedora on production, that's strange to me, but 
why I should object?

-- 
Sincerely,

Konstantin Boyandin
system administrator (ProWide Labs Ltd. - IPHost Network Monitor)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Konstantin Boyandin via CentOS]

On 18.12.2020 23:28, Johnny Hughes wrote:
> On 12/17/20 7:54 PM, Konstantin Boyandin via CentOS wrote:
>> On 16.12.2020 22:50, Johnny Hughes wrote:
>>> On 12/15/20 9:59 PM, Joshua Kramer wrote:
 On Tue, Dec 15, 2020 at 7:41 PM Johnny Hughes 
 wrote:

> $250K is not even close.  That is one employee, when you also take
 into
> account unemployment insurance, HR, medical insurance etc.  now
 multiply
> that by 8.  Now, outfit those 8 employees to work from home .. all
 over
> the world, different countries, different laws.

 I'm genuinely curious about something, and this is mostly academic
 since it's probably the subject of proprietary discussions within
 RedHat.  Presumably, RedHat had a build pipeline for RHEL that worked
 well for them, by supplying alpha/beta releases of point releases to
 their customers and giving them time to "cook" before releasing those
 point releases into production.  Why would RedHat invest millions more
 in buying the CentOS process just to have CentOS act as the beta?
>>>
>>> Why did they change the development process of RHEL ..
>>>
>>> Because they want to do the development in the community.  The current
>>> process of RHEL development is closed .. they want it to be open.  It is
>>> that simple.
>>>
>>> I think Stream is also very usable as a distro.  I think it will be just
>>> as usable as CentOS Linux is now.
>>
>> It's usable, as Fedora is certainly usable - in its separate use cases.
>> It's not bug-for-bug copy of current RHEL, so it's *not* as usable as
>> CentOS Linux was.
>>
>>> It is not a beta .. I keep saying that.  Before a .0 release (the main,
>>> or first, main reelase) is a beta.  Point releases do not really need
>>> betas .. certainly not open to anyone other than customers.  Now CentOS
>>> Stream is available all the time to everyone, customer or not.  Once the
>>> full infrastructure is in place, everyone (not just RHEL customers) can
>>> provide feed back and bugs, do pull requests, etc.
>>
>> Now please tell me whether Chris Wright was lying when saying the below
>> to ZDNet:
>>
>> "To be exact, CentOS Stream is an upstream development platform for
>> ecosystem developers. It will be updated several times a day. This is
>> not a production operating system. It's purely a developer's distro."
>>
>> It's purely a developer's distro. Shall I explain difference between a
>> developer's distro and the one suitable for production servers (a
>> rhetoric question)?
> 
> Of course he wasn't lying.  The purpose of ANY CentOS release from a Red
> Hat perspective, is as a developer release.  Red Hat has never produced
> CentOS to be used in production for any reason.

Believe me, I don't care a penny about what Red Hat has in its perspective.

Fact: CentOS is and was successfully used in a variety of production 
servers (where RH, of course, would prefer to see RHEL). CentOS was 
stable and reliable. This is why I, among other sysadmins, was using it. 
It was stable and conservative, that's what I need.

> It is ALSO completely free to use however YOU want to use it.  As is
> CentOS Stream.  If it meets your requirements, you can use it.  Stream
> is no different.
> 
> People who certify things, who certified CentOS Linux for things, are
> free to evaluate and do that with CentOS Stream as well.
> 
> Is it ever going to be like it was before .. no.  If that is a deal
> breaker for you, OK.  Then you can't use CentOS any longer.  Great, if
> you can't use it, then use something else.
> 
> All I can do is what I can do .. All you can do is what you can do.
> What is absolutely not helpful is continued complaining.  A decision
> was made. It is implemented. CentOS Stream is CentOS Stream.

Who's complaining?

I am just displeased to see a corporation, which has no more use in 
CentOS, having decided to just kill it off.

As it was said many a time in the list, if the problem was in money, all 
RH would need to do was to ask. There would have been much response from 
both people and companies. No, RH just doesn't need it. CentOS Stream 
better supports its business model. Just a business decision, nothing 
personal.

I am sorry to see the community being split and displeased, that's all.

I will definitely use CentOS Stream, as development media (as I use 
Fedora), in case someone cares.

> If you never want to use CentOS again .. great, don't use it.  I can't
> make people use CentOS if they don't want to.
> 
> What I will do is what I have been doing for the last 17 years .. I will
> do the best job I can to make the things I can build for any version of
> CentOS Linux (or Stream) the best they can be.  If people can use them,
> OK.  If they can't OK.

I appreciate both your efforts and and efforts of whoever else supported 
CentOS all these years. It was a great work.

Personally, I advised to whoever I could to buy something from RH to 
support the cause, and supported CentOS in other possible ways I 

[CentOS] PXE configuration

[Erick Perez - Quadrian Enterprises]

Hi guys,
I have a Centos 7.9 TFTP/PXe server that I use to serve ISO installers. I
can properly serve installers but not live CDs.

But I want to add a live cd, I'm using this but is not working.

Can someone suggest a fix?

label 2
menu label ^2) Run Centos LiveCD 79 x64
kernel centos7_x64_livecd_genome/isolinux/vmlinuz0
append initrd=centos7_x64_livecd_genome/isolinux/initrd0.img
rootfstype=auto ro rd.live.image
method=http://192.168.1.83/centos7_live/LiveOS/squashfs.img
devfs=nomount


-- 

-
Erick Perez
Quadrian Enterprises S.A. - Panama, Republica de Panama
Skype chat: eaperezh
WhatsApp IM: +507-6675-5083
-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Que rumbo piensa seguir este grupo de listeros?

[Gerardo Barajas]

Excelente pregunta.

Sin embargo, creo yo, que sucederá lo mismo que en otros proyectos. La
Lista seguirá ahí pero con muy poca, y si no es que nula actividad.
*Gerardo Barajas Puente*



On Fri, Dec 18, 2020 at 2:28 PM Ing. H. Anibal Talingo G. via CentOS-es <
centos-es@centos.org> wrote:

> Muy buenos dias a todos.
>
> Sigo a esta lista desde hace unos 8 años (quizá mas;
>
> no tengo la certeza, ya que hace unos meses borré miles de correos
> antiguos;
>
> sin embargo conservo algunos de esta lista,  con fecha de Mayo de
> 2013...je je je)
>
>
> A lo largo de este tiempo, las respuestas a mis preguntas por parte del
> grupo, me han
> ayudado mucho en la resolución de varios problemas. Gracias a todos por
> su apoyo.
>
>
> Ahora que el tema (tan sonado en Internet por cierto) de
> IBM-CentOS-RedHat está
> en boca de tantos profesionales de las IT, me pregunto:
>
> Cual es el futuro de este grupo?
>
> Me queda claro, que es muy pronto para responder, que hay varias
> alternativas (como lo
> decia EPE en su video, muy bueno por cierto) pero lo que si veo claro es
> que:
>
> CentOS, deja absolutamente de ser CentOS (como lo conociamos hasta hace
> poco)
> y dificilmente volverá a ser lo que era.
>
>
> Quedo al pendiente de todos sus atinados comentarios.
>
>
>
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] CentOS 8 future

[Ljubomir Ljubojevic]

On 12/18/20 9:20 PM, Joshua Kramer wrote:
> Suppose it is June of 2022 and I have been collecting and archiving
> all of the various versions of packages that are coming out for CentOS
> Stream.  Then, maybe RHEL 8.7 is finalized and hits the mirrors.  I
> can analyze the versions of packages that landed in RHEL 8.7.  Then I
> can grab those versions from my archive and tag them "8.7".  I could
> configure my repositories appropriately and build some ISO images.  Of
> course, I couldn't call that "CentOS 8.7" because RedHat has
> prohibited that.  But still I could release ISO's of "Enterprise
> Respin 8.7".  That is the easy problem to overcome.

Every package in CentOS stream will be signed with CentOS keys, and
CentOS is now trademark of Red Hat. Are you sure it would be legal to
publish/distribute CentOS-signed packages under any other name?

CentOS and other clones were legaly "safe" because they distributed
their own binaries, but could bot use any RHEL's binaries...


-- 
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-es] Que rumbo piensa seguir este grupo de listeros?

[Ing. H. Anibal Talingo G. via CentOS-es]

Muy buenos dias a todos.

Sigo a esta lista desde hace unos 8 años (quizá mas;

no tengo la certeza, ya que hace unos meses borré miles de correos antiguos;

sin embargo conservo algunos de esta lista,  con fecha de Mayo de 
2013...je je je)



A lo largo de este tiempo, las respuestas a mis preguntas por parte del 
grupo, me han
ayudado mucho en la resolución de varios problemas. Gracias a todos por 
su apoyo.



Ahora que el tema (tan sonado en Internet por cierto) de 
IBM-CentOS-RedHat está

en boca de tantos profesionales de las IT, me pregunto:

Cual es el futuro de este grupo?

Me queda claro, que es muy pronto para responder, que hay varias 
alternativas (como lo
decia EPE en su video, muy bueno por cierto) pero lo que si veo claro es 
que:


CentOS, deja absolutamente de ser CentOS (como lo conociamos hasta hace 
poco)

y dificilmente volverá a ser lo que era.


Quedo al pendiente de todos sus atinados comentarios.



___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] CentOS 8 future

[Matthew Miller]

On Fri, Dec 18, 2020 at 03:20:30PM -0500, Joshua Kramer wrote:
> 2027 + 1".  Or maybe it's even RHEL 10 by that point.  So maybe long
> term updates won't go through the CentOS Streams process.

Right, as the plan exists right now, long term updates (after five years)
won't go through CentOS Stream.

-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Joshua Kramer]

On Fri, Dec 18, 2020 at 11:29 AM Johnny Hughes  wrote:

> People who certify things, who certified CentOS Linux for things, are
> free to evaluate and do that with CentOS Stream as well.

This is what makes me think this isn't as bad as people made it out to
be.  (And yeah, I take full responsibility for being one of those
'people' LOL).  For the community, there are two challenges.  One is
very easy to overcome and the other is an unknown.  (Or perhaps it is
a known, once we can get everyone to see from the same perspective.)

Suppose it is June of 2022 and I have been collecting and archiving
all of the various versions of packages that are coming out for CentOS
Stream.  Then, maybe RHEL 8.7 is finalized and hits the mirrors.  I
can analyze the versions of packages that landed in RHEL 8.7.  Then I
can grab those versions from my archive and tag them "8.7".  I could
configure my repositories appropriately and build some ISO images.  Of
course, I couldn't call that "CentOS 8.7" because RedHat has
prohibited that.  But still I could release ISO's of "Enterprise
Respin 8.7".  That is the easy problem to overcome.

But there's still the question of long term support.  Suppose it is
2027 and some major bug is found in OpenSSL.  For RedHat customers,
RedHat will build a package of OpenSSL for RHEL 8.10 that fixes the
bug.  I would guess that such an OpenSSL package would NOT be the same
one that lands in whatever version of RHEL 9 drops in 2027, since the
OpenSSL in RHEL 9 will be based on a later version of OpenSSL and have
more features.  Presumably that RHEL 8 version of OpenSSL would go
through the CentOS Streams process.  Theoretically I could pick up
that version of the package and provide it as an update to "Enterprise
Respin 8.10".

Except... how could that RHEL8 version of OpenSSL go through the
CentOS Streams process?  Based on what we've been told, at that time,
"CentOS Streams" would really be "Whatever version of RHEL 9 drops in
2027 + 1".  Or maybe it's even RHEL 10 by that point.  So maybe long
term updates won't go through the CentOS Streams process.

So the question for the community is how to account for that second issue.

--JK
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Valeri Galtsev]

> On Dec 18, 2020, at 12:14 PM, Matthew Miller  wrote:
> 
> On Fri, Dec 18, 2020 at 08:12:26AM -0500, Konstantin Boyandin via CentOS 
> wrote:
 It's purely a developer's distro.
>>> Has Chris Wright ever recommended CentOS for any purpose other than 
>>> development and testing?
>> Will a Red Hat CTO, in his right mind, ever recommend a free clone of 
>> RHEL for any purpose other than  development and testing?
> 
> Right... he's not "lying", he just has a different audience.
> 
> Red Hat has definitely never ever said in any official way that CentOS Linux
> is acceptable for production uses.

OT: when will I learn to just shut up after arriving at my own decision? 
(rhetoric question)

It doesn’t matter whether RedHat said anything or not. We did use CentOS as 
“binary replica” of RedHat Enterprise (I for one for over decade and a half), 
and did have same level of stability as RedHat Enterprise customers had 
[almost?].Which confirmed the second word in the abbreviated name of the system 
(Community Enterprise OS).

But now there is nothing [in my book] to justify that “Enterprise" word in the 
name.

> And that's not going to change with
> CentOS Stream.
> 
> You should see people's heads spin around like a scene from a horror movie
> when I suggest that people actually do run Fedora operating systems in
> production!

Indeed, that is why many of us who originally switched to Fedora (Hm, when free 
RedHat ceased to exist somewhere near RedHat 8, do people still remember these 
CD/DVD sets?). And shortly after, from Fedora to CentOS.

And no, “development” precursor of RedHat Enterprise which Fedora was is no 
match to “binary replica” of  RedHat Enterprise. And it looks - for not too 
insightful person: myself - that now it will be CentOS a “development” 
precursor of RedHat Enterprise (taking place of Fedora, and potentially same 
production usability as Fedora has). And again, I will be happy for everyone 
who bravely keeps using CentOS (Stream) in production if my feelings are 
gravely wrong. But I myself “chickened out”. Servers: over 6 years ago (to 
FreeBSD, and there no surprises with FreeBSD; but apologies for annoying 
mentioning of the great UNIX successor on this list).

And once again, Thanks a lot for great work, CentOS team! We were enjoying 
excellent fruits of your work,  I - for about decade and a half. And good luck 
to you in future, I know your work will be same great, it is just humble us who 
are unhappy about future arrangement.

Valeri

> 
> -- 
> Matthew Miller
> 
> Fedora Project Leader
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future [ Interesting Article.. ZDNet ]

[John Plemons]

https://www.zdnet.com/article/cloudlinux-to-invest-more-than-a-million-dollar-a-year-into-centos-clone/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Leon Fauster via CentOS]

Am 18.12.20 um 19:14 schrieb Matthew Miller:

On Fri, Dec 18, 2020 at 08:12:26AM -0500, Konstantin Boyandin via CentOS wrote:

It's purely a developer's distro.

Has Chris Wright ever recommended CentOS for any purpose other than
development and testing?

Will a Red Hat CTO, in his right mind, ever recommend a free clone of
RHEL for any purpose other than  development and testing?


Right... he's not "lying", he just has a different audience.

Red Hat has definitely never ever said in any official way that CentOS Linux
is acceptable for production uses. And that's not going to change with
CentOS Stream.

You should see people's heads spin around like a scene from a horror movie
when I suggest that people actually do run Fedora operating systems in
production!



In the different threads here in the list - I noticed that everyone
(not all in quantity) has a different definition of production and 
development "classification". For instance RH: Their devel license

talks about not to use it for production. I am still unsure where
the border for that are? Running a workstation and "producing" output
that have value for me is a production system. As also a fly radar
HA cluster running 24/7 is a production system. Anyway, lets see
what Q1 2021 will bring ...

--
Leon






___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Matthew Miller]

On Fri, Dec 18, 2020 at 10:36:12AM -0600, Christopher Wensink wrote:
> You have been involved in CentOS for a long time.  Would you mind
> explaining the structure here.  Do you work for Red hat full time on
> the CentOS team?  How many people are on that Team that were working
> on CentOS?  Is CentOS structured as a non-profit company with staff
> just working on development of this distribution or is this just a
> group of independent developers working on the same project?  How
> many people are working on active development of on the Red hat team
> / CentOS Organization (if any)?

Johnny can answer this too (and I'll let him cover the specifics about his
own employment) but since I'm here:

Like Fedora, there is no formal legal structure around CentOS as a project.
"A group of developers and stakeholders" is a reasonable description. Red
Hat is the primary sponsor of both projects, and holds the trademarks and
other intellectual property — and takes most legal responsibility and risk.
Red Hat also funds engineering, hardware, and a community budget.

There is no dedicated CentOS team at Red Hat, just as there is no dedicated
Fedora team. There are two highly-relevant teams, though. The first is
Community Platform Engineering, which serves infrastructure and
build tooling for both projects. Second is the Open Source Program Office,
which has a team of community managers and leaders. (Rich Bowen and Marie
Nordin fit in there.) Others are employeed other places — Ben Cotton, who
serves as Program Manager for both Fedora and CentOS Stream — comes to us
from the program management office.

There is no one at Red Hat whose individual job is "develop Fedora".
Instead, like non-RH community members, lots of different people across Red
Hat engineering have "maintain my package in Fedora" as part of their job,
or "work on the Fedora Workstation as a whole". Those people are usually
also responsible for something similar in RHEL.

This is true for RDO for OpenStack or OKD for OpenShift, too. And I'd have
to check for sure but I assume it is also the case for AWX for Ansible.

So, CentOS Linux is something kind of an aberration, because RH was paying
people in the CPE team to spend their time on package builds, even though
they weren't building those packages for RHEL. That's the thing Red Hat
wants to stop doing. With Stream, packages will be actually built by the
engineers who are building them for RHEL. People working on CentOS Stream
_project_ engineering will be more like the way CPE works for Fedora: on
infrastructure and services around that.

As I understand it, this was something like 2-3 full-time equivalent
positions just doing repackaging and associated work. I don't know the
precise number. That might not seem like a lot, but if you've ever scrambled
for req's for a project, you know it's a big deal. Red Hat's RHEL
organization does not actually have a lot of extra fat to spare. But there
is a lot of work that needs to be done to make the CentOS Stream
infrastructure.

So, like I've said before, the given explanation of "we want to actually
focus resources" makes total sense to me as an important driver. Instead of
doing what is essentially duplicative work, people paid to work on CentOS
specifically can act as catalysts, and the hundreds of people in the RHEL
organization who previously didn't look at CentOS at all are now CentOS
developers directly.


-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Matthew Miller]

On Fri, Dec 18, 2020 at 08:12:26AM -0500, Konstantin Boyandin via CentOS wrote:
> >> It's purely a developer's distro.
> > Has Chris Wright ever recommended CentOS for any purpose other than 
> > development and testing?
> Will a Red Hat CTO, in his right mind, ever recommend a free clone of 
> RHEL for any purpose other than  development and testing?

Right... he's not "lying", he just has a different audience.

Red Hat has definitely never ever said in any official way that CentOS Linux
is acceptable for production uses. And that's not going to change with
CentOS Stream.

You should see people's heads spin around like a scene from a horror movie
when I suggest that people actually do run Fedora operating systems in
production!


-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-docs] [centos/centos.org] branch master updated: Fixing simple typo

[git]

This is an automated email from the git hooks/post-receive script.

arrfab pushed a commit to branch master
in repository centos/centos.org.

The following commit(s) were added to refs/heads/master by this push:
 new 1cca569  Fixing simple typo
1cca569 is described below

commit 1cca5696a8d722e6140dc921001038bf425e3aad
Author: Fabian Arrotin 
AuthorDate: Fri Dec 18 18:44:47 2020 +0100

Fixing simple typo

Signed-off-by: Fabian Arrotin 
---
 download/aws-images.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/download/aws-images.md b/download/aws-images.md
index 3581d09..17c2ecc 100644
--- a/download/aws-images.md
+++ b/download/aws-images.md
@@ -12,7 +12,7 @@ CentOS Amazon AMI images
 
 Here is the list of current/up2date AMI images IDs that we made public.
 
-So far we build/update/maintain the following CentOS variants and architecures:
+So far we build/update/maintain the following CentOS variants and 
architectures:
 
  * CentOS Stream 8 (x86_64 and aarch64)
  * CentOS Linux 8 (x86_64 and aarch64)

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] [centos/centos.org] branch master updated: Added Stream 8 AMIs ID

[git]

This is an automated email from the git hooks/post-receive script.

arrfab pushed a commit to branch master
in repository centos/centos.org.

The following commit(s) were added to refs/heads/master by this push:
 new d312beb  Added Stream 8 AMIs ID
d312beb is described below

commit d312bebd01d561324426ad456e4f816d4813fb26
Author: Fabian Arrotin 
AuthorDate: Fri Dec 18 17:52:48 2020 +0100

Added Stream 8 AMIs ID

Signed-off-by: Fabian Arrotin 
---
 _data/aws-images.csv   | 40 
 download/aws-images.md |  1 +
 2 files changed, 41 insertions(+)

diff --git a/_data/aws-images.csv b/_data/aws-images.csv
index 4115771..560ce09 100644
--- a/_data/aws-images.csv
+++ b/_data/aws-images.csv
@@ -1,4 +1,44 @@
 "Version","Region","Architecture","AMI ID","Deploy link"
+" CentOS Stream 8 
","us-east-2","x86_64","ami-0d97ef13c06b05a19","https://console.aws.amazon.com/ec2/v2/home?region=us-east-2#LaunchInstanceWizard:ami=ami-0d97ef13c06b05a19;
+" CentOS Stream 8 
","us-east-1","x86_64","ami-059f1cc52e6c85908","https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-059f1cc52e6c85908;
+" CentOS Stream 8 
","us-west-1","x86_64","ami-0f377b303df4963ab","https://console.aws.amazon.com/ec2/v2/home?region=us-west-1#LaunchInstanceWizard:ami=ami-0f377b303df4963ab;
+" CentOS Stream 8 
","us-west-2","x86_64","ami-0ddc70e50205f89b6","https://console.aws.amazon.com/ec2/v2/home?region=us-west-2#LaunchInstanceWizard:ami=ami-0ddc70e50205f89b6;
+" CentOS Stream 8 
","af-south-1","x86_64","ami-0d9566f77fcfa00e5","https://console.aws.amazon.com/ec2/v2/home?region=af-south-1#LaunchInstanceWizard:ami=ami-0d9566f77fcfa00e5;
+" CentOS Stream 8 
","ap-east-1","x86_64","ami-0b78c5e9b943c50be","https://console.aws.amazon.com/ec2/v2/home?region=ap-east-1#LaunchInstanceWizard:ami=ami-0b78c5e9b943c50be;
+" CentOS Stream 8 
","ap-south-1","x86_64","ami-0c45b2c735e7cbd50","https://console.aws.amazon.com/ec2/v2/home?region=ap-south-1#LaunchInstanceWizard:ami=ami-0c45b2c735e7cbd50;
+" CentOS Stream 8 
","ap-northeast-1","x86_64","ami-01f328f87670cc361","https://console.aws.amazon.com/ec2/v2/home?region=ap-northeast-1#LaunchInstanceWizard:ami=ami-01f328f87670cc361;
+" CentOS Stream 8 
","ap-northeast-2","x86_64","ami-068ba57b029f1a659","https://console.aws.amazon.com/ec2/v2/home?region=ap-northeast-2#LaunchInstanceWizard:ami=ami-068ba57b029f1a659;
+" CentOS Stream 8 
","ap-southeast-1","x86_64","ami-084be8fbdbd21b027","https://console.aws.amazon.com/ec2/v2/home?region=ap-southeast-1#LaunchInstanceWizard:ami=ami-084be8fbdbd21b027;
+" CentOS Stream 8 
","ap-southeast-2","x86_64","ami-0bac9d0b7acaea5d4","https://console.aws.amazon.com/ec2/v2/home?region=ap-southeast-2#LaunchInstanceWizard:ami=ami-0bac9d0b7acaea5d4;
+" CentOS Stream 8 
","ca-central-1","x86_64","ami-02085625d206d7eb3","https://console.aws.amazon.com/ec2/v2/home?region=ca-central-1#LaunchInstanceWizard:ami=ami-02085625d206d7eb3;
+" CentOS Stream 8 
","eu-central-1","x86_64","ami-073a8e22592a4a925","https://console.aws.amazon.com/ec2/v2/home?region=eu-central-1#LaunchInstanceWizard:ami=ami-073a8e22592a4a925;
+" CentOS Stream 8 
","eu-west-1","x86_64","ami-090b347d44e58c47b","https://console.aws.amazon.com/ec2/v2/home?region=eu-west-1#LaunchInstanceWizard:ami=ami-090b347d44e58c47b;
+" CentOS Stream 8 
","eu-west-2","x86_64","ami-0109cc95c55669f94","https://console.aws.amazon.com/ec2/v2/home?region=eu-west-2#LaunchInstanceWizard:ami=ami-0109cc95c55669f94;
+" CentOS Stream 8 
","eu-west-3","x86_64","ami-0718ab19524d69434","https://console.aws.amazon.com/ec2/v2/home?region=eu-west-3#LaunchInstanceWizard:ami=ami-0718ab19524d69434;
+" CentOS Stream 8 
","eu-south-1","x86_64","ami-0138a15900e393a17","https://console.aws.amazon.com/ec2/v2/home?region=eu-south-1#LaunchInstanceWizard:ami=ami-0138a15900e393a17;
+" CentOS Stream 8 
","eu-north-1","x86_64","ami-08ec5ec25b9b7d5c5","https://console.aws.amazon.com/ec2/v2/home?region=eu-north-1#LaunchInstanceWizard:ami=ami-08ec5ec25b9b7d5c5;
+" CentOS Stream 8 
","me-south-1","x86_64","ami-01b5a0aafcc2288c2","https://console.aws.amazon.com/ec2/v2/home?region=me-south-1#LaunchInstanceWizard:ami=ami-01b5a0aafcc2288c2;
+" CentOS Stream 8 
","sa-east-1","x86_64","ami-0f0c3edb7c1e023da","https://console.aws.amazon.com/ec2/v2/home?region=sa-east-1#LaunchInstanceWizard:ami=ami-0f0c3edb7c1e023da;
+" CentOS Stream 8 
","us-east-2","aarch64","ami-0deb895048c4f105b","https://console.aws.amazon.com/ec2/v2/home?region=us-east-2#LaunchInstanceWizard:ami=ami-0deb895048c4f105b;
+" CentOS Stream 8 
","us-east-1","aarch64","ami-0a311be1169cd6581","https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-0a311be1169cd6581;
+" CentOS Stream 8 
","us-west-1","aarch64","ami-06872c0074e26d7a6","https://console.aws.amazon.com/ec2/v2/home?region=us-west-1#LaunchInstanceWizard:ami=ami-06872c0074e26d7a6;
+" CentOS Stream 8 

Re: [CentOS] CentOS 8 future

[Christopher Wensink]

Johnny,

You have been involved in CentOS for a long time.  Would you mind 
explaining the structure here.  Do you work for Red hat full time on the 
CentOS team?  How many people are on that Team that were working on 
CentOS?  Is CentOS structured as a non-profit company with staff just 
working on development of this distribution or is this just a group of 
independent developers working on the same project?  How many people are 
working on active development of on the Red hat team / CentOS 
Organization (if any)?


Thanks for your time.

Chris


On 12/18/2020 10:28 AM, Johnny Hughes wrote:

On 12/17/20 7:54 PM, Konstantin Boyandin via CentOS wrote:

On 16.12.2020 22:50, Johnny Hughes wrote:

On 12/15/20 9:59 PM, Joshua Kramer wrote:

On Tue, Dec 15, 2020 at 7:41 PM Johnny Hughes  wrote:


$250K is not even close.  That is one employee, when you also take into
account unemployment insurance, HR, medical insurance etc.  now multiply
that by 8.  Now, outfit those 8 employees to work from home .. all over
the world, different countries, different laws.

I'm genuinely curious about something, and this is mostly academic
since it's probably the subject of proprietary discussions within
RedHat.  Presumably, RedHat had a build pipeline for RHEL that worked
well for them, by supplying alpha/beta releases of point releases to
their customers and giving them time to "cook" before releasing those
point releases into production.  Why would RedHat invest millions more
in buying the CentOS process just to have CentOS act as the beta?

Why did they change the development process of RHEL ..

Because they want to do the development in the community.  The current
process of RHEL development is closed .. they want it to be open.  It is
that simple.

I think Stream is also very usable as a distro.  I think it will be just
as usable as CentOS Linux is now.

It's usable, as Fedora is certainly usable - in its separate use cases.
It's not bug-for-bug copy of current RHEL, so it's *not* as usable as
CentOS Linux was.


It is not a beta .. I keep saying that.  Before a .0 release (the main,
or first, main reelase) is a beta.  Point releases do not really need
betas .. certainly not open to anyone other than customers.  Now CentOS
Stream is available all the time to everyone, customer or not.  Once the
full infrastructure is in place, everyone (not just RHEL customers) can
provide feed back and bugs, do pull requests, etc.

Now please tell me whether Chris Wright was lying when saying the below
to ZDNet:

"To be exact, CentOS Stream is an upstream development platform for
ecosystem developers. It will be updated several times a day. This is
not a production operating system. It's purely a developer's distro."

It's purely a developer's distro. Shall I explain difference between a
developer's distro and the one suitable for production servers (a
rhetoric question)?


Of course he wasn't lying.  The purpose of ANY CentOS release from a Red
Hat perspective, is as a developer release.  Red Hat has never produced
CentOS to be used in production for any reason.

It is ALSO completely free to use however YOU want to use it.  As is
CentOS Stream.  If it meets your requirements, you can use it.  Stream
is no different.

People who certify things, who certified CentOS Linux for things, are
free to evaluate and do that with CentOS Stream as well.

Is it ever going to be like it was before .. no.  If that is a deal
breaker for you, OK.  Then you can't use CentOS any longer.  Great, if
you can't use it, then use something else.

All I can do is what I can do .. All you can do is what you can do.
What is absolutely not helpful is continued complaining.  A decision
was made. It is implemented. CentOS Stream is CentOS Stream.

If you never want to use CentOS again .. great, don't use it.  I can't
make people use CentOS if they don't want to.

What I will do is what I have been doing for the last 17 years .. I will
do the best job I can to make the things I can build for any version of
CentOS Linux (or Stream) the best they can be.  If people can use them,
OK.  If they can't OK.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


--
Christopher Wensink
IS Administrator
Five Star Plastics, Inc
1339 Continental Drive
Eau Claire, WI 54701
Office:  715-831-1682
Mobile:  715-563-3112
Fax:  715-831-6075
cwens...@five-star-plastics.com
www.five-star-plastics.com

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] CentOS Governing Board: Do not destroy CentOS by using it as a RHEL upstream

[José Roberto Alas]

Excelente propuesta

El jue, 17 de dic. de 2020 a la(s) 20:28, Peter Q. (btove...@gmail.com)
escribió:

> Bonjour,
> Je viens de signer la pétition "CentOS Governing Board: Do not destroy
> CentOS by using it as a RHEL upstream" et je souhaitais savoir si vous
> voudriez nous aider en ajoutant votre signature.
>
> Notre objectif est d'atteindre 10 000 signatures et nous avons besoin de
> plus de soutiens. Pour en savoir plus et pour signer, c'est ici:
>
> http://chng.it/Pg5TsFb69N
>
> Merci !
> Qz
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>


-- 
Saludos,
cheperobert
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] CentOS 8 future

[Johnny Hughes]

On 12/17/20 7:54 PM, Konstantin Boyandin via CentOS wrote:
> On 16.12.2020 22:50, Johnny Hughes wrote:
>> On 12/15/20 9:59 PM, Joshua Kramer wrote:
>>> On Tue, Dec 15, 2020 at 7:41 PM Johnny Hughes  wrote:
>>>
 $250K is not even close.  That is one employee, when you also take into
 account unemployment insurance, HR, medical insurance etc.  now multiply
 that by 8.  Now, outfit those 8 employees to work from home .. all over
 the world, different countries, different laws.
>>>
>>> I'm genuinely curious about something, and this is mostly academic
>>> since it's probably the subject of proprietary discussions within
>>> RedHat.  Presumably, RedHat had a build pipeline for RHEL that worked
>>> well for them, by supplying alpha/beta releases of point releases to
>>> their customers and giving them time to "cook" before releasing those
>>> point releases into production.  Why would RedHat invest millions more
>>> in buying the CentOS process just to have CentOS act as the beta?
>>
>> Why did they change the development process of RHEL ..
>>
>> Because they want to do the development in the community.  The current
>> process of RHEL development is closed .. they want it to be open.  It is
>> that simple.
>>
>> I think Stream is also very usable as a distro.  I think it will be just
>> as usable as CentOS Linux is now.
> 
> It's usable, as Fedora is certainly usable - in its separate use cases. 
> It's not bug-for-bug copy of current RHEL, so it's *not* as usable as 
> CentOS Linux was.
> 
>> It is not a beta .. I keep saying that.  Before a .0 release (the main,
>> or first, main reelase) is a beta.  Point releases do not really need
>> betas .. certainly not open to anyone other than customers.  Now CentOS
>> Stream is available all the time to everyone, customer or not.  Once the
>> full infrastructure is in place, everyone (not just RHEL customers) can
>> provide feed back and bugs, do pull requests, etc.
> 
> Now please tell me whether Chris Wright was lying when saying the below 
> to ZDNet:
> 
> "To be exact, CentOS Stream is an upstream development platform for 
> ecosystem developers. It will be updated several times a day. This is 
> not a production operating system. It's purely a developer's distro."
> 
> It's purely a developer's distro. Shall I explain difference between a 
> developer's distro and the one suitable for production servers (a 
> rhetoric question)?
> 

Of course he wasn't lying.  The purpose of ANY CentOS release from a Red
Hat perspective, is as a developer release.  Red Hat has never produced
CentOS to be used in production for any reason.

It is ALSO completely free to use however YOU want to use it.  As is
CentOS Stream.  If it meets your requirements, you can use it.  Stream
is no different.

People who certify things, who certified CentOS Linux for things, are
free to evaluate and do that with CentOS Stream as well.

Is it ever going to be like it was before .. no.  If that is a deal
breaker for you, OK.  Then you can't use CentOS any longer.  Great, if
you can't use it, then use something else.

All I can do is what I can do .. All you can do is what you can do.
What is absolutely not helpful is continued complaining.  A decision
was made. It is implemented. CentOS Stream is CentOS Stream.

If you never want to use CentOS again .. great, don't use it.  I can't
make people use CentOS if they don't want to.

What I will do is what I have been doing for the last 17 years .. I will
do the best job I can to make the things I can build for any version of
CentOS Linux (or Stream) the best they can be.  If people can use them,
OK.  If they can't OK.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Questions about Stream

[Johnny Hughes]

On 12/17/20 3:04 AM, edward via CentOS wrote:
> 
> On 2020-12-17 13:30, Johnny Hughes wrote:
>> Red Hat is going to an open development model for RHEL using CentOS
>> Stream.
> 
> 
> will it be something similar  hp is doing with clearOS development?
> 
> https://www.clearos.com/products/clearos-editions/clearos-7-compare-editions
> 


Well .. the centos stream will be available for free during it's lifetime.

Red Hat is working on more subscription (or even free) models for centos
users via:  centos-questi...@redhat.com

I don't know what those models will be for RHEL .. I don't work on that
team inside Red Hat.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] YUM problem

[Keith Christian]

system-config-lvm appears to be deprecated:

https://duckduckgo.com/?q=centos+%22system-config-lvm%22=ffab=web
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 8 future

[Konstantin Boyandin via CentOS]

On 18.12.2020 14:46, Gordon Messmer wrote:
> On 12/17/20 5:54 PM, Konstantin Boyandin via CentOS wrote:
>> It's purely a developer's distro.
> 
> Has Chris Wright ever recommended CentOS for any purpose other than 
> development and testing?

Will a Red Hat CTO, in his right mind, ever recommend a free clone of 
RHEL for any purpose other than  development and testing?

>> Shall I explain difference between a
>> developer's distro and the one suitable for production servers (a
>> rhetoric question)?
> 
> How did you imagine you would look when you asked a CentOS maintainer if 
> he understands the importance of the thing he's been doing for 17 years?

That's completely unrelated to my statements.

Please do worry about your own look. Thanks.

-- 
Sincerely,

Konstantin Boyandin
system administrator (ProWide Labs Ltd. - IPHost Network Monitor)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-docs] [centos/centos.org] 02/02: Adding new AltusHost sponsor link and logo on sponsors section

[git]

This is an automated email from the git hooks/post-receive script.

arrfab pushed a commit to branch master
in repository centos/centos.org.

commit 30b7babd68a24e3045c4aee12f4116103811876e
Author: Fabian Arrotin 
AuthorDate: Fri Dec 18 13:02:04 2020 +0100

Adding new AltusHost sponsor link and logo on sponsors section

Signed-off-by: Fabian Arrotin 
---
 _sponsors/altushost.md|   7 +++
 assets/img/sponsors/altushost.png | Bin 0 -> 10436 bytes
 2 files changed, 7 insertions(+)

diff --git a/_sponsors/altushost.md b/_sponsors/altushost.md
new file mode 100644
index 000..f76ed90
--- /dev/null
+++ b/_sponsors/altushost.md
@@ -0,0 +1,7 @@
+---
+name: AltusHost
+country: usa
+logo: /assets/img/sponsors/altushost.png
+address: https://www.altushost.com/
+---
+
diff --git a/assets/img/sponsors/altushost.png 
b/assets/img/sponsors/altushost.png
new file mode 100644
index 000..db87303
Binary files /dev/null and b/assets/img/sponsors/altushost.png differ

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] [centos/centos.org] 01/02: Modified Packet.net logo with Equinix (acquisition)

[git]

This is an automated email from the git hooks/post-receive script.

arrfab pushed a commit to branch master
in repository centos/centos.org.

commit f2b8ce86e603424761a2e3cf085c676c1c38541f
Author: Fabian Arrotin 
AuthorDate: Fri Dec 18 13:01:26 2020 +0100

Modified Packet.net logo with Equinix (acquisition)

Signed-off-by: Fabian Arrotin 
---
 _sponsors/equinix.md|   7 +++
 _sponsors/packet.md |   7 ---
 assets/img/sponsors/equinix.png | Bin 0 -> 1750 bytes
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/_sponsors/equinix.md b/_sponsors/equinix.md
new file mode 100644
index 000..411d1eb
--- /dev/null
+++ b/_sponsors/equinix.md
@@ -0,0 +1,7 @@
+---
+name: Equinix Metal
+country: usa
+logo: /assets/img/sponsors/equinix.png
+address: https://metal.equinix.com/
+---
+
diff --git a/_sponsors/packet.md b/_sponsors/packet.md
deleted file mode 100644
index 3a23ebf..000
--- a/_sponsors/packet.md
+++ /dev/null
@@ -1,7 +0,0 @@

-name: Packet
-country: usa
-logo: /assets/img/sponsors/packet.png
-address: https://www.packet.com/

-
diff --git a/assets/img/sponsors/equinix.png b/assets/img/sponsors/equinix.png
new file mode 100644
index 000..8033ed2
Binary files /dev/null and b/assets/img/sponsors/equinix.png differ

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] [centos/centos.org] branch master updated (537e0b3 -> 30b7bab)

[git]

This is an automated email from the git hooks/post-receive script.

arrfab pushed a change to branch master
in repository centos/centos.org.

from 537e0b3  Remove Ralph, now that minutes are published.
 new f2b8ce8  Modified Packet.net logo with Equinix (acquisition)
 new 30b7bab  Adding new AltusHost sponsor link and logo on sponsors section

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _sponsors/altushost.md|   7 +++
 _sponsors/equinix.md  |   7 +++
 _sponsors/packet.md   |   7 ---
 assets/img/sponsors/altushost.png | Bin 0 -> 10436 bytes
 assets/img/sponsors/equinix.png   | Bin 0 -> 1750 bytes
 5 files changed, 14 insertions(+), 7 deletions(-)
 create mode 100644 _sponsors/altushost.md
 create mode 100644 _sponsors/equinix.md
 delete mode 100644 _sponsors/packet.md
 create mode 100644 assets/img/sponsors/altushost.png
 create mode 100644 assets/img/sponsors/equinix.png

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-es] CentOS Governing Board: Do not destroy CentOS by using it as a RHEL upstream

[David González Romero]

Ya firmé, pero lo que pasa es que CentOS está agarrada por los hue por
el tema que Red Hat es dueño de ellos... así que en si Red Hat dice no, es
no...

Saludos,
David

El jue, 17 dic 2020 a las 23:28, Peter Q. () escribió:

> Bonjour,
> Je viens de signer la pétition "CentOS Governing Board: Do not destroy
> CentOS by using it as a RHEL upstream" et je souhaitais savoir si vous
> voudriez nous aider en ajoutant votre signature.
>
> Notre objectif est d'atteindre 10 000 signatures et nous avons besoin de
> plus de soutiens. Pour en savoir plus et pour signer, c'est ici:
>
> http://chng.it/Pg5TsFb69N
>
> Merci !
> Qz
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-es] CentOS rip?

[David González Romero]

Bueno no estoy de acuerdo Rene, una de las virtudes del software libre es
que puede ser gratis... y ojo no digo que es gratis, sino que puede ser
gratis. Para existe el concepto de DONACIÓN cosa que nosotros los latinos
nos cuesta mucho o un poco...

Saludos,
David

El jue, 17 dic 2020 a las 21:00, Rene L.A. ()
escribió:

>
>
> El 17/12/2020 a las 01:41 p. m., David González Romero escribió:
>
>
>
> El lun, 14 dic 2020 a las 14:36, Rene L.A. ()
> escribió:
>
>> Tal vez  debamos, nosotros, los usuarios, reflexionar sobre ciertos temas.
>> 1) ¿Habrá algún proyecto que mantenga en el largo plazo sin la
>> contribución de la mayoría de los usuarios?
>> Pienso que no.
>>
> Es que esa es la política o filosofía del Software Libre... hasta un Beta
> Tester es importante en el proceso. No todos tenemos que ser programadores.
>
>
>
>> 2) Debemos contribuir mas.
>> Estoy de acuerdo que muchos lo usamos porque no hacemos gran negocio con
>> él, pero  todos podemos en alguna medida contribuir.
>>
> Yo pienso al contrario habemos quienes hemos hecho muchos negocios con
> CentOS y era precisamente la ventaja de poder hacer negocio con un software
> de calidad y sin costo directo sobre el software.
>
>
>> Por mas filantrópico que sea el software libre, necesita recursos.
>>
> Eso es claro, por eso hay quien contribuyen no solo con código, sino con
> donaciones... o eventualmente algún negocio...
>
> En fin seguiremos esperando a ver que pasa, lo único malo de esto y es lo
> que me huele mal es la cuestión de estabilidad en producción; no es otra
> cosa, quizá a nivel de usuario empresarial o pequeños servicios sea super;
> pero algo con cierta estabilidad y requerimientos de producción altos; no
> se puede confiar en una cuestión de orden no estable. No se pienso muchas
> cosas... ahora lo que más me preocupan son mis centrales telefónicas
> Isabel...
>
> Saludos,
> David
>
>
> Así es David. Pero también, esos que no son de pequeñas empresas  y
> pequeños servicios puden (y deberían) pagar algo como RedHat.
> Un negocio, si es negocio, debe dar para pagar sus insumos,  si no, sería
> como algo subsidiado.
> Creo que es algo que debemos meditar.
> Si mi negocio, es tal porque no pago impuestos o no pago algunos servicios
> que ocupo para producir, no es un buen negocio.
>
> Por otra parte, quien inicia, quien estudia, no puede pagar. Allí es
> necesario ése subsidio y esa oportunidad.
> Insisto: creo que nos debemos re plantear algunas cosas.
> r.lara
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS] YUM problem

[Gestió Servidors]

Hi,

I'm trying to find a YUM package. My system runs a CentOS-7.2.1511 (yes, it's a 
old version, but some software is "stable" with this CentOS version). Now, I'm 
looking for a package with YUM. When a run "yum provides */system-config-lvm", 
I get this error:
[root@mysystem ~]# yum provides */system-config-lvm
Complementos cargados:fastestmirror, langpacks, priorities
Loading mirror speeds from cached hostfile
* epel: mirror.uv.es
* extras: ftp.csuc.cat
* updates: ftp.csuc.cat
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in 
yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 584, in doCommands
return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, 
self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1557, in doCommand
return base.provides(extcmds)
  File "/usr/share/yum-cli/cli.py", line 1619, in provides
callback_has_matchfor=True)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3538, in 
searchPackageProvides
tagdata = getattr(po, tag)
  File "/usr/lib/python2.7/site-packages/yum/packages.py", line 668, in 
filelist = property(fget=lambda self: self.returnFileEntries(ftype='file'))
  File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1504, in 
returnFileEntries
self._loadFiles()
  File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1478, in 
_loadFiles
files = self.hdr['filenames']
_rpm.error: invalid header data

I have run "yum clean metadata" and "yum clean all", but error message still 
appears.

What can I do?

Thanks.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] MTU report question

[Peter Kjellström]

On Mon, 14 Dec 2020 14:46:30 +0100
Patrick Bégou  wrote:

> Hi,
> 
> I'm deploying a CentOS8 (not stream ) cluster and I have a question
> about MTU on the interfaces. I have a connectX6 Mellanox interface
> where I need IBoIP setup.
> I've setup this interface via nmcli and set the MTU to 65520 with:
> 
> nmcli connection modify ib0 mtu 65520
> nmcli connection up ib0
> 
> Running "nmcli connection show ib0" report:
> 
> infiniband.mtu: 65520
> 
> But "ip addr show ib0" report a mtu of 2044:
> 
> 6: ib0:  *mtu 2044 *qdisc mq
> state UP group default qlen 256

2044 is what you get with DATAGRAM mode and the native IB running with
2K packages. You can get 4092 IPoIB MTU with 4K IB. And you do want to
run 4K native IB in general.

To run 64K MTU you need to switch from DATAGRAM mode to CONNECTED mode
for IPoIB. CONNECTED mode give the highest single stream bandwidth
typically but may not give best overall performance (vs 4092 DATAGRAM
mode).

Cheers,
 Peter K
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos