Johannes Meixner

Regarding OS_VENDOR values: What OS_VENDOR value dependant scripts we have: ``` # for OS_VENDOR in Arch RedHatEnterpriseServer Debian Fedora SUSE_LINUX Ubuntu ; \ do echo $OS_VENDOR ; find usr/sbin/rear usr/share/rear/...

What I think what is needed and what works in practice (in particular what is maintainable in practice) is only two semantically different/separated variables: * one for the Linux distribution...

@lzaoral when you finished all what you need to do in particular for Fedora and Red Hat (no rush, step by step, take your time) and when that also works...

@lzaoral @pcahyna is the actual subject of this issue "OS vendor and version autodetection fails on Fedora" solved at least for now for ReaR 2.8 with https://github.com/rear/rear/pull/3171 and https://github.com/rear/rear/pull/3344 merged?

See https://github.com/rear/rear/issues/2995 for the issue that led to this improvement request.

@pcahyna I am sorry, I forgot to inform you in advance that I am unavailable until 04. Sept. I will have a look then (as time permits).

A simple "rear mkbackup" plus "rear recover" test worked for me on two KVM QEMU virtual machines with OUTPUT=ISO and BACKUP=NETFS on SLES12 SP5 with DHCP networking (both on the...

@pcahyna I didn't notice error messages or other "suspicious" messages. I will have a closer look tomorrow when I test SLES15.

A simple "rear mkbackup" plus "rear recover" test worked for me on two KVM QEMU virtual machines with OUTPUT=ISO and BACKUP=NETFS on SLES15 SP3 with DHCP networking (both on the...

Regarding D-Bus in the ReaR recovery system: In the ReaR recovery system on SLES12 SP5 neither 'dmesg | grep -i dbus' nor 'journalctl | grep -i dbus' shows anything. In...