![](https://cdn.fosstodon.org/accounts/avatars/000/299/269/original/51c09a57eafd4c50.jpg)
![](https://lemmy.kde.social/pictrs/image/f5a2ef84-8058-41a4-8c36-aa53a26052df.png)
@carlschwan @kde@lemmy.kde.social @kde@floss.social
Yeah, RHEL 7 uses it out of the box and is still supported, at least until June 2024: https://www.redhat.com/en/blog/end-maintenance-red-hat-enterprise-linux-7-almost-here
zyga aka zygoon, Dad, FOSS programmer, Canonical, ex-Huawei, ex-Samsung. IRC: zyga, GitHub: zyga, GitLab: zyga-aka-zygoon photograph bees and shitpost about the state of FOSS from time to time.
Snapd developer with unlimited enthusiasm.
@carlschwan @kde@lemmy.kde.social @kde@floss.social
Yeah, RHEL 7 uses it out of the box and is still supported, at least until June 2024: https://www.redhat.com/en/blog/end-maintenance-red-hat-enterprise-linux-7-almost-here
@brauner @kde@lemmy.kde.social @kde@floss.social
Thanks for the insight. I was surprised by EPERM, would have expected ENOSYS as well.
Looks like EPERM is most likely coming out of unknow system call name being filtered-out by snap-seccomp compiler. I’ll update snapd to 2.61.1 to avoid chasing fixed bugs and then see if there’s something to improve in the compiler.
@Conan_Kudo @carlschwan @kde@lemmy.kde.social @kde@floss.social yeah, I strongly suspect seccomp. I’m debugging this now and I will share updates when I get to the bottom of the problem.