Eric Blake <e...@byu.net> writes: > The point is that setuidgid is not installed. It exists only for the > purposes > of the testsuite. If it were an installed app, then yes it would make sense > to > keep it around, although perhaps rewritten as a wrapper around the new chroot > functionality. But since setuidgid is not installed, while chroot is, there > is > no longer any incentive to even have setuidgid in the first place. By using > chroot in the first place, the testsuite would be a) adding to the coverage > of > chroot features, and b) minimizing reliance on software that gets no testing > outside of the testsuite, both of which are good moves.
Well, in this case I agree with you. It is better to remove setuidgid and use the new chroot features. Less code means less problems. Giuseppe _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
