Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CentOS Linux 7.5 (1804) Released

blog.centos.org

Post reply on HN
Print view View original

11–20 of 57 posts

Re: CentOS Linux 7.5 (1804) Released

#11

Post by SirMonkey »

forapurpose wrote: post #8

Where are good places to find CentOS technical documentation and community? I can't find a manual online, and the other resources seem insufficient. I think I must be missing something: These forums seem to have not great content or traffic (at least when I looked): https://www.centos.org/forums/ The FAQ is only a few questions, and the How-tos and Tips & Tricks are very uneven in their coverage and often outdated ("…

Somethings are a bit different, but it's "almost the same" https://access.redhat.com/documentation/en-us/red_hat_enterp... (as an example) Most of the time I look for RH Stuff or fedora and do a mental downgrade of some of the tools.

Re: CentOS Linux 7.5 (1804) Released

#13

Post by eatandwonder »

Technical problem for which I haven't found a hint of an answer online:

I'm installing CentOS 7.0 x64 on a Thinkpad, my first Linux install. The install seems to go fine but on boot, right after the BIOS splash screen, in text mode, I see the following, then it stops (I'm going to use italics to be nice to people with small screens):

Failed to open \EFI\BOOT\grubx64.efi - Not Found

Failed to load image \EFI\BOOT\grubx64.efi: Not Found

start_image() returned Not Found

Secure boot is enabled, in case that's important. I've no idea why backslashes are used but I'm going to overlook that for now.

I booted to rescue mode and looked at the file system. /mnt/sysimage/boot/efi/EFI/BOOT/ indeed lacks grubx64.efi; I did find /mnt/sysimage/boot/efi/EFI/centos/grub64.efi [0] (I'm assuming the paths in the error message are all relative to /mnt/sysimage/boot/efi, because that's the only place I see relevant files).

Do I just copy the grubx64.efi file to ../EFI/BOOT/? Change the path in some config file to point at ../EFI/centos/? Or am I on the completely wrong path?

[0] Sh-ucks. My notes say the filename is ../centos/grub64.efi; the error message says grubx64.efi (i.e., with an x between grub and 64). Hopefully it's a typo in my notes. I don't have the laptop with me to check.

Re: CentOS Linux 7.5 (1804) Released

#14

Post by eatandwonder »

eatandwonder wrote: post #13

Technical problem for which I haven't found a hint of an answer online: I'm installing CentOS 7.0 x64 on a Thinkpad, my first Linux install. The install seems to go fine but on boot, right after the BIOS splash screen, in text mode, I see the following, then it stops (I'm going to use italics to be nice to people with small screens): Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grub…

For some reason I can't edit my post. I wanted to write that I know Hacker News is not a technical support forum, but I'm a little stuck so I was hoping some kind CentOS veteran could help or point me to where I can find answers to questions like this one. Thanks!

Re: CentOS Linux 7.5 (1804) Released

#15

Post by bubblethink »

forapurpose wrote: post #8

Where are good places to find CentOS technical documentation and community? I can't find a manual online, and the other resources seem insufficient. I think I must be missing something: These forums seem to have not great content or traffic (at least when I looked): https://www.centos.org/forums/ The FAQ is only a few questions, and the How-tos and Tips & Tricks are very uneven in their coverage and often outdated ("…

RHEL docs.

Re: CentOS Linux 7.5 (1804) Released

#16

Post by dnhz »

mlindner wrote: post #10
hd4 wrote: post #3

Is it true that most of Silicon Valley runs on CentOS?

It's literally the oldest most out of date Linux distro available (even this update), so probably. CentOS recently added Python 2.7 instead of Python 2.6...

Well what are the downsides of this? One is not limited to Python 2.7 because of the operating system, for instance.

Re: CentOS Linux 7.5 (1804) Released

#17

Post by Kostic »

eatandwonder wrote: post #13

Technical problem for which I haven't found a hint of an answer online: I'm installing CentOS 7.0 x64 on a Thinkpad, my first Linux install. The install seems to go fine but on boot, right after the BIOS splash screen, in text mode, I see the following, then it stops (I'm going to use italics to be nice to people with small screens): Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grub…

Any specific reason why you aren't using latest Fedora instead of CentOS?

If you want to stick with CentOS, I would suggest you try with Secure Boot turned off.

Re: CentOS Linux 7.5 (1804) Released

#18

Post by sciurus »

mlindner wrote: post #10
hd4 wrote: post #3

Is it true that most of Silicon Valley runs on CentOS?

It's literally the oldest most out of date Linux distro available (even this update), so probably. CentOS recently added Python 2.7 instead of Python 2.6...

I'm pretty sure RHEL 7.0, which was released in 2014, shipped with Python 2.7 as the default.

Re: CentOS Linux 7.5 (1804) Released

#19

Post by Diggity »

eatandwonder wrote: post #13

Technical problem for which I haven't found a hint of an answer online: I'm installing CentOS 7.0 x64 on a Thinkpad, my first Linux install. The install seems to go fine but on boot, right after the BIOS splash screen, in text mode, I see the following, then it stops (I'm going to use italics to be nice to people with small screens): Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grub…

This may be related to having an older machine that doesn't support EFI boot.

To solve the problem: 1) Create a partition that is of type bios boot (I believe it needs to be 2K) 2) Create a regular boot partition /boot (I recommend ext4 or 3) 3) Create your other partitions per normal.

Re: CentOS Linux 7.5 (1804) Released

#20

Post by Diggity »

One major undocumented problem that I did not see in the patch notes involves openldap.

Specifically there is some error in generating a PID file in the system-d service call.

I solved the problem by removing/commenting out the run PID line in /usr/lib/systemd/system/slapd.service

Post reply on HN