BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Debian 12 vs. WSL 1
- Subject: [Discuss] Debian 12 vs. WSL 1
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Sat, 24 Jun 2023 11:37:45 -0400
- In-reply-to: <ZJb6KQZIsV2HW4mY@csail.mit.edu>
- References: <20230617000719.GC24375@bladeshadow.org> <ZI3joxAhn/hBUEjJ@csail.mit.edu> <20230620190819.GG24375@bladeshadow.org> <ZJJS7tyoCe0SgsHs@csail.mit.edu> <20230621160423.GI24375@bladeshadow.org> <ZJOuOhNYlqKx3Bwu@csail.mit.edu> <20230622184310.GL24375@bladeshadow.org> <20230622190045.GM24375@bladeshadow.org> <ZJXIguU/FuxJGL+X@csail.mit.edu> <70742c49-36fe-ebb4-4c26-5ddb22015951@syntheticblue.com> <ZJb6KQZIsV2HW4mY@csail.mit.edu>
On Sat, 24 Jun 2023 10:14:01 -0400 grg <grg-webvisible+blu at ai.mit.edu> wrote: > I agree usrmerge is a good thing, but I'd say it's actually adding > bloat rather than trimming it: post-usrmerge there are (at least) two > paths for every binary, two linkings for every library. pre-usrmerge > there was usually just one on a given machine (even if different > machines had different ones). This isn't quite accurate. While there are multiple valid search paths to binaries and multiple possible link paths for libraries, the shell and runtime linker only care about the first ones they find. For example: $ which nohup /usr/bin/nohup $ ldd /bin/nohup /usr/bin/nohup /bin/nohup: linux-vdso.so.1 (0x00007ffdf9729000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1647dd0000) /lib64/ld-linux-x86-64.so.2 (0x00007f1647fd4000) /usr/bin/nohup: linux-vdso.so.1 (0x00007ffcf42e0000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3234636000) /lib64/ld-linux-x86-64.so.2 (0x00007f323483a000) It's a bit like multipath I/O: there are (at least) two paths for every LUN but the multipath driver usually only cares about one at a time. This isn't bloat. It's redundancy. It keeps the system running in spite of failures. > if we were trimming bloat we'd e.g. eliminate /bin, /sbin, /lib* > completely (or the reverse, eliminate /usr completely) and have just The accepted UsrMerge makes this possible: just delete the /bin, /lib, /lib64 and /sbin symbolic links. Done. Your machines will be unusable after doing this, but you can very easily do it. NB: I don't recommend doing this. -- \m/ (--) \m/
- Follow-Ups:
- [Discuss] Debian 12 vs. WSL 1
- From: grg-webvisible+blu at ai.mit.edu (grg)
- [Discuss] Debian 12 vs. WSL 1
- References:
- [Discuss] Debian 12 vs. WSL 1
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] Debian 12 vs. WSL 1
- From: grg-webvisible+blu at ai.mit.edu (grg)
- [Discuss] Debian 12 vs. WSL 1
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] Debian 12 vs. WSL 1
- From: grg-webvisible+blu at ai.mit.edu (grg)
- [Discuss] Debian 12 vs. WSL 1
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] Debian 12 vs. WSL 1
- From: grg-webvisible+blu at ai.mit.edu (grg)
- [Discuss] Debian 12 vs. WSL 1
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] Debian 12 vs. WSL 1
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] Debian 12 vs. WSL 1
- From: grg-webvisible+blu at ai.mit.edu (grg)
- [Discuss] Debian 12 vs. WSL 1
- From: daniel at syntheticblue.com (Daniel M Gessel)
- [Discuss] Debian 12 vs. WSL 1
- From: grg-webvisible+blu at ai.mit.edu (grg)
- [Discuss] Debian 12 vs. WSL 1
- Prev by Date: [Discuss] Debian 12 vs. WSL 1
- Next by Date: [Discuss] Debian 12 vs. WSL 1
- Previous by thread: [Discuss] Debian 12 vs. WSL 1
- Next by thread: [Discuss] Debian 12 vs. WSL 1
- Index(es):