On 12 Jan 2018, at 7:40, Lennart Poettering wrote: > On Fr, 12.01.18 07:20, Steve Dickson (SteveD@xxxxxxxxxx) wrote: > >> Instead of doing the blow by blow these threads >> always turn into I'm just going jump to the point. >> >> systemd wants to use uid 65534 and it can't because >> NFS is using it. So instead of changing systemd needs >> they want to change NFS potentially break all NFS >> environments. > > This is really not helpful. Grow up. This directive is equally unhelpful. Steve D is condensing and summarizing his understanding of the case and his argument here so that we can more easily get to the point of the issue without a lot of back-and-forth. I think that counts as grown-up behavior. He's wrong about systemd, thanks for correcting him. > User namespacing is a Linux kernel feature. It's most well known > consumers are probably Docker, and maybe flatpak/bubblewrap and LXC. > > Neither Docker, nor flatpak/bubblewrap, nor LXC are systemd projects. > > It's not systemd that came up with reusing 65534 for user > namespacing. It's kernel people: > > $ cat /proc/sys/kernel/overflowuid > 65534 OK, so do we need to go back and revisit the bug attached to this change? https://bugzilla.redhat.com/show_bug.cgi?id=1350526 That was closed with NOTABUG. > You know, if you want my personal opinion: I don't think user > namespaces are particularly well designed even. But it doesn't > matter what I think on that, because userns is there, it has been > introduced by Linux kernel people, it's widely used, and it's not > going to go away. And we should make the best of it. But that doesn't mean it can't be changed or updated. Let's find the best way and not throw out some of the options. >> Is or isn't this what we are talking about without >> all the bloviation to justify the change. > > It really is not. You *really* should read up on what the Linux kernel > has been doing with user namespaces and how it started using the 65534 > UID for that. Good point; once again, I think let's go back to the bug and work on this problem there. It is likely that re-opening that bug will get the matter back in front of a number of people that originally decided it shouldn't be changed. > That UID long ceased to be Steve Dickson's private property, and it's > not systemd who took it away from you. It's evil evil kernel > hackers. Please complain to them. Steve Dickson is advocating for a large community of NFS users that have been building things with NFS for long before the userns stuff started conflicting. He's not arguing because he thinks that it is his private property, he's rightly raising the alarm that this change risks regressions, and he's saying that risk is very likely, and the scope is probably larger than you might realize. I don't think he's attacking systemd. Ben _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
