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.

text says "today is *post a screenshot of a folder* day! go on! take a screnshot of a folder and post it in the comments! we will all comment on it. made by maria on lemmy with Krita within 5 minutes". the background is colorful and looks like colorful yellow greenery. there is a screenshot in the center of a Pictures folder. things standing out are: images of salt sticks, tofu, potatoes and quark, potato fritters, a purble place game screenshot, lesbian flag image, lemmy icon, lesb_post.png, krita_girl_has_new_drip.png and plenty files named "xxx_letter.png" where the word before "letter" is marked out with black.
you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 3 months ago (6 children)

May i present, the source folder for my operating system.

  • source
  • hideshow 6 child comments
  • [–] 1 point 3 months ago (5 children)
  • [–] 4 points 3 months ago (1 child)

    In this case it's because the compiler would like to link to the standard library (which doesn't exist in this case, this is a kernel). Additionally i need a specific binary file layout, that's what the linker script is for.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 3 months ago* (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 months ago (1 child)

    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

  • source
  • parent
  • hideshow 1 child comment