News for hackers. Stuff that matters.
Re:Debian considers merging /usr by wtbob on Tuesday November 22, 2016 @06:23AM (#13013287)
Wouldn't it make more sense to merge stuff into / than into /usr, i.e., move /usr/bin/* into /bin, /usr/share into /share &c.? The 'usr' portion of the path is weird historical cruft which adds no real information.

While we're at it, why don't we add a real Plan-9-style bind and use union mounts?

Re:Debian considers merging /usr by fnord123 on Tuesday November 22, 2016 @06:56AM (#13013430)
>While we're at it, why don't we add a real Plan-9-style bind and use union mounts?

There have been a few stabs at a union fs. The most recent one, OverlayFS was merged in 2014.

Re:Debian considers merging /usr by JdeBP on Wednesday November 23, 2016 @05:49AM (#13021600)
The thinking behind keeping the "weird historical" /usr is that it parallels other operating systems that (mostly) store their stuff in a subtree that is under a single subdirectory of the root. Think \OS2, \DOS, and \WINDOWS for starters. Also remember \LINUX from the world of LOADLIN.
Re:Debian considers merging /usr by qb45 on Tuesday November 22, 2016 @02:07PM (#13016576)
Some programs may have strings like /usr/share hardcoded in them. I once tried renaming the root user to "boss" and it unearthed few issues of exactly this kind.
Re:Debian considers merging /usr by kasabali on Tuesday November 29, 2016 @07:11AM (#13062551)

  # ln -s / /usr
Re:Debian considers merging /usr by lima on Tuesday November 22, 2016 @07:52AM (#13013707)
No, some people want /usr as a separate partition.
Re:Debian considers merging /usr by rleigh on Tuesday November 22, 2016 @05:58PM (#13018430)
This hasn't had a genuinely useful purpose for many years.

On a modern package-managed Linux distribution, both / and /usr are under the control of the package manager, and separating them doesn't make sense since they are modified in lockstep, and used as a coherent whole.

And while in the Linux world we're busy "unifying" these locations, other systems can have the whole system on ZFS, where these locations can be in separate datasets if desired, and the whole lot can be snapshotted at will. Since it's all in a single pool, there's no need to even consider splitting it.