[debian] Notes on using OpenBSD under virt-manager

* CDROM must be SATA

* Remove the "tablet device" from the preferences, as I've encountered some issues with it. I'm using CWM on both the host and guest, and I've noticed some strange behavior with Virt-Manager. Specifically, when I use Alt + mouse to move a window, it affects the virtual window on the host instead of the guest.

[debian] nmtui error: settings plugin does not support modifying connections

Another 'cryptic' error from this goddamned OS, oh well... solution (as I read on various posts on web) :

edit  /etc/network/interfaces and remove any reference to the eg wired, reboot .

BTW keep the setting managed=true on /etc/NetworkManager/NetworkManager.conf in the case you use NetworkManager (nmcli etc )

[FreeBSD] Ouch ... ok lolz

I challenged my luck and tried FreeBSD again - for the xxth time, I can't really remember when was the last time.

Unfortunately, it failed to work well as a desktop on my system.

Especially disappointing was the lack of compatibility with my system, particularly the inability to resume from suspend to RAM. (Just for the record: OpenBSD* excels in this area!), last time I ve used it the sound was like sh*t... 

The software was in a similarly disappointing state, some packages frequent crashed (even obconf crashed, FFS). Interestingly, during the installation of various ports, I noticed that many of them lacked maintainers, so one day they may be removed. Oh well...  still a nice OS for servers.

 

* OpenBSD is really a champ.. >> VA-API (Video Acceleration API) imported into xenocara  , I am sure the day they implement gfx on vmm I will screw the linux partition once for all! (still need some apps that work with USB devices like oscilloscope..)

[ssh] oh no.. can't connect to the crap old server !

After installing a RHEL 9-based distribution, you might encounter difficulties when trying to SSH into crap older systems because of the newer, stronger cryptographic standards implemented by the operating system.

ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: error in libcrypto


Anyway, there are some ways to fix this

1. Allow legacy crap system-wide (be warned.. heh)

# update-crypto-policies --set LEGACY

# ...reboot

2. or create a coe a config file (say .legacy_ssh.conf)

.include /etc/ssl/openssl.cnf
[openssl_init]
alg_section = evp_properties
[evp_properties]
rh-allow-sha1-signatures = yes

and ssh to the legacy server/NAS etc via:

OPENSSL_CONF=./.legacy_ssh.conf ssh server.ip -l root


oh, btw , your old server etc may need extra params, in my case I need to set the Key Exchange Algorithm as +diffie-hellman-group14-sha1 so I have a special config on the desktop just for that server eg :

$ cat ~/.ssh/config

Host xx.xx.xx.xx

HostKeyAlgorithms +ssh-rsa
PubkeyAcceptedKeyTypes +ssh-rsa
KexAlgorithms +diffie-hellman-group14-sha1
MACs +hmac-sha1
PubkeyAcceptedAlgorithms +ssh-rsa


In fact that server (a darn NAS in fact) it's just for backups (backup of backup of backup , you have an idea) and it is under firewall, strictly local net, YMMV 

[flatpak] WSJTX / JTDX in effing dark!

FFS, those god-darn apps have no 'dark' theme esp under the fuckflatpak, so you are doomed to burn your effin eyeballs using it.. no more!! 

flatpak run edu.princeton.physics.WSJTX -stylesheet :/qdarkstyle/style.qss 

yes

HAM in dark FUCKING MODE !!! hurrah! 

it is working with JTDX - I think with any other KDE flatpak ...

[fun time] M5Stack cardputer effed up

 

 

Screen screwed. How did this happen? I just touched it while trying to move the cardputer, not even with a 'hard' grip! Indeed the display there is frigging fragile also there is ZERO protection - engineering failure or simply they just want to avoid the extra cost of a few ...cents (?) in order to put a piece of transparent plastic on top of the TFT (FFS really)

 

The bad news: the TFT part of cardputer is not avail, esp as I read on subreddit .

Fortunately, there is a compatible TFT display, that works with the M5Stack Stick.

You can find it usually on the web as "Display Module 135x240 SPI Interface ST7789V 1.14in", keep in mind you will need the 8pin version, alas comes with a shorter ribbon cable.
So I bit the bullet and ordered that, and also an 8pin FPC ribbon extension cable along with an FPC coupler.

I think that if you can't find an FPC coupler you can use two 8pin FPC connectors soldered together, after all its just 8pins not 80 to solder..

Work in progress..

 

 to be update when parts arrive!

Notes:

• M5Stack useless support, no part avail so think well before buy this IoT !!

• FPC extension not quite compatible with the current setup, the FFC extension cable that I got is bit thinner (different manufacturers).

 

yeah!!! It is possible to fix the darn thing....

(oh btw... the displays came from China into a thin bag like crap... FFS some people)

 

 

fix annoying auto-save of PDFs on firefox

 Mozilla crackhead-devs setup by DEFAULT to save any online PDF you open, so in fact this is spamming your Downloads folder with unwanted crap. 

Solution: 

set browser.download.open_pdf_attachments_inline (about:config) to TRUE