My home server for a few years has been a Gigabyte BRIX 1900. Aside from powering this site, my email, project mailing lists and source code repositories, I use use it to host some VM’s as XEN DOMU HVM guests so I can ensure my code works on many operating systems. However, the VM hosting brought my server to it’s knees.
I’ve recently purchased an AMD 2600x which I’ve fitted out with 32GB RAM.
NetBSD PR lib/23910 was filed over 16 years ago. It describes how NetBSD curses fails to work with Vifm, a Vim interface for a curses GUI file manager. It’s quite a nice idea after playing around with it some as Vim is my favourite text editor.
Since I was the main protagonist in bringing terminfo to NetBSD, I had a reasonable grasp on how our curses worked and I had looked at this bug before, but left scratching my head over it.
POSIX mandates implementations must support upto a short but may exceed it. When NetBSD terminfo was implemented, no terminfo description used over a short, but because ncurses has supported ints for some time, some now do.
Infact, such a terminfo description was imported where colour pairs for screen-256color went up to 65536 which exposed a bug in the existing implementation where it was set to zero. Because the number might mean something more than a range, we need to be able to store it accurately.
So I’ve used Grav since 2017 to power my project and blog pages. It’s a flat-file Content Management System. It’s really easy to use and takes away a lot of the pain of setup. By easy to use I mean you don’t ever have to use the command line after the initial setup and the admin pages and general look and feel are really nice and clean.
Internally, Grav uses markdown files to store the user pages using frontmatter to store meta-data such as tags, publication date, etc.
DHCP clients by default send a fair chunk of data which can identify you to the local DHCP server. In return they provide you with a stable IP address and configuration parameters.
At a bare minimum, the hardware address of the interface is sent- this is required to work.
So, how to solve this dilema of wanting total anonymity? The answer is to randomise the hardware address. This will happen when the carrier is down OR dhcpcd starts with the interface down.
Roy's Blog