Il 09/08/20 10:40, Johnny Hughes ha scritto:
On 8/9/20 2:49 AM, Alessandro Baggi wrote:
Il 07/08/20 17:39, Leon Fauster via CentOS ha scritto:
Am 07.08.20 um 17:17 schrieb Alessandro Baggi:
Hi Johnny,
what is the current status of the notification tool for security
updates on C8? There are
On 8/9/20 2:49 AM, Alessandro Baggi wrote:
>
> Il 07/08/20 17:39, Leon Fauster via CentOS ha scritto:
>> Am 07.08.20 um 17:17 schrieb Alessandro Baggi:
>>>
>>> Hi Johnny,
>>>
>>> what is the current status of the notification tool for security
>>> updates on C8? There are possibilities to get
Il 07/08/20 17:39, Leon Fauster via CentOS ha scritto:
Am 07.08.20 um 17:17 schrieb Alessandro Baggi:
Hi Johnny,
what is the current status of the notification tool for security
updates on C8? There are possibilities to get soon announces on ML
for EL8?
Would be great have the tool
Hi Alessandro,
Compared to Microsoft , both RH and SuSE are awesome.
You always need a patch management strategy with locked repos
(spacewalk/pulp) which can be tested on less important systems, prior
deployment on Prod.
Keep in mind that Secureboot is hard to deploy in Virtual
Il 07/08/20 15:46, Stephen John Smoogen ha scritto:
On Fri, 7 Aug 2020 at 09:15, Chris Adams wrote:
Once upon a time, Alessandro Baggi said:
you are right but is not UEFI a standard and it shouldn't work the
same on several vendors? I ask this because this patch broken all my
uefi
Am 07.08.20 um 17:17 schrieb Alessandro Baggi:
Hi Johnny,
what is the current status of the notification tool for security updates
on C8? There are possibilities to get soon announces on ML for EL8?
Would be great have the tool working.
As I understand some kind of mapping must be
Il 07/08/20 14:53, Johnny Hughes ha scritto:
On 8/7/20 5:30 AM, Phil Perry wrote:
On 07/08/2020 10:01, Johnny Hughes wrote:
On 8/7/20 3:46 AM, Nicolas Kovacs wrote:
Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
Probably many users have not updated their machines between the bug
release
Le 07/08/2020 à 11:01, Johnny Hughes a écrit :
>
> Microsoft, Debian, Ubuntu and others also had issues with this .. so if
> you are losing trust, you are losing it with all OS vendors WRT this issue.
>
> All I can say is .. this issue was the hardest thing I have been
> involved with since
> On 8/7/20 5:30 AM, Phil Perry wrote:
>> On 07/08/2020 10:01, Johnny Hughes wrote:
>>> On 8/7/20 3:46 AM, Nicolas Kovacs wrote:
Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
> Probably many users have not updated their machines between the bug
> release and
> the resolution
> Once upon a time, Alessandro Baggi said:
>> you are right but is not UEFI a standard and it shouldn't work the
>> same on several vendors? I ask this because this patch broken all my
>> uefi workstations.
>
> The great thing about standards is there's so many to choose from! Also
> relevant:
On Fri, 7 Aug 2020 at 09:15, Chris Adams wrote:
>
> Once upon a time, Alessandro Baggi said:
> > you are right but is not UEFI a standard and it shouldn't work the
> > same on several vendors? I ask this because this patch broken all my
> > uefi workstations.
>
> The great thing about standards
Once upon a time, Alessandro Baggi said:
> you are right but is not UEFI a standard and it shouldn't work the
> same on several vendors? I ask this because this patch broken all my
> uefi workstations.
The great thing about standards is there's so many to choose from! Also
relevant:
On 8/7/20 5:30 AM, Phil Perry wrote:
> On 07/08/2020 10:01, Johnny Hughes wrote:
>> On 8/7/20 3:46 AM, Nicolas Kovacs wrote:
>>> Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
Probably many users have not updated their machines between the bug
release and
the resolution (thanks
On 07/08/2020 10:01, Johnny Hughes wrote:
On 8/7/20 3:46 AM, Nicolas Kovacs wrote:
Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
Probably many users have not updated their machines between the bug release and
the resolution (thanks to your fast apply in the weekend, thank you) and many
Il 07/08/20 10:47, Johnny Hughes ha scritto:
On 8/7/20 2:40 AM, Alessandro Baggi wrote:
Il 07/08/20 08:22, Johnny Hughes ha scritto:
"How on earth could this have passed Q & A ?"
Hi Johnny,
Niki's question is spread, legit, in the thoughts in many and many users
so don't see this as an
Il 07/08/20 10:46, Nicolas Kovacs ha scritto:
Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
Probably many users have not updated their machines between the bug release and
the resolution (thanks to your fast apply in the weekend, thank you) and many
update their centos machines on a 2
On 8/7/20 3:46 AM, Nicolas Kovacs wrote:
> Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
>> Probably many users have not updated their machines between the bug release
>> and
>> the resolution (thanks to your fast apply in the weekend, thank you) and many
>> update their centos machines on a
On 8/7/20 2:40 AM, Alessandro Baggi wrote:
>
> Il 07/08/20 08:22, Johnny Hughes ha scritto:
>>> "How on earth could this have passed Q & A ?"
>
> Hi Johnny,
> Niki's question is spread, legit, in the thoughts in many and many users
> so don't see this as an attack. Many and many users,though
Le 07/08/2020 à 09:40, Alessandro Baggi a écrit :
> Probably many users have not updated their machines between the bug release
> and
> the resolution (thanks to your fast apply in the weekend, thank you) and many
> update their centos machines on a 2 months base (if not worst). I think also
>
Il 07/08/20 08:22, Johnny Hughes ha scritto:
"How on earth could this have passed Q & A ?"
Hi Johnny,
Niki's question is spread, legit, in the thoughts in many and many users
so don't see this as an attack. Many and many users,though really "if
this was tested before release" and I think
On 8/6/20 8:57 AM, Nicolas Kovacs wrote:
> Le 04/08/2020 à 08:31, lpeci a écrit :
>> I had the same problem with my UEFI bios machine and I fixed it so for
>> Centos 7:
>>
>> 1) Boot from an rescue linux usb
>>
>> 2) When the rescue system is running:
>>
>> 2.1) #chroot /mnt/sysimage
>>
>> 3)
Le 06/08/2020 à 16:53, Kenneth Porter a écrit :
> A practical equivalent is simply to avoid applying updates for a week to see
> if
> someone else gets burned by them. I'm already waiting for a weekend so I don't
> disrupt work in case a catastrophe happens, and I wait at least a week and
> watch
On Thu, Aug 06, 2020 at 03:57:56PM +0200, Nicolas Kovacs wrote:
> Le 04/08/2020 à 08:31, lpeci a écrit :
> > I had the same problem with my UEFI bios machine and I fixed it so for
> > Centos 7:
While this worked for me, it might not work for you...
My "solution" was to boot the previous kernel,
On 8/6/2020 7:25 AM, Simon Matter via CentOS wrote:
The only real solution I can think of to prevent this would be to make
preview versions of updates available to the public so that a lot of
people can test them on their hardware, hopefully spare hardware, and give
feedback.
A practical
> Le 04/08/2020 à 08:31, lpeci a écrit :
>> I had the same problem with my UEFI bios machine and I fixed it so for
>> Centos 7:
>>
>> 1) Boot from an rescue linux usb
>>
>> 2) When the rescue system is running:
>>
>> 2.1) #chroot /mnt/sysimage
>>
>> 3) Config network:
>>
>> 3.1) # ip addr
Le 04/08/2020 à 08:31, lpeci a écrit :
> I had the same problem with my UEFI bios machine and I fixed it so for Centos
> 7:
>
> 1) Boot from an rescue linux usb
>
> 2) When the rescue system is running:
>
> 2.1) #chroot /mnt/sysimage
>
> 3) Config network:
>
> 3.1) # ip addr add
On 8/4/20 10:45 AM, ja wrote:
> On Tue, 2020-08-04 at 10:36 -0500, Chris Adams wrote:
>> Once upon a time, Johnny Hughes said:
>>> The issues should now be resolved.
>>>
>>> If you just mount /mnt/sysimage, set an ip address and upgrade (to get
>>> th new shim) .. then:
>>>
>>> yum reinstall
>>
On Tue, 2020-08-04 at 10:36 -0500, Chris Adams wrote:
> Once upon a time, Johnny Hughes said:
> > The issues should now be resolved.
> >
> > If you just mount /mnt/sysimage, set an ip address and upgrade (to get
> > th new shim) .. then:
> >
> > yum reinstall
>
> I'm curious - why does the
Once upon a time, Johnny Hughes said:
> The issues should now be resolved.
>
> If you just mount /mnt/sysimage, set an ip address and upgrade (to get
> th new shim) .. then:
>
> yum reinstall
I'm curious - why does the kernel need to be reinstalled? The shim-x64
package installs its files
On 8/4/20 9:51 AM, Johnny Hughes wrote:
> On 8/4/20 1:31 AM, lpeci wrote:
>> Hi all,
>>
>> I had the same problem with my UEFI bios machine and I fixed it so for
>> Centos 7:
>>
>> 1) Boot from an rescue linux usb
>>
>> 2) When the rescue system is running:
>>
>> 2.1) #chroot /mnt/sysimage
>>
On 8/4/20 1:31 AM, lpeci wrote:
> Hi all,
>
> I had the same problem with my UEFI bios machine and I fixed it so for
> Centos 7:
>
> 1) Boot from an rescue linux usb
>
> 2) When the rescue system is running:
>
> 2.1) #chroot /mnt/sysimage
>
> 3) Config network:
>
> 3.1) # ip addr add
On 8/4/20 2:31 AM, lpeci wrote:
3) Config network:
3.1) # ip addr add X.X.X.X/X dev X
3.2) # ip route add default via X.X.X.X <--- default router
While I appreciate the thoughts behind this step in the instructions,
and I thank you for the post that will be useful to those
> Am 04.08.2020 um 08:31 schrieb lpeci :
>
> Hi all,
>
> I had the same problem with my UEFI bios machine and I fixed it so for Centos
> 7:
>
> 1) Boot from an rescue linux usb
>
> 2) When the rescue system is running:
>
> 2.1) #chroot /mnt/sysimage
>
> 3) Config network:
>
>
Hi all,
I had the same problem with my UEFI bios machine and I fixed it so for
Centos 7:
1) Boot from an rescue linux usb
2) When the rescue system is running:
2.1) #chroot /mnt/sysimage
3) Config network:
3.1) # ip addr add X.X.X.X/X dev X
3.2) # ip route add default via
Le 03/08/2020 à 19:24, david a écrit :
> After trying several paths, some suggested on this list, here's my results.
Hi,
Just back from a hiking trip. One of my clients sent me a message that his
CentOS server refuses to boot. So tomorrow I have to drive there to figure out
what's going on. I
After trying several paths, some suggested on this list, here's my results.
1) Fixing a unbootable system wasn't practical in my
case. Fortunately, all my systems can be rebuilt from scratch.
2) When I was lucky enough to catch an updated system before reboot,
backing out the defective
36 matches
Mail list logo
