Russ Allbery dixit: >I don't see any point in doing this as opposed to just moving everything >from sbin into bin and making sbin a symlink to bin.
Alone the pain to do so (and the complaints from traditionalists) should be enough to not do that. There’s also the “if I want to have a look at what commands on the system are used for administering, I can just ls /sbin /usr/sbin” thing. Additionally, non-sudo users (especially on Derivatives, but maybe also on Debian itself) might want to have that excluded again (e.g. by the person administering their system), which would not work were they all in one directory. That being said, for a mostly-tech OS, having the sbins in the $PATH is A Good Thing. In MirBSD, I’ve been using that for years. bye, //mirabilos -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -- Edward Burr -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1208081154120.12...@herc.mirbsd.org