Back in the good days when vim users were vim users and nobody knew you were a dog. When buying a video card could be as casual as a network card.

I guess AnandTech (RIP) had taken over the mantle next to you guys by then if memory serves right?

The expected payout is negative so no, not similar to investing. It becomes the opposite, pretty much.

💁🦋

I think that might be the same chip as the Bananapi M7 which I did a write-up on last year. Trying a different kernel might help with your issue - it did for me.

https://blog.kumio.org/posts/2025/01/bananapim7-hvm.html#kernel-versions

I should probably update the table for trixie.

Terrible headline. Should have just been “Rockchip has…”.

Am I showing my age if I say that Tomshardware used to be decent?

No one talks about how Alpine has been doing immutable and atomic installations since way before it was trendy.

https://wiki.alpinelinux.org/wiki/Immutable_root_with_atomic_upgrades

deleted by creator

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

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.

ruh-roh

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.

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.

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.