On Tue, Apr 02, 2024 at 09:05:53AM +0800, ericwq...@qq.com wrote: > > On Apr 2, 2024, at 06:25, Laurent Bercot <ska-skaw...@skarnet.org> wrote: > > > > If the default PATH has /usr/sbin before /usr/bin for all users, then the > > best thing is probably to install cd, umask and wait into /usr/sbin. It's > > not exactly clean, but at this point we're not trying to be clean, we're > > trying to make things work. And it wouldn't be the first time a binary > > that's > > available to all users gets installed in /usr/sbin. > > Two options: > 1. Move the conflicted files: cd, umask and wait to /usr/sbin, while keep the > others in /bin directory. > 2. Install all of them to /usr/sbin directory. > > Which one is better? > > Wang qi.
There have been some discussions, starting at Fedora, about unifying the bin and sbin directories: https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin ...so... neither option may be a very good long-term solution :( Also, even apart from unifying the directories, there are various people who have expressed concern about having different programs with the same name in /usr/bin and /usr/sbin, thus making it something of a potluck which one will be invoked depending on the user's search path. I have to admit that I am kind of in agreement with that: different binaries with the same name in directories that are both meant to be in the search path seems... a bit fishy to me, and, yeah, with the potential for problems if the directories are reordered (I have seen arguments for both sides: "things in /sbin are more important, so it should come before /bin; things in /bin are used much more often, so it should come before /sbin"). G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
