5 ms·

> There's no actual REASON for any of it anymore. No reason to do it on embedded system. Lots of backward compatibility reason on servers/desktops.

• pilif 4y ago
  it's my understanding that most distros by now have moved to have their stuff in /usr, though there might still be backwards compatibility symlinks of course.
  • hulitu 4y ago
    Good luck mounting /usr when mount is in /usr/bin. Not everybody uses a ramdisk to boot the system.
    • pabs3 4y ago
      Not using an initrd is unsupported on lots of distros these days.
      • blueflow 4y ago
        You mean initramfs, initrd is unsupported on lots of distros these days.
        • pabs3 4y ago
          Right.
    • colonwqbang 4y ago
      Just don't put /usr on its own partition. What is the point anyway after we have merged /bin into /usr/bin, /lib into /usr/lib etc. Just put your operating system on a single partition and be happy.
• usrbinbash 4y ago
  Backward compatibility can be ensured with a couple of symlinks.
• moffkalast 4y ago
  > backward compatibility You're kidding me right? Nobody ever bothers with that for anything else and the company I work at spends like more than half the time resolving stupid install breaking changes that nobody asked for. This would just be one minor extra thing on that pile, but at least it would make sense for once.