• DaddleDew@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    16 days ago

    I’ve been using Linux for over 2 years. When does that part when I think I know how it works kicks in? I didn’t get it.

    • yeehaw@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      16 days ago

      I dunno, I’ve been using it since like 2012 and I still have no idea sometimes when it breaks.

    • OpenStars@discuss.online
      link
      fedilink
      English
      arrow-up
      1
      ·
      16 days ago

      Read the meme: you already passed it long ago!

      (Though there is a second stage that kicks in when you manage to grow a grey beard - which is particularly impressive if you are a woman!)

    • AlligatorBlizzard@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      15 days ago

      Statistically yes, but also you’re noticing a lot more because Lemmy creates those guys. Source: random guy. (Although I’m actually the low end “who the fuck knows” on the IQ chart version of this meme.)

        • redjard@reddthat.com
          link
          fedilink
          arrow-up
          2
          ·
          3 days ago

          Understand on what level?

          The basic idea is that dbus is a type of communication layer and api.
          Services can register there and programs see their registrations. dbus can in theory then launch a service too, so things don’t have to run all the time.
          The idea is similar to having some known config file, that programs write to and that a service listens on or uses later. But dbus has more granularity.

          It also often runs the other way, with system components presenting info in dbus and programs using it, to adapt to user configuration.

          And let’s not even get into udev.

          Point here is that dbus could be implemented via a command and an sqlite database for example. The command checks the database and constructs the dbus state from it.
          But for likely performance reasons it isn’t, so this info is simply hidden in dbus, in ram, instead of being a file.

          You can access dbus via a socket file ofc, but it’s not like you can mount it.

          Even more confusingly, the internal ephemeral dbus structure with its apis and endpoints resembles a filesystem. In that way it is similar to the w!ndows registry, though not nearly as bad.

          so yeah dbus is most definitely not files

          edit: also there’s multiple dbusses, usually one per user and one for the system. Those two hold different apis and info. It’s just the same thing twice tho.

  • uderecife@piefed.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days ago

    24 years exclusively running it.

    Short answer: magic.

    Long answer: a stressful full week trying to get everything right, followed by a long, blissful period forgetting how hard it was to get it up and running like magic.

  • hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    16 days ago

    It takes the raw code, bakes it at 450°F for 90 minutes, then does some magic.

    • Theoriginalthon@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      15 days ago

      First you get a file(kernel source), then use another file to change the file, then you have a kernel, but the kernel(file) in the the file system, then use a magic boot file to run the file. That’s basically it?

  • Zeniv@lemmy.quasarke.net
    link
    fedilink
    arrow-up
    1
    ·
    13 days ago

    Well. ACTUALLY, it’s very simple you see every time you spin up a new linux box a little piece of Linus Torvold’s soul get’s imprinted in the CPU registers and then that fragment handles everything from there.

    • lime!@feddit.nu
      link
      fedilink
      arrow-up
      1
      ·
      14 days ago

      except that thing. …and the other thing. that thing used to be a file but it’s not anymore. that’s only a file if you use this specific shell. that one is a file system, but there’s no files in it. oh don’t touch that file, that’s deprecated. oh that’s only a partial file, you need to open this one too otherwise it breaks.