Why stop there?

Posted Feb 25, 2014 1:37 UTC (Tue) by bojan (subscriber, #14302)
In reply to: Next feature to import by bluss
Parent article: Debian TC vote on init system coupling

While at it, they can also rename /lib32 to /lib and /lib to /lib64. ;-)

Why stop there?

Posted Feb 25, 2014 2:18 UTC (Tue) by HelloWorld (guest, #56129) [Link]

Debian solved that problem a long time ago. 32 bit x86 libraries live in /usr/lib/i386-linux-gnu, 64 bit ones in /usr/lib/x86_64-linux-gnu.

Why stop there?

Posted Feb 25, 2014 2:19 UTC (Tue) by mathstuf (subscriber, #69389) [Link] (2 responses)

Debian already solved this with multiarch (e.g., lib/amd64 or something, probably the ABI triplet).

Once you get /usr/bin and /bin merged, let's get /usr/bin and /usr/sbin merged :D .

Why stop there?

Posted Feb 25, 2014 7:46 UTC (Tue) by mbunkus (subscriber, #87248) [Link] (1 responses)

This is not so uncommon anymore. On my Arch they've been merged last year:

[0 mbunkus@chai-latte ~] ls -ld /{s,}bin /usr/{s,}bin
lrwxrwxrwx 1 root root 7 31. Mai 2013 /bin -> usr/bin/
lrwxrwxrwx 1 root root 7 31. Mai 2013 /sbin -> usr/bin/
drwxr-xr-x 1 root root 81396 21. Feb 15:53 /usr/bin/
lrwxrwxrwx 1 root root 3 31. Mai 2013 /usr/sbin -> bin/

Why stop there?

Posted Feb 25, 2014 8:11 UTC (Tue) by mathstuf (subscriber, #69389) [Link]

Yeah, I would have guessed someone had done it; may as well be Arch. I run Rawhide and some of the stuff Arch does scares me (Python3 as default…).