its Get-Blamed-For-Using-Gnome Day! post a screenshot of a folder u feel fond of or fabricate one to appear more interesting than u actually are. im kidding, u are interesting <3

didnt have much time today, sorry. im meeting with some old friends for … plant-based hotdogs and poker.

sooo have this for today.

lets keep screenshots family-friendly, okay? ~

i hope u have a lovely day and get to feel loads of fun things.

  • gandalf_der_12te@lemmy.blahaj.zoneEnglish
    2·
    10 hours ago

    in linux, (almost) every executable file (similar to windows .exe file) dynamically links to standard libraries. (“dynamic linking” means it links at run-time, rather than at compile-time). most link at least to a standard library called libc (standard C library).

    so when the program starts, before it actually executes any of its program code, the linker program is responsible for hooking up the program to any library that it needs. that’s the task of the linker, and that’s why technically, each time you start a program, the linker gets called before the program actually starts.

    idk why it’s in the root directory here.

    anyways: try the following: cat /usr/bin/bash | head or replace bash with any other program. you should see something like the following:

    where in the first few lines it says /lib64/ld-linux-x86-64.so that’s a reference to the linker that should be used.

    • beegnyoshi@lemmy.zipEnglish
      1·
      8 hours ago

      Ahh thank you for the explanation. I was asking in the context of the root of the configuration though, especially since nixos usually doesn’t use a linker at runtime anyway. Afaik, this process only happens to dynamically linked files, which nixos hates for some reason (although things like nix-ld and buildFHSenv exist) so most of the time statically linked executables are used instead.

      I was curious why someone would have that when they can just use nix-ld or yank it directly from nix’s glibc package or something