Re: booststrapping /usr-merged systems
- To: debian-devel@lists.debian.org
- Subject: Re: booststrapping /usr-merged systems
- From: Bjørn Mork <bjorn@mork.no>
- Date: Fri, 09 Jun 2023 19:58:07 +0200
- Message-id: <[🔎] 87jzwcfrgw.fsf@miraculix.mork.no>
- References: <e5c52175-adaa-cd87-3a5f-8b49263b3894@debian.org> <20230504112638.GA3013157@subdivi.de> <aaaccce6-1ecf-624e-cac3-8fdc791648e1@debian.org> <ZFUs94snrqK4X3Pc@argenau.bebt.de> <CAMw=ZnRNJ4L5Qwjn15Cf0yEFZ5XSYad4F070wq+wfcFTYwL0vw@mail.gmail.com> <20230506175434.GA720192@subdivi.de> <CAMw=ZnSAkS=GkNaRvSEFYwX8p3xv64FsdjgcERqR33uLy5=tYw@mail.gmail.com> <20230507055020.GA756628@subdivi.de> <CAMw=ZnRyzknWB+8xPmDmdMsijj079GC9D21026ymi-yKV4eC0A@mail.gmail.com> <20230517093036.GA4104525@subdivi.de> <20230517093036.GA4104525@subdivi.de> <[🔎] E1q7eEa-00CVvv-IM@mail.einval.com>
Steve McIntyre <steve@einval.com> writes:
> Raphaël Hertzog wrote:
>>
>>In the same spirit, I'd like to throw an idea... could we decide that
>>base-files is the first package to be configured as part of the bootstrap
>>protocol and change base-files maintainer's scripts into statically linked
>>executables so that they can work even if we don't have the library loader
>>on the ABI-compliant path?
>
> What exactly do you mean here? You know that even a statically linked
> executable needs an interpreter defined in the ELF header?
Maybe I'm missing something, but can't you code a different interpreter
path insto such a special purpuse script?
#!/usr/lib/x86_64-linux-gnu/ld-2.31.so /usr/bin/dash
echo foo
[ -e /lib ] || /usr/lib/x86_64-linux-gnu/ld-2.31.so /usr/bin/ln -s /usr/lib /lib
or whatever?
Bjørn
Reply to: