DefederateLemmyMl

  • Gen𝕏
  • Engineer ⚙
  • Techie 💻
  • Linux user 🐧
  • Ukraine supporter 🇺🇦
  • Pro science 💉
  • Dutch speaker
  • 0 Posts
  • 140 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle
  • Due to the energy crisis in Europe at the beginning of the Russian invasion of Ukraine, as a cost saving measure some cities here in Belgium decided to turn off the street lights at a certain time. I think they went dark at 23:00 or 22:00, so your Cinderella Lighting scenario.

    I thought it felt quite peaceful to have some true darkness, and wouldn’t mind it back, but at the same time if you had to walk outside at that time, it could feel a bit unsettling even if I live in a very safe neighborhood. I also found that there were some practical issues like, not being able to see obstacles or the state of the pavement, so you had to tread carefully. I’d definitely buy a decent flashlight if they implement that again.

    Later, I suppose after complaints from citizens, they reverted to turning only every other streetlight off. I didn’t like that at all, it was the worst of both worlds. There were still patches where you couldn’t see properly, but none of the peaceful feeling of true darkness. Since a year or so it’s back to all streetlights all night.







  • I ran it perfectly on a 33MHz 486 with 4mb RAM for a long time. Even Doom II with some of its heavier maps ran fine.

    “Perfectly” would mean it ran at 35fps, the maximum framerate DOS Doom is capped at. In the standard Doom benchmark, a dx33 gets about half that: 18fps average in demo3 of the shareware version with the window size reduced 1 step. Demo3 runs on E1M7, which isn’t the heaviest map, so heavier maps would bog the dx33 down even more.

    I’m sure you found that acceptable at the time, and that you look back on it with slightly rose-tinted glasses of nostalgia, but a dx2/66 and preferably even better definitely gave you a much better experience, which was my point.


  • If anyone can enlighten me, This is pretty much why you can find DooM on almost any platform BECAUSE of its Linux code port roots?

    I mean yeah. Doom was extremely popular and had a huge cultural impact in the 90s. It was also the first game of that magnitude of which the source was freely released. So naturally people tried to port it to everything, and “but can it run Doom?” became a meme on its own.

    It also helps that the system requirements are very modest by today’s standards.


  • It ran like absolute ass on 386 hardware though, and it required at least 4MB of RAM which was also not so common for 386 computers. Source: I had a 386 at the time, couldn’t play Doom until I got a Pentium a few years later.

    Even on lower clocked 486 hardware it wasn’t that great. IIRC, it needed about a 486 DX2/66 to really start to shine.



  • Without knowing what was being hosted, the only surefire way would be pulling a complete disk image with cat or dd.

    That’s not surefire, unless you’re doing it offline. If the data is in motion (like a database that’s being updated), you will end up with an inconsistent or corrupt backup.

    Surefire in that case would be something like an lvm snapshot.

    If you wanted to stay on a similar system, RHEL 9 would be a good option or one of its “as similar as possible” like AlmaLinux.

    No love for Rocky?

    Also Oracle Linux is still free, and fully compatible with RHEL.


  • How the fuck am I supposed to know that Network Manager won’t support DNS over TLS

    Read the documentation? Use google?

    The very first hit when you google “dns over tls tumbleweed” provides the answer: https://dev.to/archerallstars/using-dns-over-tls-on-opensuse-linux-in-4-easy-steps-enable-cloud-firewall-for-free-today-2job

    A more generic query “dns over tls linux” gives this, which works just the same: https://medium.com/@jawadalkassim/enable-dns-over-tls-in-linux-using-systemd-b03e44448c1c

    Both google searches return several more hits that basically say the same thing.

    Even the NetworkManager reference manual refers you to systemd-resolved as the solution: https://www.networkmanager.dev/docs/api/latest/settings-connection.html

    Key Name Value Type Description
    dns-over-tls int32 Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: “yes” (2) use DNSOverTls and disabled fallback, “opportunistic” (1) use DNSOverTls but allow fallback to unencrypted resolution, “no” (0) don’t ever use DNSOverTls. If unspecified “default” depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

    I don’t use NetworkManager, I’ve never even used Tumbleweed and I found the answer in all of 10 minutes. Of course that doesn’t help if you’re so clueless that you didn’t even know that you were using DNS-over-TLS, or that DoT is a very recent development that differs significantly from regular DNS and that it requires a DNS resolver that supports it.

    when every other operating system does?

    Like Windows 10? (Hint: it doesn’t)

    You use Arch. Mr skillful

    Who cares what I use. When I’m messing with something I don’t understand, I at least read the documentation first instead of complaining on the internet and calling the whole community toxic and, I quote, “Butthurt Linux gobblers” when you get the slightest bit of pushback.







  • DefederateLemmyMl@feddit.nltoArch Linux@lemmy.mlChoosing Next OS
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    5 months ago

    But everyone says its always breaking and gives problems. That’s because of users, not OS… right?

    It’s an exaggeration, it doesn’t always break but yes it occasionally does. Any Arch user who tells you otherwise is lying or hasn’t used Arch for very long yet.

    That’s because of users, not OS… right?

    No it’s because of regressions in new releases. Arch relentlessly marches forward and always tries to give you the latest-and-greatest version of any package on your system. There is some testing done obviously, but it can never be ruled out that newer software contains new bugs and regressions that are not caught in testing, and that it ends up being released.

    To give an example of such a regression, the past few weeks there have been some kernel releases with broken bluetooth support for the (very common) Intel AX200 chipset. It is fixed now, but if you wanted to use bluetooth, Arch was in fact broken for some time.

    The fix is usually: temporarily rollback the offending packages until the issue is fixed upstream or until a workaround is found. It does mean you will occasionally have to spend some time diagnosing issues and checking user forums to see if other users are having the same problem.