On Wed, Jan 10, 2024 at 12:49 AM <to...@tuxteam.de> wrote: > > On Wed, Jan 10, 2024 at 05:06:33AM +0000, miphix wrote: > > If you were to issue 'ls -l /' You'll find that /bin, /sbin, > > lib{32,64,x32} are linked to their counterparts in /usr/. I under- > > stand the logic in doing so. However, for specific reasons that would > > require exhaustive explanations that I would prefer to save us all from > > me doing, I would like to break this behaviour by having /usr genuinely > > be whole heartedly installed on its own partition. I'm cool with doing > > things the hard and painful way. Any details you can share that would > > allow me to figure out how to break, or divert this behaviour would > > be appreciated. I'm not elite with linux enough to figure this out, > > but I am comfertable with digging deep with the right background > > knowledge to navigate what's needed. > > The jargon for this thing is "usrmerge". With that, search engines > turn up some hits on other people with your same needs, e.g. > > > https://brontosaurusrex.github.io/2023/09/11/Upgrade-Debian-11-to-12-without-usrmerge-errors/ > > I don't know whether some applications start breaking because of that > (why should they, but there's badly designed software everywhere).
I think some programs can break, like those that assume / and /usr are both mounted early in the boot process. I think the only guarantee is / will be mounted early, and all programs needed to boot are available from /. I thought there was a discussion about some problems with systemd when / and /usr are different mount points (and only / is mounted early), but I can't find it at the moment. Also see <https://news.ycombinator.com/item?id=30929024> and <https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=usrmerge>. Jeff