

Suicidally bad naming is the one thing we can always rely on Microsoft for


Suicidally bad naming is the one thing we can always rely on Microsoft for


For something pretty low level and gigantic, Mesa (or at least RADV) is a pleasure to hack on. It has a great config system (meson), compiles super fast, has lots of debug functionality, and can easily be loaded into e.g. a game, without any system level configuration.


Yeah I’ve seen this a few times recently.
I think it might be https://github.com/LemmyNet/jerboa/issues/1711
Strange, I’ve never seen that. Have you rebooted the system to make sure it has nothing to do with open files?
I did find one thread that seems related:
https://www.reddit.com/r/btrfs/comments/lip3dk/unreachable_data_on_btrfs_according_to_btdu/
btdu is an excellent tool for finding out what’s taking up space in btrfs


Were you running dmesg on another screen or over ssh or something? I’d look in journalctl -b-1 after a reboot.
Is it completely frozen or does it respond to pings etc?


Were you running dmesg on another screen or over ssh or something? I’d look in journalctl -b-1 after a reboot.
Is it completely frozen or does it respond to pings etc?


deleted by creator


Image: Office of Speaker Mike Johnson.
Ouch


This sounds like good engineering, but surely there’s not a big gap with their competitors. They are spending tens of millions on hardware and energy, and this is something a handful of (very good) programmers should be able to pull off.
Unless I’m missing something, It’s the sort of thing that’s done all the time on console games.


Have you checked these all on winehq? It would be nice for them to be reported with logs if they haven’t already.
Garmin Express for example is on there with some discussion here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40213
It might not help in the short term, but even just having logs for more broken programs could be useful for the wine project.
Is there a reason you’re suspicious about that particular dependency, or are you just asking about dependencies in general?


I’d probably:
systemctl suspendWhen the screen fails to wake, are you able to get it back by powering it off, or by unplugging it? Is it X or wayland?


Of course not, but you have to either trust your users to some extent or give them a system that’s locked down to the point of hindering them.


What is ‘unallowed software’? A shell script the user wrote? Something they downloaded and compiled?
Limiting that seems fundamentally at odds with FOSS.


Emacs I assume.


cmake compiles to makefiles as well (it just also supports some other backends). I’m not sure why that matters though. In both cases the makefile is generated.
If you stop shipping autotools generated artefacts in your tarballs, things will be a lot simpler.
Weirdly enough the malicious code does look eerily similar to the benign code, because both are unnecessarily obfuscated.
This is not a human written or readable file you’re talking about. It’s a generated script.


the wilds of Nova Scotia
Walking across the Windsor Street exchange is wild for sure.
It obviously won’t work for everyone, but for remote access I’ve been very impressed with waypipe. I use it to pull windows from headless machines onto my main workstation, like X forwarding.
I’d like something for persistence, like wprs, but it’s not quite there yet.