> > At this point, I think it'd be worth revisiting, at the project level, > the historical tradition of leaving the sbin directories out of non-root > paths. Setting aside all the single user desktop and laptop systems, > there are enough alternative ways to grant restricted root (file ACLs, > etc), and to run in alternate filesystem namespaces (e.g. containers), > that the functional distinctions that lead to the original directory > split are probably applicable in a minority of situations these days.
I also agree we could here revisit the unix tradition ( which btw is not such a strong one anymore CentOS, and the BSDs have /usr/sbin and /sbin in path) However I also I agree that it should be done at the project level, not in the vagrant box or cloud image , so I will reassign this to the general pseudo-package.
