Notices by Zygmunt Krynicki (zygoon@fosstodon.org)

I've just released mount-insight v0.1 https://gitlab.com/zygoon/mount-insight/-/releases/v0.1

Here's an excerpt from the release notes:

This is the initial release of mount-insight, a tool created to explore and display the data provided by the statmount system call.
Some features are only going to work once Linux 6.15 is released. The code needs to see matching, up-to-date headers for userspace Linux APIs as well.

CC @brauner

@organicmaps The aspect few people seem to mention is that any infrastructure operated in a given country needs to adhere to the law of the land.

What if it was hosted in Europe and someone from Russia or Belarus triggered a similar ban? Is the implementation bad and not transparent? Sure! Is this a problem of US and GitHub specifically? Not at all.

Even when you host your own instance, men in black boots can kick your door and take you away along with your hardware.

I routinely run my phone in power saving mode. The amazing devices with multi day battery life are all around us, we just choose to run them into the ground with loads of background activity and occasional high-refresh-rate scrolling.

I found an incompatibility between #SWIG 4.3 and #apparmor that I don't fully understand. A tuple created with %append_output contains an extra argument. This is noted in the SWIG 4.3.0 changelog but I don't know how to fix this while the typemaps are shared between python, perl and ruby.

I described the issue in the apparmor issue tracker, along with my analysis of 4.2 vs 4.3 wrapper at https://gitlab.com/apparmor/apparmor/-/issues/475

Do you know someone who knows swig and can shed some light on a possible solution?

You had one job ADATA.

Hey my #RedHat #CentOS friends. Is there a Cloud image for x86_64 that is compatible with EFI?

Images on https://cloud.centos.org/centos/9-stream/x86_64/images/CentOS-Stream-GenericCloud-9-latest.x86_64.qcow require BIOS boot mode.

Anyone?

GNU make 4.4 now supports --shuffle to allow a form of fuzz-testing rules for errors that may come up in concurrent builds.

That's really nice, I'll look at supporting this in zmk as well.

I think #introductions are in order. I'm an aging C/Python/Go developer circling around Ubuntu.

I've been involved in a number of projects, but most people recall me from my snapd work.

I'm mostly consumed by my day job, but I love to create small projects at the level of system tools and libraries. I use Linux, Windows, and MacOS, though I almost never code on anything but Linux.

Together with my wife, we look after our family: three kids, dog, and two cats.

@theron29 @zygoon I have a home test lab that runs and builds various things for me. I and not looking for a desktop. My ideal board has 8GB+ of memory and is not crippled by hardware design decisions or bugs. Something that can run Debian, Fedora or Ubuntu.

@theron29 @zygoon is that also significant for integer operations?

@theron29 as much as I like the fact that tiny boards _can_ run linux desktop, I'm much more interested in headless systems at present.

Coincidentally, I ran a Windows XP virtual machine with 256MB of ram and one CPU. The crazy speed at which everything ran on that system is a nice baseline to how slow our modern systems are. There's something lost, I think, in how we make software.

I'm contemplating getting a #RISCV board for use at home. I ruled out the enterprise systems that are several thousand USD/EUR, as I plan to only use it for hobby capacity. Is there anything that is there to avoid? I recently learned that the SiFive boards have somewhat terrible memory performance, making them painfully slow for real world use. Any advice?