kernel-4.18.0-326.el8 is being pushed to the mirrors now.
On Wed, Jul 28, 2021 at 2:42 PM Brian Stinson wrote:
>
> Carl summarized really well how code moves through RHEL and CentOS
> Stream, and we’re working on making sure we publish a build that has
> made it through the usual set of RHEL
On 7/28/2021 1:57 PM, Scott Techlist wrote:
Is that an improvement? I'm still running Centos7 so I'm not familiar with it.
https://ungleich.ch/en-us/cms/blog/2018/08/18/iptables-vs-nftables/
___
CentOS mailing list
CentOS@centos.org
>> For what it’s worth, if you use the fail2ban-firewalld package, it uses
>> ipset rather than iptables, which is more efficient.
>
>That’s in CentOS 7 though.
>CentOS 8 firewalld uses nft instead of the older netfilter (iptables/ipset)
>code.
Is that an improvement? I'm still running
Carl summarized really well how code moves through RHEL and CentOS
Stream, and we’re working on making sure we publish a build that has
made it through the usual set of RHEL tests. -326 is a possible
candidate here.
Think about CentOS Stream as the development location for the next-minor
release
Thank you for the update and your candor on this.
Jul 28, 2021, 9:44 AM by c...@redhat.com:
> It's being worked on. RHEL maintainers can fix things independently
> in different minor version branches. The fix was applied to the
> internal 8.4 branch while it was under embargo. It has since
It's being worked on. RHEL maintainers can fix things independently
in different minor version branches. The fix was applied to the
internal 8.4 branch while it was under embargo. It has since been
released in RHEL 8.4, which allowed it to be rebuilt in CentOS Linux
8. CentOS Stream 8 is
On Wed, Jul 28, 2021 at 08:56:29AM -0400, mario juliano grande-balletta wrote:
>
> Anyone using or working with VzLinux, seems to be an upstream distro of
> CentOS/RHEL and no vendors involved
> Would love to hear experiences.
> thanks!
Please start a new thread rather than replying to an
On Wed, Jul 28, 2021 at 09:16:48AM -0500, Jon Pruente wrote:
> No vendors? It's the product of a single vendor, the long running Linux
> hypervisor platform creator Virtuozzo. They made it to run on their OpenVZ
> hypervisor platform.
>
>
Thanks John! Appreciate it.
a co-worker uploaded an appliance into customer vCenter and it was
VzLinux, never saw it or heard of it before, didn't have time to
research, just thought I would ask the group here for a quick answer,
thanks!
On Wed, 2021-07-28 at 09:16 -0500, Jon Pruente wrote:
On Wed, Jul 28, 2021 at 7:56 AM mario juliano grande-balletta <
mario.balle...@gmail.com> wrote:
> Anyone using or working with VzLinux, seems to be an upstream distro of
> CentOS/RHEL and no vendors involved
> Would love to hear experiences.
> thanks!
> :-)
>
No vendors? It's the
On 28.07.21 14:44, Jonathan Billings wrote:
On Jul 27, 2021, at 16:43, H wrote:
|Running CentOS 7. I was under the impression - seemingly mistaken - that by
adding a rule to /etc/hosts.deny such as ALL: aaa.bbb.ccc.* would ban all
attempts from that network segment to connect to the
Anyone using or working with VzLinux, seems to be an upstream distro of
CentOS/RHEL and no vendors involved
Would love to hear experiences.
thanks!
:-)
On Wed, 2021-07-28 at 08:49 -0400, Jonathan Billings wrote:
> On Jul 28, 2021, at 08:44, Jonathan Billings
> wrote:
>
> For what
On Jul 28, 2021, at 08:44, Jonathan Billings wrote:
>
> For what it’s worth, if you use the fail2ban-firewalld package, it uses ipset
> rather than iptables, which is more efficient.
That’s in CentOS 7 though. CentOS 8 firewalld uses nft instead of the older
netfilter (iptables/ipset) code.
On Jul 27, 2021, at 16:43, H wrote:
>
> |Running CentOS 7. I was under the impression - seemingly mistaken - that by
> adding a rule to /etc/hosts.deny such as ALL: aaa.bbb.ccc.* would ban all
> attempts from that network segment to connect to the server, ie before
> fail2ban would
I am trying to "add" an entry to grub.conf on CentOS 6.3 - and change the
default=0 to default=1
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and
On Tue, 27 Jul 2021 at 17:17, Pete Biggs wrote:
>
> On Tue, 2021-07-27 at 16:43 -0400, H wrote:
> > > Running CentOS 7. I was under the impression - seemingly mistaken -
> > > that by adding a rule to /etc/hosts.deny such as ALL: aaa.bbb.ccc.*
> > > would ban all attempts from that network
On Tue, 27 Jul 2021 at 16:43, H wrote:
>
> |Running CentOS 7. I was under the impression - seemingly mistaken - that by
> adding a rule to /etc/hosts.deny such as ALL: aaa.bbb.ccc.* would ban all
> attempts from that network segment to connect to the server, ie before
> fail2ban would
17 matches
Mail list logo
