4 ms·

They might as well rename it C:/Linux/System32 while they're at it. The separate paths were originally done for reasons but since you can't install a mainstrea

They might as well rename it C:/Linux/System32 while they're at it. The separate paths were originally done for reasons but since you can't install a mainstream distro with < 512MB RAM these days (not even Alpine) some of those reasons are moot. Linux is becoming less and less like UNIX every day.

initplus 2y ago
The original history behind a lot of original UNIX directory structure is engineers running out of disk space on a PDP-11 50 years ago and shuffling things around to keep the system operating. Other reasoning has been piled on top over the years.
- Athas 2y ago
  Yes, and undoing this means it's no longer UNIX as it will no longer run on that PDP-11! (Unless you can afford a bigger disk I guess.)
  - NekkoDroid 2y ago
    If "being UNIX" hinges on the fucking filesystem structure I honestly am fine with it "not being UNIX"
    - pjmlp 2y ago
      It does, however it is actually less strict than I had in mind, https://pubs.opengroup.org/onlinepubs/9699919799/ https://pubs.opengroup.org/onlinepubs/9699919799/
    - eru 2y ago
      I suspect you missed the sarcasm in Athas' comment?
      - deleted 2y ago
        [deleted]
  - jraph 2y ago
    A lot of thoughts [1] have been put into the usr merge, and compatibility with unix is one of them, and one other unix that has done this merge is Solaris, so Linux distros doing the merge are not even that special. (note: it's not about merging /bin and /sbin) [1] https://systemd.io/THE_CASE_FOR_THE_USR_MERGE/ https://systemd.io/THE_CASE_FOR_THE_USR_MERGE/
setopt 2y ago
> The separate paths were originally done for reasons These reasons were not originally philosophical in nature: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html http://lists.busybox.net/pipermail/busybox/2010-December/074... IMO, keeping /usr/bin and /usr/local/bin separate from /bin doesn’t serve any useful purpose except historical continuity. You can’t really get rid of those paths without breaking things (e.g. since /usr/bin/env is usually hardcoded in shebangs), but symlinking them together is a practical way of effectively merging them.
- forgotpwd16 2y ago
  > > The separate paths were originally done for reasons > > These reasons were not originally philosophical in nature: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html http://lists.busybox.net/pipermail/busybox/2010-December/074... > > IMO, keeping /usr/bin and /usr/local/bin separate from /bin doesn’t serve any useful purpose except historical continuity. You can’t really get rid of those paths without breaking things (e.g. since /usr/bin/env is usually hardcoded in shebangs), but symlinking them together is a practical way of effectively merging them. The `local` does. It is were
  - forgotpwd16 2y ago
    Urgh, that's what get trying to write a comment through an app (and sadly edit time window is gone). Anyway, the `local` does. It is a manually managed sub-hierarchy, compared to rest being system managed. So `/bin` and `/usr/bin` will have executables managed through a package manager whereas `/local/bin` is were admin will put executables by themselves to be accessible by all users. Also, it's were `make install` will put its builds by default. Systemd provides a per-user similar hierarchy in `~/.local`, which has a `~/.local/bin` directory.
- DaSHacka 2y ago
  `/usr/local/bin` is where manually installed packages go, and I've never seen it merged to `/bin` or `/usr/bin` on any *NIX system I've ever used. I use it all the time for custom scripts/programs I don't want the package manager to interfere with. https://unix.stackexchange.com/questions/4186/what-is-usr-local-bin#4187 https://unix.stackexchange.com/questions/4186/what-is-usr-lo...

initplus 2y ago

The original history behind a lot of original UNIX directory structure is engineers running out of disk space on a PDP-11 50 years ago and shuffling things around to keep the system operating. Other reasoning has been piled on top over the years.

Athas 2y ago
Yes, and undoing this means it's no longer UNIX as it will no longer run on that PDP-11! (Unless you can afford a bigger disk I guess.)
- NekkoDroid 2y ago
  If "being UNIX" hinges on the fucking filesystem structure I honestly am fine with it "not being UNIX"
  - pjmlp 2y ago
    It does, however it is actually less strict than I had in mind, https://pubs.opengroup.org/onlinepubs/9699919799/ https://pubs.opengroup.org/onlinepubs/9699919799/
  - eru 2y ago
    I suspect you missed the sarcasm in Athas' comment?
    - deleted 2y ago
      [deleted]
- jraph 2y ago
  A lot of thoughts [1] have been put into the usr merge, and compatibility with unix is one of them, and one other unix that has done this merge is Solaris, so Linux distros doing the merge are not even that special. (note: it's not about merging /bin and /sbin) [1] https://systemd.io/THE_CASE_FOR_THE_USR_MERGE/ https://systemd.io/THE_CASE_FOR_THE_USR_MERGE/

setopt 2y ago

> The separate paths were originally done for reasons These reasons were not originally philosophical in nature: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html http://lists.busybox.net/pipermail/busybox/2010-December/074... IMO, keeping /usr/bin and /usr/local/bin separate from /bin doesn’t serve any useful purpose except historical continuity. You can’t really get rid of those paths without breaking things (e.g. since /usr/bin/env is usually hardcoded in shebangs), but symlinking them together is a practical way of effectively merging them.

forgotpwd16 2y ago
> > The separate paths were originally done for reasons > > These reasons were not originally philosophical in nature: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html http://lists.busybox.net/pipermail/busybox/2010-December/074... > > IMO, keeping /usr/bin and /usr/local/bin separate from /bin doesn’t serve any useful purpose except historical continuity. You can’t really get rid of those paths without breaking things (e.g. since /usr/bin/env is usually hardcoded in shebangs), but symlinking them together is a practical way of effectively merging them. The `local` does. It is were
- forgotpwd16 2y ago
  Urgh, that's what get trying to write a comment through an app (and sadly edit time window is gone). Anyway, the `local` does. It is a manually managed sub-hierarchy, compared to rest being system managed. So `/bin` and `/usr/bin` will have executables managed through a package manager whereas `/local/bin` is were admin will put executables by themselves to be accessible by all users. Also, it's were `make install` will put its builds by default. Systemd provides a per-user similar hierarchy in `~/.local`, which has a `~/.local/bin` directory.
DaSHacka 2y ago
`/usr/local/bin` is where manually installed packages go, and I've never seen it merged to `/bin` or `/usr/bin` on any *NIX system I've ever used. I use it all the time for custom scripts/programs I don't want the package manager to interfere with. https://unix.stackexchange.com/questions/4186/what-is-usr-local-bin#4187 https://unix.stackexchange.com/questions/4186/what-is-usr-lo...