Hacker News new | ask | show | jobs
by MrStonedOne 1124 days ago
Only having one key bin/ folder for hard coded paths.

/usr/bin only existed because of fast small mainframe hard drives and slower larger hard drives.

I don't understand why the direction is the way it is thou. getting rid of /usr/ seems like it would make more sense.

1 comments

I’m also confused why all system supplied data is in /usr instead of say /sys.
Because that potentially allows all distro-supplied files to live under one (eventually read-only) directory.
So, somebody imagined/wished that all distros will switch to /usr/* and them will ship / part ? :> I don't think so. Totally wrong direction.

And init binary in /usr is complete braindeadness...

Also MS behind anything means they are trying to get rid of your options, eg by complicating things into "enterprise level" and keep pushing windows as userware.

But there is other possibility: minimal root that is easy to manage, switch, etc. etc. and rest of the system :)

> But there is other possibility: minimal root that is easy to manage, switch, etc. etc. and rest of the system :)

Yeah, libostree ("git for operating systems binaries") benefits from merging /usr. It might even be a requirement to have merged /usr to be able to use it.

https://en.m.wikipedia.org/wiki/OSTree

> I’m also confused why all system supplied data is in /usr instead of say /sys.

Wasn't that basically a historical accident? IIRC in very early UNIX, "/usr" used to be like the modern "/home", but they happened to have a big disk for that mount and started putting system files there.