pcahyna

> * During recovery one can NOT at any stage re-run "rear recover". > In my experience in most cases re-running "rear recover" fails > or would only work with...

@danboid can you please have a look at the resulting document https://github.com/rear/rear/blob/16d6be5664a24ce5f30e5f8b9cb727e89a15c37f/doc/user-guide/06-layout-configuration.adoc ? Not to check correctness, but to see whether it is better understandable than the previous version and...

@jsmeix I especially dislike the wording > There are two ways to deal with different hardware. One is being lazy and dealing with problems when you encounter them. The second...

@jsmeix I have been hoping that my professional doc writer colleague would review the PR and possibly even help with the numerous formal/style problems that we identified, that's why I...

> * ReaR version: 2.6 / 2020-06-17 > > * OS version: RHEL 8.6 Something is wrong with your screenshots then, they show ReaR 2.00 and CentOS 7.

> Current machine is a custom UEFI BIOS. I suspect that's the issue then, ``` ISO_DEFAULT="automatic" ISO_RECOVER_MODE="unattended" ``` work only with legacy BIOS and not UEFI (or with GRUB booting...

I believe there is a bootloader menu shown before boot where you can see whether it is GRUB, isn't it? For example, the screenshot hou have shown is from SYSLINUX.

Yes so unfortunately the problem is that `ISO_DEFAULT` is not supported for GRUB, so one option would be to boot in legacy BIOS mode, if that's feasible (uses SYSLINUX), another...

Sorry @keredf for my untested and nonfunctional suggestion. This code works for modifying the ISO image that is bootable on another platform (POWER with OpenFirmware), but apparently this is not...

The logic is: If I run tests on RHEL, the tests install packages from RHEL when they install some RPMS, not from Fedora, even if the tests are opensource and...