Spoiler

A meme with a emoji of a man doing a face palm.

Circular arrows around the emoji point to a repeating set of events:

  1. I meet someone
  2. We talk
  3. I say “I use Arch BTW”
  4. They leave
  • historicaldocuments@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    16 hours ago

    I haven’t compiled a kernel since I wanted PF in FreeBSD, and because that hardware wasn’t current for its day it took something like 22 hours. In today’s world IF it was Linux and IF I was using the same hardware then that’s functionally a DoS. There was a new bitlocker exploit today, and while supposedly limited in utility it’s going to cycle everyone through the update/reboot process again. I wonder what’s happening in parts of the world where overall bandwidth for a country is limited, or internet isn’t relatively cheap/easy.

    • Eli Schwartz@fosstodon.org
      link
      fedilink
      arrow-up
      2
      ·
      10 hours ago

      @historicaldocuments

      Well, if what you’re worried about is bandwidth and Internet connectivity costs more than any other factor, then you definitely want to compile from source. :)

      Given that compiling from source can provide you an entirely new kernel with fixes for security vulnerabilities, at the internet bandwidth cost of 50kb (or less) of downloaded incremental patch files.

      • historicaldocuments@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        26 minutes ago

        I hadn’t thought about it that way.

        Upon further investigation debian has an entire git system setup for exactly the use case I was thinking of. It looks like it lets you clone just the packages you’re interested in and maintains the infrastructure to build debian packages locally, so over time it would decay to just pulling source diffs. If I understand that correctly that’s pretty neat.