Understanding the bin, sbin, usr/bin, usr/sbin split (2010)

Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by tremon on Wednesday May 11, 2022 @05:18AM (#31337562)

/usr/games should never have existed in the first place, imnsho. If it's a small game, its binary could just have been put in /usr/bin. If it's a large game, it probably should be in /opt/$game.

[ Parent | on HN ]

Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by bityard on Wednesday May 11, 2022 @08:21AM (#31338848)

It's a historical unix thing. Things in /usr/games (which were not all games) were frivolous and not essential to the OS, and were distributed as a separate tape or archive so that admins could easily choose whether or not to install them.

[ Parent | on HN ]

Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by shagie on Wednesday May 11, 2022 @01:22PM (#31343052)

I'll also note /usr/games/dm ( https://github.com/vattam/BSDGames/tree/master/dm ) which allowed sysadmins to restrict when programs in /usr/games could be run. Setting up that structure in /usr/bin would be more work to maintain.

[ Parent | on HN ]

Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by jmclnx on Wednesday May 11, 2022 @09:56AM (#31339998)

/usr/games existing allows people to find the most important binaries. If in */bin finding all of these could be difficult

[ Parent | on HN ]

Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by KerrAvon on Wednesday May 11, 2022 @11:23AM (#31341344)

We have a hierarchical filesystem. /usr/bin/games could be a thing.

[ Parent | on HN ]