Just like the transformer paper Attention Is All You Need proved, working with AI agents has taught me: Files is all you need. Simplicity is your greatest ally. The ecosystem offers many sophisticated tools—MCP (Model Context Protocol) servers for structured tool access, Skills frameworks for capability registration, Memory systems for persistent context. While powerful, these add layers of abstraction and ceremony that can obscure what the agent actually needs to do. After experimenting with these approaches, I’ve found that a simpler pattern often works better: plain files, executable scripts, and clear references. This keeps token usage low, workflows predictable, and debugging straightforward. You get the benefits of structure without the overhead of complex registration systems or protocol layers.

TL;DR To boot and get a serial console add "console=ttyS0" to your kernel boot arguments via boot.kernelParams = [ "console=ttyS0" ];. The MinnowBoard is an x86 based developer board, similar to the Raspberry Pi or the BeagleBone Black. It comes in multiple versions like the MinnowBoard MAX and the newer MinnowBoard Turbot. They are both compatible to each other and these instructions work for both of them. Check out the Getting Started Guide on minnowboard.org to get started with your board.

When running docker for some time on your local machine it accumulates quite some data and from time to time you might want to clean them up. This is a collection of docker commands I found most useful in this context: Clean Volumes Cleans all volumes that are not used by any container. docker volume rm $(docker volume ls -qf dangling=true) Clean Images Cleans all images that are not used by any running container. This includes old versions of images.

Start plain In this post we will have a look at a simple TCP example in Go and how it can be changed to use secure TLS instead. Plain TCP server First let’s have a look at a simple TCP server. It listens on port 8088 and prints everything it receives to stdout. package main import ( "fmt" "io" "log" "net" "os" ) func main() { l, err := net.Listen("tcp", ":8088") if err != nil { log.Fatal(err) } defer l.Close() for { conn, err := l.Accept() if err != nil { log.Fatal(err) } go func(c net.Conn) { io.Copy(os.Stdout, c) fmt.Println() c.Close() }(conn) } } Plain TCP client Next we have a client that will send a message to the above server.

Most of the time recipes in Yocto and OpenEmbedded are pretty static in the sense that when you build your image you either you get what is described in the recipe. It is possible to build the package different based on the MACHINE for example but otherwise packages are fixed in what they provide. What if you want a package that can be built in different ways? For example Apache Thrift can build additional libraries if libevent or zlib is available at build-time.

I recently updated the Unison version in my [PPA](https://launchpad.net/~pascal-bach/+archive/unison](https://launchpad.net/~pascal-bach/+archive/unison). The current version is 2.40.102. This version is taken from the Debian git sources and build without modifications. The package is available for the following Ubuntu versions: 10.04 LTS (lucid) 12.04 LTS (precise) 12.10 (quantal) 13.04 (raring) If you encounter any problems please let me know.

Update 2: With newer version it is much easier to just follow the instructions here. On windows I mostly use Putty as my SSH client. But in some cases for example when I use unison or rsync I use the ssh client from cygwin. Following good practice I use public key authentication and Putty’s Pageant to manage my password protected keys. This works great with Putty and Plink. I thought this would be great if I could use the same agent for cygwin too. As often the solution already existed in the form of ssh-pageant.

Today I had the problem that my Nokia N900 Mail for Exchange could not sync with my Zentyal server via Active Sync. After some research I found a solution in the Zarafa forum. It consists of activating LOOSE_PROVISIONING in your z-push config.php. If you are using Zentyal 2.0 this is located at /usr/share/z-push/config.php and you have to change the line: define('LOOSE_PROVISIONING', false); to define('LOOSE_PROVISIONING', true); now it should work. Unfortunately I’m not sure if this gets overwritten during the next update!

Sometimes there is a bug in a package from Ubuntu that is not yet fixed, or you just want to modify something in the source of a software. Here is an easy way to build your own package from the Ubuntu sources. First you need to install the required tools for building software from source sudo apt-get install build-essential Let’s assume you want to build a package called foo and apply a patch bar.patch to it.

I just found a nice method to invoke screen automatically if after login via SSH. So you don’t have to manually start it first. Put the following at the end of your ~/.bashrc # Auto-screen invocation. see: http://taint.org/wk/RemoteLoginAutoScreen # if we're coming from a remote SSH connection, in an interactive session # then automatically put us into a screen(1) session. Only try once # -- if $STARTED_SCREEN is set, don't try it again, to avoid looping # if screen fails for some reason. if [ "$PS1" != "" -a "${STARTED_SCREEN:-x}" = x -a "${SSH_TTY:-x}" != x ] then STARTED_SCREEN=1 ; export STARTED_SCREEN [ -d $HOME/lib/screen-logs ] || mkdir -p $HOME/lib/screen-logs sleep 1 screen -RR && exit 0 # normally, execution of this rc script ends here... echo "Screen failed! continuing with normal bash startup" fi # [end of auto-screen snippet] If you want more details and some additional tricks just go to http://taint.org/wk/RemoteLoginAutoScreen.