Blog

Main posts for this site
#gaming #legacy

LHX Attack Chopper- sim game from 1990

Category: feed

I used to play this a lot in my early childhood. Games back then were made with passion, love, and attention to detail. Even though computer power wasn’t as high as it is now, especially for sim-like games, some games were pretty immersive.

This game is called “LHX Attack Chopper” it was made in 1990 by Brent “Buzzboy” Iverson. (published by Electronic Arts.) Buzzboy later designed legendary Chuck Yeager’s Air Combat.

I remember playing this with my father on an old 386DX CPU. Take a look at this screenshots I made recently.

#utils

LogSeq - notes taking application

Category: feed

Found this interesting project called LogSeq.

Its hardcore, privacy-first notes taking app, knowledge base, might be even compared to org-roam.

Features

  • Markdown, Wiki-alike, Plain text format
  • Local first which means it saves everything locally, and if you want it can synchronize
  • Mobile App for both platforms iOS/Android
  • Obsidian like intrerface with interlinking and visual graph
  • It’s org-mode inspired, supports org-mode formatting
  • Plugins market place with various plugins

Probably will be most popular tool after Obsidian for average ppl very soon.

https://hub.logseq.com/getting-started/uQdEHALJo7RWnDLLLP7uux/an-overview-of-50-logseq-features/jn3RC9eBF3ofpjaLtxXrDe

https://logseq.com/

#dev, #utils

Benchmarks code for CPU testing

Category: link

Various benchmarks to launch to load CPU

https://benchmarksgame-team.pages.debian.net/benchmarksgame/

Ruby Example:

# The Computer Language Benchmarks Game # https://salsa.debian.org/benchmarksgame-team/benchmarksgame/ # Contributed by Wesley Moxam # Modified by Sokolov Yura aka funny_falcon # Parallelised by Scott Leggett # Thread.exclusive deprecated require 'thread' module MiniParallel class Worker def initialize(read, write) @read, @write = read, write end def close_pipes @read.close @write.close end def work(index) Marshal.dump(index, @write) Marshal.load(@read) end end def self.map(array, &block) work_in_processes( array, [array.size, core_count].min, &block ) end def self.core_count @@core_count ||= IO.read("/proc/cpuinfo").scan(/^processor/).size end private def self.work_in_processes(array, count, &block) index = -1 results, threads = [], [] mx = Mutex.new workers = create_workers(array, count, &block) workers.each do |worker| threads << Thread.new do loop do mx.synchronize do index += 1 end break if index >= array.size results[
                        More
                    
#linux, #debian, #event

Debian 30 years behind

Category: link

https://bits.debian.org/2023/08/debian-turns-30.html

I am using Debian since later "Potato" distribution. Debian is one of the good distribution back in the time, today is even better. Take a look at this newsgroup message from Ian Murdock this is how Debian was created.
 From portal!imurdock Mon Aug 16 06:31:03 1993 Newsgroups: comp.os.linux.development Path: portal.imurdock From: imurdock@shell.portal.com (Ian A Murdock) Subject: New release under development; suggestions requested Message-ID: <CBusDD.MIK@unix.portal.com> Sender: news@unix.portal.com Nntp-Posting-Host: jobe.unix.portal.com Organization: Portal Communications Company -- 408/973-9111 (voice) 408/973-8091 (data) Date: Mon, 16 Aug 1993 13:05:37 GMT Lines: 86 Fellow Linuxers, This is just to announce the imminent completion of a brand-new Linux release, which I'm calling the Debian Linux Release. This is a release that I have put together basically from scratch; in other words, I didn't simply make some changes to SLS and call it a new release. I was inspired to put together this release after running SLS and generally being dissatisfied with much of it, and after much altering of SLS I decided that it would be easier to start from scratch. The base system is now virtually complete (though I'm still looking around to make sure that I grabbed the most recent sources for everything), and I'd like to get some feedback before I add the "fancy" stuff. Please note that this release is not yet completed and may not be for several more weeks; however, I thought I'd post now to perhaps draw a few people out of the woodwork. Specifically, I'm looking for: 1) someone who will eventually be willing to allow me to upload the release to their anonymous ftp-site. Please contact me. Be warned that it will be rather large :) 2) comments, suggestions, advice, etc. from the Linux community. This is your chance to suggest specific packages,...
                    
                    
                
#github

Ancient english helps closing PRs // Github

Category: social

I’ve tried to use this ancient english message as a comment for PR review to bring attention

I bid thee good tidings. I beseech thee to take heed, for lo, several moons have waxed and waned since this comment hath been inscribed, yet it remaineth unresolved. I humbly beseech thee to attend to this matter forthwith, that we may advance the pull request without further delay.

After this message PR was closed, and even branch was deleted due to its obsolete.

#linkedin

Agile clown show // Linkedin

Category: social

The Agile coaching industry has become a parody of itself because of #agileclownshow, using buzzwords without actually providing any substantial value. It's as if they claim to know the solution to a problem but have no understanding of the problem itself. The issue with Agile coaching is not just the lack of expertise, but also the audience and those in charge. Just as a teacher must have experience in a subject to effectively teach it, an Agile coach must have experience in the business world. Simply put, they must have a track record of producing results, both positive or negative, before they can effectively coach anyone. If not then red nose and fancy hair should be the working suit.

Even more horrible is the fact that agileclowns make new agileclowns each show performed.

#linux, #virtualbox, #kernel

How to sign VirtualBox kernel modules when you're on secure boot

Category: share

When you’re installing VirtualBox on a system with Secure Boot enabled, the installation process requires kernel modules to be loaded that are not signed by the system’s Secure Boot key. In this situation, you have two options:

  1. Disable Secure Boot in BIOS: This option involves going into the system’s BIOS settings and disabling Secure Boot. This will allow the installation process to proceed without any further intervention.

  2. Sign the kernel modules: If you prefer to keep Secure Boot enabled, you can sign the required kernel modules with a key that is trusted by the system’s Secure Boot infrastructure. This involves generating a new key pair, importing the public key into the system’s key store, and using the private key to sign the kernel modules.

Create new key and enroll it with MOK

1 2 3 4 
sudo mkdir -p /var/lib/shim-signed/mok sudo openssl req -nodes -new -x509 -newkey rsa:2048 -outform DER -addext "extendedKeyUsage=codeSigning" -keyout /var/lib/shim-signed/mok/MOK.priv -out /var/lib/shim-signed/mok/MOK.der sudo mokutil --import /var/lib/shim-signed/mok/MOK.der sudo reboot 

Sign modules with new Key

1 2 3 4 5 6 7 
#!/bin/bash for modfile in $(dirname $(modinfo -n vboxdrv))/*.ko.xz; do echo "Signing $modfile" /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 \ /root/signed-modules/MOK.priv \ /root/signed-modules/MOK.der "$modfile" done 

The steps you’ve outlined above describe how to perform the second option. The script you’ve provided will sign all the VirtualBox kernel modules that are present on the system. Once the modules have been signed, they will be allowed to load by the system’s Secure Boot infrastructure.

It’s worth noting that signing kernel modules is a security-sensitive operation, and you should take appropriate precautions to protect the key material. Also, the exact steps for signing kernel modules may vary...