smcroute.conf example

- 3 mins read
# # smcroute.conf example # # The configuration file supports joining multicast groups, to use # Layer-2 signaling so that switches and routers open up multicast # traffic to your interfaces. Leave is not supported, remove the # mgroup and SIGHUP your daemon, or send a specific leave command. # # NOTE: Use of the mgroup command should be avoided if possible. # Instead configure "router ports" or similar on the switches # or bridges on your LAN.

N E M E S I S

- 3 mins read
Nemesis is a command-line network packet crafting and injection utility for UNIX-like and Windows systems. Well suited for testing Network Intrusion Detection Systems, firewalls, IP stacks and a variety of other tasks. As a command-line driven utility, it is perfect for automation and scripting. Nemesis can natively craft and inject ARP, DNS, ETHERNET, ICMP, IGMP, IP, OSPF, RIP, TCP and UDP packets. Using the IP and the Ethernet injection modes, almost any custom packet can be crafted and injected.

Dependency handling in Finit

- 2 mins read
finit logo

This is a blog post about Finit. Each post is concluded with a video summarizing the topic. The impatient reader can scroll down to the video.

Most non-trivial systems require dependency tracking between services. Not only does it help ensure correct operation, it is also an enabler for starting services in parallel. Less known, but just as important, is handling dependencies at system reconfiguration.

Advanced watchdog daemon for Linux

- 1 min read
watchdogd(8) is an advanced system and process supervisor primarily intended for embedded Linux and server systems. It supports “kicking” multiple watchdog timer (WDT) devices and can also monitor critical system resources, supervise the heartbeat of processes1 and record process deadline transgressions. Read more about Built-in Monitors in the extended documentation. The configuration determines how the daemon acts on monitored resources and supervised processes. See watchdogd.conf(5) for how to set up watermarks and trigger external scripts to suit your particular setup.

It's Here! ♥

- 1 min read
finit logo

Finit v4 was finally released the other day! \o/

It represents the culmination of many years of hard work and careful thought put in by many people. There’s so much to tell, hardly know where to begin … the plan anyway is to use this blog for a series of posts detailing different aspects and important features.

The impatient reader can either scroll down to the video below, or move on to the project home page: https://troglobit.com/finit.html

Alpine Linux with Finit

- 3 mins read

Alpine Linux is an amazing little operating system. It’s small, boots quick, and easy to use. The size alone makes it very attractive to container builders.

Alpine Linux started with Finit

Alpine Linux started with Finit

This blog post details how to set Alpine up with the Finit init system, replacing the default OpenRC.

Buildroot Development Checklist

- 2 mins read

Because I always forget, here’s a reminder to myself on how to use git format-patch and git send-email from the command line.

The following process applies to many other mailing-list based projects as well, with local differences in helper scripts.

Emacs: GMail and Lore Mailing Lists

- 4 mins read
With lots of help from the tireless Tobias Waldekranz, I think I’ve finally found the perfect “magit like” email setup. With Emacs, of course. This is the story of how I did it. First install notmuch, mbsync (from the isync package), and afew: sudo apt install notmuch isync afew Do initial setup of notmuch for your user. I’ve opted to store my mail in ~/mail, this is used throughout the text below, ymmv.

Backtrace in C

- 1 min read

Reminder to self: remember CFLAGS=-g -Og -rdynamic to allow backtrace_symbols() to actually pretty print function names in stack traces.

Weird Screen Artifacts on X200

- 1 min read
I blogged earlier about the awesome little ThinkPad X200 I found and its blinking WiFi LED. Briefly I mentioned an odd issue with X/Wayland on LMDE 4. This turned out to be a HW bug that can only be worked around by disabling hardware acceleration for virtualization: https://forums.lenovo.com/t5/Windows-8-1-8-7-Vista-and-XP-Discussions/Bizarre-screen-artifacts-on-R400-Integrated-Graphics-running-Win-7-RTM/m-p/153980?page=1#199768 The post says it should be sufficient to “Disable Virtualization Technology for Directed-IO (VT-d)”, but that didn’t work for me, and I wanted to keep the 8 GiB of RAM I managed to fit into it.