One blocker is lack of equivalent for set trash (in #mutt).

trying out #aerc #email client

I have now kind of current state of desktop in both #x86 and #ARM ends :-)

1. i9-13900k / 64 GB / Intel ARC A-770
2. Mac Mini M2 Pro 12 12/19 core version / 32 GB

The 2nd is both the computer I do music with (i.e. my studio machine) and also #ARM test farm for #TPM. I compile ARM kernels with it and run them in VMWare Fusion, which provides nicely packaged #vTPM’s.

i find paying for #sublimetext and using it with #neovintageous much better option than #vscode, if I need a GUI editor e.g. in meetings. It is fast and uncluttered. If you write code normally in the #terminal with #neovim, vscode can feel a bit sticky, and also stressful because it has too much shit going on in the screen estate. Milliseconds do affect to the overall feeling just like they would when e.g. when playing with a MIDI keyboard.

And generally if it is not fully open source, I feel less worried to use an application where I pay a sum of money for the license. Because the profit is often acquired by some means anyway, it is the most transparent for me…

#remindertomyself

$ ps -T -o comm,policy,rtprio -p $(pgrep -w -d ',' irq) | egrep '(snd|hci)'
irq/148-xhci_hc FF      85
irq/147-ahci[00 FF      50
irq/203-snd_hda FF      90
irq/204-snd_hda FF      90

#renewed my accidentally #expired
@lwnnet #subscription. unintentionally i had used single time payment last year (before that i was using corporate subscription while i was still working at intel). now it is set to automatic payment like it should be :-)

i have now kind of "#intel of the present day" #desktop configurtion in my main #development machine: i9-13900k with 64GB of DDR and Intel Arc A770 GPU.

ive been waiting the day to get rid of shitty #nvidia #hardware, causing all the time compatibility issues...

on #macos (which I have in my #university laptop, thus learning the ways) the easiest way to do #linux #kernel development and testing is podman (brew install podman). each container will have a #QEMU instance backing it up.

that sorted out, using macos does not really make any difference, as full-screen #tmux is pretty much the same always :-) any desktop that can launch a web browser is good enough desktop for me really...

this is how i deal with #password's. i protect the critical passwords with #PGP public key. Any password where #leakage is not an existential question is offloaded to #lastpass. The keyring itself is protected by #yubikey. i feel overally pretty safe :-)

@bitzero Another perspective is that for a kernel developer, it is an asset to have devices and machines running different operating systems for multitude of reasons :-) It is always good to have references...

@bitzero i use my desktop pc anyway for anything more serious when it comes to development (i9-13900k/64GB). possibly i would consider otherwise if it was the only machine i could use

@bitzero There's no VM image getting deployed to the external drive, as I already denoted in my text. Provisioning USB device nodes is trivial in all popular VMM's of which I'm aware of at least.

Considering #Apple silicon #MacBookPro’s: #VMware #Fusion combined with an #external #drive is an option worth of considering for running #Linux.

By provisioning direct access (aka pass-through) to the USB device for the guest, VFS and page cache of the host OS get surpassed, and disk access is as fast as it can ever be.

The resulting hard drive is (obviously) a real bootable Linux installation, not a VM image, which can turn out to be a real life-saver some day (e.g. if laptop dies).

For #development tasks the resulting overhead compared to a #native installation should rarely be any sort of problem because #throughput is nearly identical. The resulting #latency hit matters only for soft real-time (e.g. video post-production and along the lines).

I got MBP from @NISEC_TAU, so I have had to find a solid “Linux strategy” for it during last few days [1] :-)

[1] https://twitter.com/nisec_tau

:𝚙𝚞𝚝=&𝚐𝚞𝚒𝚏𝚘𝚗𝚝 #notetomyself #neovim

Note: I take special care to set the install folder for VST2's to to Common Files/VST2 in order of this scheme to work.

This is the way I sync all this in a script called `yabridge-refresh`:
````
#!/usr/bin/env bash

yabridgectl list | xargs -I{} yabridgectl rm '{}'
find ~/Documents/Yabridge/ -regex '.*\(VST2\|VST3\)$' -exec yabridgectl add '{}' \;
yabridgectl sync --prune
```
It is nice to do it like this because then well-behaving plugin families do not get hit from the shittier ones :-) And bit more structuring also gives more clean way to test whether a plugin has chances work at all.

Organizing #wine folders for #yabridge #linux #audio #vst #vst3 #clap

tag spam because i'm really in new territory so any grayish riscv/keystone/etc. tips and knowledge is welcome ofc. I'm at day zero with RISC-V so to speak :-)

Looking at https://github.com/keystone-enclave/linux-keystone-driver/tree/master/linux-keystone-driver and how much I need cut it and migrate arch/riscv to make something similar as tpm_ftpm_tee. #linux #kernel #tpm #ftpm #keystone #riscv #arm #trustzone #tee

by trial and error found workaround for #Qt application (read #neovim-qt) launching inside #WSL guest: ln -sf /mnt/wslg/.X11-unix /tmp/.X11-unix