Hi, I am an embedded software developer, tinkerer, and a generalist.
“A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly.
Specialization is for insects”— Robert A. Heinlein.
The default structure of a fresh NixOS installation makes a lot of sense, two files, which are intended to be used as the bases for future changes and represent a single machine with the bare minimum, upon which this first installation is being done. For the sake of consistent language I will call them two high level modules. The problem with "all in one configuration files" The initial installation creates two high level modules, configuration.nix and hardware-configuration.nix but what happens when we want to add zfs configuration or setup home-manger, or maybe declare neovim and emacs. The cohesion of this high level modules gets fuzzier by every such addition. Unrelated configurations get coupled together, Understating where something starts and ends and the ability to change it becomes a nightmare. ...
All posts in this series: Intro to Yocto, part 1 - Rolling your own Linux distro with yocto Intro to Yocto, part 2 - Hands-On Introduction to BitBake Intro to Yocto, part 3 - Building a Poky (Yocto Project) Image for QEMU (current) Intro to Yocto, part 4 - Yocto for raspberry pi4, build, boot, and cross compile Preface The goal of this post is to customize the Yocto reference distribution, Poky to create a bootable image for the Raspberry Pi4. This involves aspects of what is often termed as “board bring-up”, specifically adapting the build system for new hardware. And will also cover cross-compilation. ...
All posts in this series: Intro to Yocto, part 1 - Rolling your own Linux distro with yocto Intro to Yocto, part 2 - Hands-On Introduction to BitBake (current) Intro to Yocto, part 3 - Building a Poky (Yocto Project) Image for QEMU Intro to Yocto, part 4 - Yocto for raspberry pi4, build, boot, and cross compile After looking at why you should build your own distribution in Rolling you own Linux distro with Yocto, And then looking on how bitbake works, it is time to dip our toes in the water and create first real image out of poky reference repository and actually run it using a virtual machine. ...
All posts in this series: Intro to Yocto, part 1 - Rolling your own Linux distro with yocto (current) Intro to Yocto, part 2 - Hands-On Introduction to BitBake Intro to Yocto, part 3 - Building a Poky (Yocto Project) Image for QEMU Intro to Yocto, part 4 - Yocto for raspberry pi4, build, boot, and cross compile Preface This post is based on a tutorial by Harald Achitz. As I was following it I was adding notes to it for context, and clarity. Filling in the blanks I came across and refactoring the structure for readability. ...
When setting up a full NixOS system—or even just a standalone Home Manager module—secrets are often a core part of the configuration. With nix being declarative, it makes a lot of sense to integrate them into the nix configurations, but this needs to be done in a secure manner, so even if your configurations are put on public display your secrets will stay safe(case in point my repository that are a reference for this post). ...
All posts in this series: (current) Intro to Yocto, part 1 - Rolling your own Linux distro with yocto Intro to Yocto, part 2 - Hands-On Introduction to BitBake Intro to Yocto, part 3 - Building a Poky (Yocto Project) Image for QEMU Intro to Yocto, part 4 - Yocto for raspberry pi4, build, boot, and cross compile This post is the first in a series that will cover embedded development from the perspective of OS development, starting with the need of such solution, the moving parts, the basic configuration that can be used on a raspberry pi and anything else that might be relevant. ...
About The aim of this tutorial is to go over the creation of the compilation database(compile_commands.json) for cland lsp using cmake, and then more importantly expand on its limitations when it comes to cross compilation. Resources You can get all the source described bellow at the following repository. Creating the source code Understanding the include search order by clang++/g++ standard headers such as iostream or pthread(posix) are located by the compiler at standard paths, other headers(foo.h) need to be specified using the directory they are located in using -I directive. ...
There are many videos and posts dealing with tmux and how to use it, most of them only deal with its basic use, meaning explaining tabs, panes, session and at best the use of tmux as a daemon. I am on the other hand want to focus on the impact that tmux has had on my workflow and the ways I use it to reduce context switching friction. By understanding the moving parts of your tool and your interface with it you can carve a friction free workflow that suits you specifically, concentrating on the task at hand instead of wasting time and energy to bring the things you need together and then scrambling form one context to the next, just to repeat it again and again with each system restart. ...