TIL: which in Shellscripts sollte vermieden werden. Es ist inkonsistent, unvollständig, nicht plattform-/shellübergreifend und noch nicht mal in POSIX. Stattdessen bietet sich command an, also z.B. command -v tmux.

https://unix.stackexchange.com/questions/85249/why-not-use-which-what-to-use-then/85250#85250

https://pubs.opengroup.org/onlinepubs/9699919799/utilities/command.html

Ever tried comparing MySQL's my.cnf from a Debian and a Gentoo machine with diff(1) without going crazy?

diff(1) is an awesome tool, you use it (or similar implementations like git diff, svn diff etc) every day when dealing with code. But configuration files aren't code. Indentation often does not matter (yeah, there is diff -w and yeah, people use YAML for configs), order of settings does not matter and comments are just beautiful noise.
How?

cfgdiff will try to parse your configuration files, fetching all the relevant keys and values from them and then pretty-printing them in the original format. These results are then diffed and the diff is shown to you.

• With --indicator (or -q or 'set indicator') nano will show a kind
of scrollbar on the righthand side of the screen to indicate where
in the buffer the viewport is located and how much it covers.
• With <Alt+Insert> any line can be "tagged" with an anchor, and
<Alt+PageUp> and <Alt+PageDown> will jump to the nearest anchor.
When using line numbers, an anchor is shown as "+" in the margin.
• The Execute Command prompt is now directly accessible from the
main menu (with ^T, replacing the Spell Checker). The Linter,
Formatter, Spell Checker, Full Justification, Suspension, and
Cut-Till-End functions are available in this menu too.
• On terminals that support at least 256 colors, nine new color
names are available: pink, purple, mauve, lagoon, mint, lime,
peach, orange, and latte. These do not have lighter versions.
• For the color names red, green, blue, yellow, cyan, magenta,
white, and black, the prefix 'light' gives a brighter color.
Prefix 'bright' is deprecated, as it means both bold AND light.
• All color names can be preceded with "bold," and/or "italic,"
(in that order) to get a bold and/or italic typeface.
• With --bookstyle (or -O or 'set bookstyle') nano considers any
line that begins with whitespace as the start of a paragraph.
• Refreshing the screen with ^L now works in every menu.
• In the main menu, ^L also centers the line with the cursor.
• Toggling the help lines with M-X now works in all menus except
in the help viewer and the linter.
• At a filename prompt, the first <Tab> lists the possibilities,
and these are listed near the bottom instead of near the top.
• Bindable function 'curpos' has been renamed to 'location'.
• Long option --tempfile has been renamed to --saveonexit.
• Short option -S is now a synonym of --softwrap.
• The New Buffer toggle (M-F) has become non-persistent. Options
--multibuffer and 'set multibuffer' still make it default to on.
• Backup files will retain their group ownership (when possible).
• Data is synced to disk before "... lines written" is shown.
• The raw escape sequences for F13 to F16 are no longer recognized.
• Distro-specific syntaxes, and syntaxes of less common languages,
have been moved down to subdirectory syntax/extra/. The affected
distros and others may wish to move wanted syntaxes one level up.
• Syntaxes for Markdown, Haskell, and Ada were added.

Rewritten in Rust: Modern Alternatives of Command-Line Tools
https://zaiste.net/posts/shell-commands-rust/

Here's another iteration on the Zero Terminal projects I've been working on for a few years. For those of you who haven't seen them, I've been trying to design the most usable all in one Pi Zero computer out there.

This version departs a little from the previous ones, as it is more focused on modularity, and forgoes a keyboard as standard, though it is possible to add one, as I'll show you in a bit. The goal here was to create something very versatile, allowing for all sorts of use cases to unlock the Zero's potential. Anyways, let's take a look at it.

I have been running a full IBM System/370 Mainframe on a $20 Raspberry Pi Zero for ~5 months. Thousands of lines of COBOL and HLASM running flawless. Tested an entire bank’s mainframe COBOL on it.

Since 2012, the Raspberry Pi nano computer has become an increasingly important part of the DIY and « maker » community. The increase in power of the Raspberry Pi over the years offers very interesting possibilities for radio amateurs. Indeed, it allows not to permanently monopolize a PC in the decoding of frames with software like WSJT-X, FLDIGI, etc…, without forgetting the possibility to control the Raspberry Pi remotely and thus to be able to work outside the radio shack as I can sometimes do on my couch. Moreover, this nano computer is now widely used in any Hotspot (DMR or D-STAR).

Researchers from Intel Labs have developed an open-source 3D printed smart robot that it is possible to build for less than $50.

Once combined with a modern smartphone, the additive bot is able to navigate autonomously, and its real-time sensing capabilities enable it to conduct recon tasks such as following people. The PLA-based Openbot has also been designed to be easy to build too, and its STL files have been made freely available online. By making their design public, the researchers hope that creators will tinker with and improve their robot to continue developing new applications for it in the future.

YARH.IO is a fully hackable and custamizable Raspberry Pi based handheld, running Raspberry Pi OS and supporting all other Operating Systems available for Raspberry Pi.

On this page, I want to share and document my experiences flying and using a kite antenna. There's nothing too special about a kite antenna. It's a fun, novel approach to the ham's age-old question about where to hang a wire antenna. When I lived inland, I could usually find a tall tree in which to hang an antenna. After relocating to the Galvston Island, tall trees are hard to come by. While the beach may lack trees, it usually does not lack wind.
A kite antenna setup is pretty straight forward and once you deploy it a couple times, it's downright simple. The key factor is having enough wind!

Neugierig wurde ich durch eine Veröffentlichung von W9SCH in der SPRAT Nr.69 unter 'A Four-Band UP & OUTER Antenna' und später durch einen Artikel im QRP-Report. Die Antenne ist als 'Upper & Outer' bekannt geworden. Sie besteht lediglich aus einem vertikale Strahler, dünner Draht, der locker um einen Glasfiebermast gewickelt wird und einem horizontalen 'elevated' Radial. Dieses Radial, als 'zweiter Strahler' bildet das einzige Gegengewicht, keine weitere Erdung. 'Wenn Strahler und Radial die gleiche Länge, λ/4 haben, funktioniert die Antenne schon recht brauchbar. Ein Tuner sollte aber eingeschleift werden, um das SWR zu optimieren.

Amateur radio (Ham radio) operators and engineers, have been experimenting with radio and antennas since Marconi. The use of a kite to support an antenna makes for great days operating and a wonderful HF antenna.

The linked pages that are listed below describe
various elements of a typical kite-antenna flying
field setup. One important lesson that we have
learned so far is that good kite-antenna contacts
result from flying the best possible antennas.
Another lesson learned is to keep the time that is
required to set up and put away as short and
convenient as possible - otherwise we will not do it!

Admittedly, we already have a page about our kite antenna exploits which makes for interesting reading. However those pages are about the practical use of these antennas. This talk given by Henryk M0HTB covers some of the background and the equipment considerations to supplement the practical exploits.

Wer seinen PC in eine PDP-11 von DEC mit der UNIX Time-Sharing System Seventh Edition (V7) als Betriebssystem verwandeln möchte, der kann den Sanos-Port von Bob Supnik’s PDP-11 simulator ausprobieren. Denn mit Diesem ist es möglich, UNIX so auszuführen, wie es Dennis Ritchie und Ken Thompson im Jahr 1979 getan haben.
Ein Sanos-Entwickler hat ein ISO-Image mit Sanos, dem PDP-11-Simulator und dem UNIX V7-Kit vom Computer History Simulation Project erstellt. Einfach eine CD-ROM in den PC einlegen und starten. Danach wird für alle nostalgischen UNIX-Geeks der PC zu einer PDP-11 mit dem UNIX V7.

Have you ever wanted a theme tune to play as you enter the room? Perhaps the imperial march, a pop hit or Super Mario’s Jolly Roger Bay. Well now you can thanks to the Human presence triggered music player – a small box which will wait for your arrival and serenade you when you step in trough the door and switch the lights on!

It’s designed for service rooms but has applications for all kinds of locations and establishments. The music is stored on an SD card, which can be selected by pressing the knob – which also controls the volume when turned. You might like to have some relaxing music to accompany a deep bath or something to get you pumped up for the home gym – whatever you choose it’s an unusual and ingenious device. Simply let it play out or turn off the lights to stop the music!

I finally got far enough in my build to show my progress on creating an AGC DSKY as per MIT's original drawings.

How to build a replica DSKY unit using an electroluminescent driver circuit and screen-printed conductive ink.

This is VT-100 and XTerm compatible video terminal implemented on the PIC32 microcontroller. It has a serial interface with TTL or RS-232 signal levels, input from a standard PS/2 keyboard, and output to a VGA monitor. There is also a USB interface that supports serial over USB and acts as a USB-to-serial converter.

Over the years I’ve collected a rather messy ~/.ssh/config which resulted in some undesired behavior as a result of me misunderstanding how the config file prioritizes its options.

Today I investigated that.
In short, this is what I found:

Priority goes from top to bottom
Defaults MUST come last
Host specificity is NOT a factor of priority
Host sections can be specified multiple times
Multiple hostnames (and aliases) may be specified per section
Host sections apply to the name you use (not what it resolves to)