-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Announcing the version 1.0 hexpeek release!
I am pleased to announce the first stable release of hexpeek, which
seeks to be an efficient, powerful, and portable hex editor for files
of all kinds and sizes.
This release improves on the beta
At 05:01 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:27 schrieb david:
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you
Am 05.08.20 um 01:27 schrieb david:
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what
did it do when it failed to boot? What
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did it do when it
failed to boot? What text messages showed up on the
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did it do when it
failed to boot? What text messages showed up on the console? Any
reported errors when you
On Tue, Aug 4, 2020 at 11:34 AM wrote:
> Q5) If the answer to the last question is "no": shouldn't there be such
> a resource?
>
CentOS doesn't publish security errata. If you need it then you should
either buy RHEL, or deal with putting together your own set up with
something like
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did it do when it failed to
boot? What text messages showed up on the console? Any reported errors when
you ran the update or when you rebooted
Your system was most likely rebuilding the initrd, and you interrupted
it leaving you with a broken initrd.
Try booting off a rescue disk and chroot into the install, and run:
dracut -f -v
to regenerate all the initrds.
Also, you don't need to reinstall the kernel but just do a 'yum
On Tue, Aug 04, 2020 at 10:54:50AM -0700, david wrote:
> Yum got up to the point:
>
> Running transaction
> Installing : kernel-3.10.0-1127.el7.x86_64 1/1
>
> at which point the process appeared to hang. No further output happened for
> five minutes. I opened a different terminal and entered
Following the advice on this mailing list, I rebuilt (from scratch)
Centos 7.8. I added the following line into /etc/yum.conf before the
first update:
exclude=grub2* shim* mokutil
The system worked fine. I was able to do general updates
yum -y update
and all was well.
HOWEVER, following
Dear List,
I have spent some time playing around with oscap and the RHEL OVAL feed
(https://www.redhat.com/security/data/oval/v2/RHEL8/, also check Chapter
16 of the RHEL 8 Design Guide). Because I could not find an existing
OVAL file for CentOS, I downloaded one of the RHEL8 files and
> Am 04.08.2020 um 17:59 schrieb Jerome Lille :
>
> Hello
>
> Luckily I was not afflicted by this boot hole problem. I haven't done
> yum update in a week or so. I just want to make sure that now it is
> safe to do yum update?
It is.
>
> /Jerome
>
>
Hello
Luckily I was not afflicted by this boot hole problem. I haven't done
yum update in a week or so. I just want to make sure that now it is
safe to do yum update?
/Jerome
___
CentOS mailing list
CentOS@centos.org
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
21 matches
Mail list logo
