Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K

kumi

@ kumi @feddit.online

Posts
3
Comments
108
Joined
8 mo. ago

  • NAS build guidance - choice paralysis

    Jump

  • Personally I'm too paranoid about security and sus of Intel to be comfortable with vPro but you do you.

    That said, I'd go for 1, considering you already have that 6th gen on hand in case you need a spare.

    Otherwise 3 or 4 (whichever is available on secondary markets for a decent price) and hang on to that Pentium in case need arises. Doesn't sound like the extra power draw of an i7 is worth it for this build.

  • Self hosting hardware - what are your experiences with Lenovo ThinkCentre as homelab server?

    Jump

  • Up to 300 or so could be reasonable if the RAM and SSD are decent.

  • Featured

    Okay why is your distro the best?

    Jump
  • Featured

    Okay why is your distro the best?

    Jump

  • Dealing with faulty RAM modules in 2026

    Jump

  • I'm curious: What's motivating you to do that when the memmap param can do the same without patching?

  • State of the Fin 2026-01-06 | Jellyfin

    Jump

  • SWIM has a sizable aged library - wouldn't be surprising with sqlite db corruptions by now - and absolutely no issues smoothly upgrading amd migrating to 10.11. Had sweaty upgrades a few times over the years but this was not one of them.

  • Flatpak program (FreeCAD) running itself as superuser?

    Jump

  • Good question and without looking closer or verifying I'd guess it actually doesn't.

    Usually such things happen because at some point someone had an issue with accessing a hardware device or something and this became the "fix" perhaps because udev was confusing.

    If someone cares enough about it, tidying up loose flatpak packaging ends like that is often appreciated and a great way to contribute.

  • OpenWRT router

    Jump

  • Rule of thumb for OpenWRT:

    In general for consumer routers, Broadcom-based ones like the one posted require a lot of work and hacking to port and maintain. If they’re even working with OpenWRT at all it can be quite dicey and troblesome if you are not very lucky.

    In comparison, Mediatek-based models tend to be better supported and smoother sailing.

    I haven’t seen much of Qualcomm but I’d guess they fall somewhere closer to Broadcom.

    So no, I don’t think it’s a good pick. If OP got it handed down for free it might be worth a shot but I would buy something else if the purpose is to run OpenWRT or any Linux or BSD on it.

    Source: Installed OpenWRT on many different devices over the years, including one with the same chipset

  • OpenWRT router

    Jump

  • State of the Fin 2026-01-06 | Jellyfin

    Jump

  • Now if we could just sort the jf collections type in ways other than by date ;)

    Sounds like Good First Issue material! (;

  • Flatpak program (FreeCAD) running itself as superuser?

    Jump

  • ruh-roh

  • Flatpak program (FreeCAD) running itself as superuser?

    Jump

  • Is the Flatpak version running inside it’s own “box” and it isn’t getting SU permissions across my whole system?

    Indeed it is running sandboxed!

    Same principle as running uid 0 inside a rootless container.

    You can poke around a shell inside the sandboxed environment with flatpak run --command=bash org.freecad.FreeCAD and tweak access with FlatSeal.

  • GNOME and Mozilla Discuss Proposal to Disable Middle Mouse Paste on Linux

    Jump

  • Configuration UI can be added regardless of what happens with defaults. Defaults change is not a blocker for exposing configurability. If anything I'd say you got it backwards: Don't switch long-standing defaults until there is a discoverable and accessible way to change it.

  • Dealing with faulty RAM modules in 2026

    Jump

  • Thank you, I'm glad you like!

    not having worked with memmap before, it is not immediately obvious to me which hex means what (I am guessing RANGE@START? ). Would be nice to have a link to an explanation there.

    I just have the link to the kernel docs because I think they do a better job explaining it than I would 😁

    But yeah, basically. Except for this use-case you want RANGE$START not @. And you can use human sizes like 128M$RANGE.

  • Dealing with faulty RAM modules in 2026

    Jump

  • There is one part in the post mentioning how to "pad holes" in failing areas. Maybe I should expand it with some details around aligning reserved address space.

    Otherwise, corruption of the RAM itself does not usually spread like mold in bread or wear out and fail in similar ways to flash memory.