Hetzner (like many other providers) do not provide #OpenBSD machines.. but there is a nice #syadmin trick to install your beloved OS over whatever they provide. In this video we will see how you. In short: 1. Create your #GNU / #Linux machine 2. Login, wget & dd the IMG 3. Reboot in Console and install using network installation (say http packages) 4. Reboot in your new OS 5. Have fun. Here is my video of above steps... with some more info, discussion and fun :)

Reminder: #Nostr is decentralize. Change your client, start your relays. Keep it decentralized. Decenteralization is not only a tech concept, but a metnal one. Search for clients and try them. Contribute and have fun.

Have 10mins to deepen your understanding of #Unix like systems? Check the utistd.h page. This is the header file that provides access to the POSIX operating system API. Even a quick browse can show you how your program talks with your OS.

unistd.h - Wikipedia

For example whenever your program needs a higher privilege (or to act as another user), it calls `setuid` for that. Or starts with `sudo/doas` to have a higher access but calls `setuid` to become "nobody" in most of its life cycle. If still have a click to spare, check the setuid.h on #OpenBSD man pages:

setuid(2) - OpenBSD manual pages

in most cases OpenBSD man pages are the best references you need to understand the OS. #BSD #Linux

I was sending a minor PR to the uutils / #coreutils project regarding a breaking test on #NetBSD and thought its a good opportunity to record a video and: - talk about the uutils/coreutils which is a rewrite of coreutils in Rust - show the #NetBSD env and do some coding in it - Show the flow of sending a PR on #github

Everyone else: @jack is not on blah blah... We on #nostr: jack is here.

Moved my mastodon account from Mastodon.social to bsd.cafe . Why? to support the decentralized nature of mastodon, promote the federation and encouraging people to be part of smaller inter-connected communities. So if on mastodon, find me at @jadi@bsd.cafe

Exploring the 'CON' Folder Mystery in Windows by studying the recently published source code of DOS4 It's a well-known quirk that Windows doesn't allow folders named "CON" or "COM1"—a restriction that persists in 2024. While the reasons may be familiar to some, the release of MS-DOS 4.0's source code by Microsoft offers new insights. Join me as we dive into this code from over three decades ago for a fresh perspective and a retrospective peer review. #programming #clang #c

Fixing a bug in the #rust coreutils related to the returned value from the `kill` command & sending a pr on #github #programming #unix #linux

Tried all major BSDs for a week and reinstalled the #OpenBSD and will use that on my laptop for some time.

#Fedora #GNU / #Linux 40 is now officially available.

Fedora Magazine

OMG! We’re at forty! (Announcing the release of Fedora Linux 40) - Fedora Magazine

Announcing the release of Fedora Linux 40 with a description of it's contents, features, and improvements.

added a Zap icon & address the latest video on youtube... lets see if any body "understands" it. I would zap if I see one :D

Dear #Brazil, I live in #Iran and I know what a bad route you've stepping in. Please don't.

Connected my Wallet to @Alby , Any kind Zappers? :D And they provided me with one additional invite. DM me if you need it. FIFO.

Playing a ZX80 era text adventure called "Lighthouse of Doom"! Try it online here:

Lighthouse of Doom!

Unveiling the xz Utils Backdoor which deliberately opens our SSH connections for RCEs

Searching for some cute bugs to work on. Looking at the gossip, dogecoin, bitcoin, ruff, fish-shell.

Programming a game in Rust: River RIde Rust. A retro terminal game without using a game engine. Part one: creating the world, player & the moving river + collisions.

Cold day. Buy sats.

Lots of GNU/Linux & security websites are talking about CVE 2023-50547 which lets remote code execution on practically all of GNU/Linux distros, and whoever is using `shim`. In this video, first we will review the importance of the shim, then understand about the attack will step into the source code for a better understanding of how it happens and how RedHat mitigated it on the source level...