Hi DJ,

> Date: 2026-08-06 23:25:29-0400
> From: DJ Delorie <dj@redhat.com>
>
> Alejandro Colomar <alx@kernel.org> writes:
> > Hmmmmm, let's say you call execve(2) several times without any fork(2)s.
> > Assuming a that the program paths that you pass to execve(2) are all
> > dynamic ELF programs built with glibc, I guess for every time you call
> > execve(2), ld.so(8) will be run, and the tunables stored in ld.so.cache
> > will be used.  Is this correct?
> 
> I think this rabbit hole is too deep for this part of the man page.  We
> need a short sentence that's obvious to the reader, not a diatribe on
> how the linux kernel works.
> 
> I'm happy with something like "The resulting data is read when the
> program starts." regardless of how ambiguous or technically incorrect it
> might be ;-)

I'm not happy with starts, but if 's/starts/is executed/', or
alternatively 's/starts/& execution/', I'm happy.

'starts execution' is precisely the wording that execve(2) uses to
describe the moment when ld.so(8) is called.

     If the executable is an a.out  dynamically  linked  binary
     executable  containing shared‐library stubs, the Linux dy‐
     namic linker ld.so(8) is called at the start of  execution
     to  bring  needed  shared objects into memory and link the
     executable with them.

Does this sound good to you?


Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es>