I'm sharing here some practices I'm following and some small tips/tools which facilitate my usage of OpenBSD in my day to day. Some a really specific to my usage, others could be re-used.

It's funny to see what does an idle machine. In this blog I compare which websites contacts my OpenBSD laptop with a Windows 10 laptop. I do know very few things of W10, so you can consider it as stock installation. You can see it as a newbie setup.

You have just upgraded your OpenBSD machine to the brand new release, but some of your applications are no more working because they do not have the required python package. This is a very common problem between python package you have installed via pkg_add and the one you have installed via "pip install". The problem is that both are installed on your machine in /usr/local/lib/python3.8/site-packages. I propose you a methodology to identify which one were installed with which tool

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.