On Fri, 2018-01-12 at 07:20 -0500, Steve Dickson 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. > > Is or isn't this what we are talking about without > all the bloviation to justify the change. > > steved. Breaking all NFS environments is a (way?) too strong statement. My file server is running Freebsd and it uses 65534 as userid for default. Freebsd however calls it nobody, go, figure.... Now for nfs this is nowadays no problem anymore as we have the id-mapper. It now maps between 99 and 65534 and will start to automagically map between 65534 and 65534. Are there any real world examples of files owned by nobody left on Fedora? I guess that other OSs/distributions use 65534 for nobody, so this change would improve inter-operability with other environments. LouisL _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
