#3569 PR merged: Changes to recover openSUSE Tumbleweed / SLES16

Labels: enhancement, fixed / solved / done

svlv opened issue at 2026-02-19 10:36:

Pull Request Details:

  • Type: Enhancement

  • Impact: Normal

  • Reference to related issue (URL): Fixes https://github.com/rear/rear/issues/3567

  • How was this pull request tested?
    Manually recovered openSUSE Tumbleweed 20260209

  • Description of the changes in this pull request:

    • Add nsswitch.conf for SUSE with usrfiles to allow to look for /usr/etc/services needed by rpbcind
    • Copy the necessary libnss_usrfiles module to the rescue system
    • Copy /usr/libexec/openssh/sshd-aut because it is required by sshd

svlv commented at 2026-02-21 07:57:

sshd requires /usr/libexec/openssh/sshd-auth on Debian 13 as well

jsmeix commented at 2026-02-23 13:40:

@svlv
thank you for your enhancements at various places
to make ReaR working in particular on SLES16!

jsmeix commented at 2026-02-23 13:45:

@rear/contributors
I would like to merge it on Friday (27. Feb.) afternoon
unless there are objections.

As far as I see from plain looking at the code
the changes should not cause regressions
for other Linux distributions but I would prefer
if you could have a look (as time permits),
perhaps you spot possible problems in particular
incompatible issues for older Linux distributions?

jsmeix commented at 2026-02-23 13:57:

@svlv
I have a question regarding /etc/nsswitch.conf
but I am not at all an expert in this area
so my question could be somewhat stupid:

You provide another hardcoded
usr/share/rear/skel/SUSE/default/etc/nsswitch.conf
in addition to our existing hardcoded
usr/share/rear/skel/default/etc/nsswitch.conf

I wonder it it might perhaps work better to

COPY_AS_IS+=( /etc/nsswitch.conf )

from the original system "as is" so for each Linux distribution
the ReaR recovery system matches the original system.

Or is there a reason why /etc/nsswitch.conf from original system
won't work within the (rather limited) ReaR recovery system
so we must provide our own hardcoded nsswitch.conf files?

svlv commented at 2026-02-23 14:19:

I am not expert either. Moreover, I am quite sure, that you know much more about Linux than I do.

Perhaps, yes, it's better to copy /etc/nsswitch.conf from the original system to avoid hardcoding it, however, It will definitely require an additional research and copying all necessary NSS modules, so, e.g., on my home machine nss-systemd is used additionally, so, perhaps it would be necessary to copy it as well . Also, It will require re-testing on all distros. I can learn about it a bit in my spare time.

Currently, adding /etc/nsswitch.conf affects only SUSE, and, if I am not mistaken, SLES uses usrfiles for quite a long time.

jsmeix commented at 2026-02-23 14:59:

@svlv
thank you for your explanation why there is a hardcoded
usr/share/rear/skel/SUSE/default/etc/nsswitch.conf

It is OK as is because it works (at least for you)
so no need to needlessly change things (pune intended)
or "never change a running system"
or "if it ain't broke, don't fix it"

[Export of Github issue for rear/rear.]