I have now a registered private company for the sake of being a contractor starting from October: Siltakatu Solutions Oy (aka Ltd).

Siltakatu is my home street [1] in #Tampere and I try to find solutions for various issues in software engineering, so by combining these two facts I got a company name 🤷

Sometimes my solutions suck tho but I do not imply anything about quality in my "company brand" ;-)

[1] The #Finnish word silta translates to bridge and katu translates to street.

One wisdom that applies both understanding math and programming in deeper level and navigating through that jungle: be stupid and try not to understand 🤷 Stupid is the new smart.

A power user belongs to a category of users who use computers just for the sake of using them, and that is the overall main goal of using a computer.

I like Low Level Learning Youtube-channel but with this I have I have to totally disagree: https://www.youtube.com/watch?v=3T3ZDquDDVg

The golden rule for writing code and debugging is obviously:

1. Do the most simplest and least scalable trial at first.
2. If that does not scale take a more powerful tool.

I certainly know how to use core files but it is MORE EFFORT.

The way I see it how blockchains are is like early 90s, 9600bps modem and dial up. One practical issue that they might perhaps solve is mapping the dark matter of revenue streams that are ”below two decimals”.

I think their key application is a "pay for utilization" cost model, instead ”pay for subscription time” as an option. I've used a S3 storage service Storj for some time and for my use this has been quite effective.

Starting from October, when my research contract ends, I'll be joining Parity as compiler and virtualization engineer: https://www.parity.io/

Since https://github.com/RustScan/RustScan claims to be fast I tried first a trivial SYN scan to my file server:

sudo nmap -sS -p- haaparousku

I got the list of ports in about one second (bit more or less). Then I tried rustscan and got bored enough to finally SIGINT it:

rustscan --addresses haaparousku

Not sure I get the improvement here… Also command-line is not “tactile :-)

Something definitely to improve in Rust command-line apps is not to think arguments as an object tree that you feed into clap crate. That’s just lazy.

Instead a better metaphor for a great command-line interface is something like a game pad that you can “play” easily. That’s why nmap has been relevant for decades.

#AI #brain collapse

https://www.nature.com/articles/s41586-024-07566-y

Glue on pizza is apparently not enough, how about bogus AI mushroom foraging books
https://www.reddit.com/r/LegalAdviceUK/comments/1etko9h/family_poisoned_after_using_aigenerated_mushroom/

#ai

I guess I could create my own XML parser which then outputs run-qemu.sh.

I even used to bootstrap qemu and swtpm for every single build at one point ;-) It is great when testing kernel features when you can always start from known state.

@stsquad I generate the whole operating system for each kernel test build. I don't have a machine description when I start compiling it.

Essentially each test VM is also one shot, deleted after a single test run.

Basis is like https://codeberg.org/jarkko/linux-tpmdd-test

@janotomko It would be easier to have a few template configurations and XML can be more easily post-manipulated.

Registration for @linuxplumbersconf reopened

'"This year there was a huge demand to attend #LinuxPlumbers Conference in person and at last we were able to add more places and reopen the registration."'

https://lpc.events/blog/current/index.php/2024/08/16/registration-is-now-reopened/

#Linux #kernel #LinuxKernel #LinuxPlumbers2024

Hallituksen halu poistaa työntekijöitä maasta on outo https://www.hs.fi/mielipide/art-2000010631106.html
Outo, typerä, paha, valitse adjektiivisi. Taantumuskopla on sitä kaikkea.

It would be sometimes useful if #QEMU w/o libvirt could interpret domain XML to some level.

Like for instance if you want to CI kernel, that would be one use case for this.

For the sake of example, here’s the QEMU command-line that I use as starting point for any kernel testing/CI:

qemu-system-x86_64 \
  -M pc \
  -monitor unix:monitor.sock,server,nowait \
  -serial unix:serial.sock,server,wait \
  -drive file=disk.img,if=virtio,format=raw \
  -net nic,model=virtio \
  -net user,hostfwd=tcp::10022-:22 \
  -rtc base=localtime \
  -nographic \
  -chardev socket,id=chrtpm,path=${SWTPM_DIR}/swtpm-sock \
  -tpmdev emulator,id=tpm0,chardev=chrtpm \
  -device ${QEMU_TPM_DEVICE},tpmdev=tpm0 \
  -bios /usr/share/edk2/ovmf/OVMF_CODE.fd \
  "$@"

These people are not real. Just like from some bad 70s/80s B films. I bet he does "evil laughter" in front of mirror or something o_O https://edition.cnn.com/2024/08/15/politics/russ-vought-project-2025-trump-secret-recording-invs/index.html

First pull request in preparation after holidays and it is over two weeks past. I blame all those nasty interviews ;----)

https://soatok.blog/2024/08/14/security-issues-in-matrixs-olm-library/

@vitaut Tbh, this would apply better on Rust than C++, given that usually C++ developers do not impose blind trust on compiler ;-)