Since OpenBSD 6.8, boot process does not work on my ASRock J5005-ITX board. The root cause is the kernel size. In this blog, I present you 2 possible solutions

On one of my OpenBSD machine, I had, after several months of usage, a full /tmp filesystem. Despite by checking files, none were big enough to take full space of /tmp. Why [df](https://man.opensd.org/df) shows a full filesystem ? and why no big files identified by [ls](https://man.openbsd.org/ls), neither by [du](https://man.openbsd.org/du) ?

For the release of OpenBSD 6.8 I've slightly adapted my systupgrade utility.

[fzf](https://github.com/junegunn/fzf) is an addicting tool for what concerns search. The overall process is very simple, despite very quick. Moreover the tool is well presented. This post will describe how to integrate fzf with OpenBSD packages.

I would like to re-run DragonflyBSD on my laptop where OpenBSD is running. So I'll explain how I've setup a multi-boot system.

After having listen to the presentation of Hannes Mühleisen given on February 2nd at [Fosdem](http://fosdem.org). I've decided to give a try to type of DB.

Last week my NAS stopped working. The mother board has not resist to an unplanned power outage. So, I bought a new board [J5005](https://www.asrock.com/MB/Intel/J5005-ITX/index.asp). After having placed the new board in the case, I was surprised to see that the board does not see the boot sector. Looking in the documentation of the board, we can ONLY use EUFI. Legacy boot is not supported!!!. Here bellow I will explain how to migrate my disk to UEFI.

Since version 6.6 of OpenBSD we can upgrade a machine via a simple commmand: [sysupgrade](http://man.openbsd.org/sysupgrade). Unfortunately this tool as some side effects annoying for me: install all sets and reboot immediately without asking it. In this blog, I present modifications I did in order to solve those problems.

Today it's exactly 100 days that my website is running on top of Fapws4 without any troubles.

After my blog on [xenodm](/post/post_20190626), I've received several interesting remarks. So, this blog is to integrate some of those remarks (not all) and to include a nice looking dynamic picture.