CentOS Linux 7.5 (1804) Released
blog.centos.org
blog.centos.org
[0]: https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7.1804?ac...
[1]: https://access.redhat.com/documentation/en-us/red_hat_enterp...
Most relevant to CentOS / this post is
https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/r...
I've had good luck with their version of Python 3.6 but as always, YMMV with others.
Here's more on how software collections work and what is released: https://developers.redhat.com/products/softwarecollections/o...
Big companies goes to red hat because they promise to support software beyond their life cycle for years. So that's that.
Ubuntu is limited to younger folks and younger companies.
And half of them had screwed up their entire setup by installing the Remi repos. Sigh.
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.
If you want to stick with CentOS, I would suggest you try with Secure Boot turned off.
I tried. I don't have the details, but no luck. Thanks.
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.
The machine is a Thinkpad from the last couple of years. It definitely supports UEFI. I'd think it would have to be a very old machine to not support it at this point, or am I misunderstanding something?
I work professionally in IT and one reason I'm installing it is to better learn my way around Linux. RHEL is the most prominent distro in business so CentOS seems the place to start. There's no better way to learn than to keep burning my hand. :)
I did make sure I used a Thinkpad to maximize the chance of a successful, functional outcome with CentOS or any other distro or 'nix. AFAICT, Thinkpads are by far the most popular machines among the developers of the various 'nixes.
One advantage to CentOS, for me, is its stability. I don't want rapid upgrade cycles. I have no need for the latest and greatest; I'm not gaming; I don't even use Bluetooth. Vim and a web browser should work fine regardless of the distro.
Anyway, here is a thread that I just found that seems to summarize the pain I went through at the time (alas, my path was far more circuitous)...
https://lists.centos.org/pipermail/centos/2018-January/16786...
I've been running RHEL on a ThinkPad T420 for years without any major issues. It Just Works(tm).
Thanks. Here's my reasoning regarding my choice of distro, FWIW:
Anyways, you might consider posting the details (including verbatim error messages, hardware (partitioning) details, etc.) in a new post on the CentOS forums [0] or inquire about the error message on the CentOS IRC channel [1].
Alternatively, if you continue to run into issues with the installation, feel free to reach out to me if you'd like. I'm not associated with either Red Hat or CentOS but I do run a lot of RHEL/CentOS machines (mostly on servers but I do happen to have a ThinkPad running RHEL 7.5 sitting here by me) and I'd be happy to help troubleshoot the issue with you, if necessary.
It seemed that the EFI/boot/bootx64.efi that would get loaded instead (EFI default loader search) couldn't find grub in the EFI/centos folder. It booted fine after I copied the relavent grub files over to EFI/boot, but it seemed like a really kludgy solution. Fine for a single research box, but not for production.
Basically this problem is because Anaconda (the RedHat / CentOS installer) puts the files in [/boot]/efi/centos/... when you install into a UEFI-capable system, but efibootmgr, the tool that manipulates your laptop's NVRAM to tell the UEFI boot loader what to display/default boot, was being told they're in [/boot]/efi/boot/... That's the standard location on other Linux types (Ubuntu, Arch, etc.) and is being picked up as a default somewhere.
If you patch or upgrade the system subsequent to your initial installation, it can mess this part up (supposedly this was fixed in RH/CentOS 7.4)
You can make a one-time fix using efibootmgr from rescue mode from the installation DVD as pointed out in the linked mailing list post by others.
But my recommendation would be to blow away the existing partitions and try doing it from scratch using 7.5 if you haven't done anything with the system yet.
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 ("How to setup Firefox 4 (i386 and x86_64) on CentOS 5").
https://wiki.centos.org/FAQ/CentOS7
Depending on what the topic is, the age of an article may not be all that relevant -- the important thing is to make sure that it's aimed at the version of CentOS that you're running. Some of those old wiki pages were written for CentOS 4 and that's been EOL for over six years!
If you have run into problems or have some specific questions, the CentOS forums can be a great resource. There seems to be some pretty knowledgeable folks there and the moderators will, at the least, ensure that no incorrect or outdated information is given out.
Finally, remember that Red Hat publishes a tremendous amount of technical documentation for RHEL 7 [0] which (with a few exceptions) also applies directly to CentOS 7. The PDF versions of their "Installation Guide" [1] and "System Administrator's Guide" [2] for RHEL 7 weigh in at 489 and 602 pages, respectively.
At times, you may come across knowledge base articles or other documentation on their "customer portal" (access.redhat.com) [3] but that you can't see because it requires an account. Fortunately, they have a (free!) "Red Hat Enterprise Linux Developer Program" [4] that you can sign up for which will give you access to that "customer portal" in addition to providing you with a valid license to run RHEL (as well as a lot of their other stuff) for development/testing purposes. See the original announcement [5] and/or press release [6] for more information.
[0]: https://access.redhat.com/documentation/en-us/red_hat_enterp...
[1]: https://access.redhat.com/documentation/en-us/red_hat_enterp...
[2]: https://access.redhat.com/documentation/en-us/red_hat_enterp...
[3]: https://access.redhat.com/documentation/en-us/
[4]: https://access.redhat.com/products/Red_Hat_Enterprise_Linux/...
[5]: https://developers.redhat.com/blog/2016/03/31/no-cost-rhel-d...
[6]: https://www.redhat.com/en/about/press-releases/red-hat-expan...
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
ICYMI, the openldap-servers package is "deprecated and will not be included in a future major release of Red Hat Enterprise Linux".
For RHEL, that means it will remain in the 7.x versions but will not be included in 8.x when it is released (which should be Real Soon Now(tm)).
For CentOS, that also (likely) means that OpenLDAP will not be included in future (major) versions.
[0]: https://access.redhat.com/documentation/en-us/red_hat_enterp...
openldap upstream suggest using these on CentOS / RHEL over the redhat packages, if operating the server components.