- caching of group and passwd does not make sense because sssd and winbind have their own caches, and NIS is not used nowadays
- caching to accelerate DNS resolution would be useful, but:
- systemd-resolved is used by default in rosa2019.1 and has its own cache
- but hosts cache is offed by default by eglibc-mandriva-nscd-no-host-cache.patch
So, nscd does not make sense. And causes troubles in different situations, e.g. in useradd --root <...> in Anaconda.
Support being a chroot on RHEL 8 (4.18), Ubuntu 18.04 (4.15) and LTS (4.14) kernel
For example, we have an aarch64 server with such kernel where it is problematic to upgrade it right now :(
Fixes: f1a767c "Support syscalls of kernel 5.4"
I have looked at https://sourceware.org/git/?p=glibc.git;a=history;f=sysdeps/unix/sysv/linux/syscall-names.list;h=HEAD;hb=HEAD
and it seems that we do not support quite a lot of syscalls
We loose ability to run in chroots/containers on CentOS 8, but it is probably not a big problem for us right now
(ROSA is not a populer distro for contaienrs unfortunately)
and, I think, it is better to support newer syscalls than try to support strange hosts of containers.
We do not support RHEL 7 hosts now (they have kernel 3.10, but we require 4.0+).
Both rosa2019.1 and RHEL 9 with a newer kernel will be released soon
Discussed with and approved by fedya@.
He also said that older kernels are not required on aarch64.