IRC channel logs

2025-02-26.log

back to list of logs

<fossy>stikonas:oops, sorry missed your messages, had a hectic few days
<fossy>stikonas: i do not really care, let's choose the faster option
<fossy>is the saving of time building mes more than the increased tcc time?
<matrix_bridge><Andrius Štikonas> fossy, probably but I need to double check
<doraskayo>Hi!
<doraskayo>I got disconnected so I'm nore sure if my previous messages were sent.
<doraskayo>not*
<doraskayo>Is there any Matrix bridge that can be used with this channel?
<matrix_bridge><gtker> Yes, I believe the address is #bootstrappable:stikonas.eu
<matrix_bridge><Dor Askayo> fossy. Andrius Štikonas: it looks like none of the packages in live-bootstrap provide the common FHS symlinks ("/lib"->"/usr/lib", "/bin"->"/usr/bin", "/sbin"->"/usr/bin", "/usr/sbin"->"bin", "/var/run"->"../run"). There's also no "/run" directory in general and "util-linux" seems to install its binaries in "/usr/sbin" instead of "/usr/bin".
<matrix_bridge>Is any of this intentional?
<matrix_bridge><Dor Askayo> Well, some of its binaries anyway.
<nimaje>/{,s}bin vs /usr/{,s}bin is classically if something is needed for boot or not and bin vs sbin is if it is something general or for the super user (root)
<matrix_bridge><Andrius Štikonas> Dor Askayo: we don't need those symlinks in live bootstrap
<matrix_bridge><Andrius Štikonas> And neither they are needed in normal Linux system
<matrix_bridge><Andrius Štikonas> I guess they are mostly there to keep compatibility
<matrix_bridge><Andrius Štikonas> But if stuff is already installed in /usr/bin instead of /usr/sbin, nothing should break
<matrix_bridge><Dor Askayo> Andrius Štikonas: it breaks dynamic loading, at minimum:
<matrix_bridge>$ python --help
<matrix_bridge>sh: /usr/bin/python: cannot execute: required file not found
<matrix_bridge>$ ldd $(which python)
<matrix_bridge> /lib/ld-musl-i386.so.1 (0xf2e98000)
<matrix_bridge> libc.so => /lib/ld-musl-i386.so.1 (0xf2e98000)
<matrix_bridge>$ ls -l /lib
<matrix_bridge>ls: cannot access '/lib': No such file or directory
<matrix_bridge><Dor Askayo> Some distributions have a "filesystem" package where the basic FHS directories and symlinks reside. It would have been nice to have something similar in live-bootstrap.
<matrix_bridge><Dor Askayo> The alternative is that I would hit issues like the above one by one and fix them with a downstream change, which wouldn't benefit others who may want to try and use live-bootstrap as a basis for their runtimes or distributions.
<matrix_bridge><Andrius Štikonas> Well, yes FHS or base package could be nice to have
<nimaje>how did it get build that broken? shouldn't the linker create the correct metadata there or complain that it can't find files?
<matrix_bridge><Dor Askayo> nimaje: the symlinks are created during bootstrap but not included in any specific package. When extracting all the packages to create a system based on live-bootstrap, those symlinks are missing.
<matrix_bridge><Andrius Štikonas> Dor Askayo: I guess either create an issue on live-bootstrap repo, so that it won't be forgotten or even better make a PR 🙂