David's Computer Blog

So in a previous article I mentioned installing OpenBSD into Hyper-V. I had encountered a problem with disk space while trying to install packages. A partition the size of 20GB and 30GB was too small for the auto-partition feature of the OpenBSD installer. Gnome and Firefox took too much space for the auto-partition feature. In fixing the space issue, I thought about possibly redoing the OpenBSD installation and use manual partitioning in order to have more space. It worked. The auto-installer creates 9 partitions for OpenBSD. There is the root partition along with tmp, var, usr, usr/X11R6, usr/local, usr/src, usr/obj, and /home. So I deleted all these non-root partitions. I then had to delete the SWAP partition as it was preventing the root partition from being resized. I resized partition A to 95% of the 30GB disk and created a new SWAP partition that used the remaining 5% of the drive.  This arrangement probably isn't ideal for a production or a long-term setup, but it works we

So I wanted to try out the  new FreeBSD 13.1. Rather than installing it onto a physical computer, I decided to try creating a virtual machine in Hyper-V.  Hyper-V is a Microsoft product, and it was all I am able to use in the work environment that I am in. In a previous experiment I was able to create a Linux Mint virtual machine in Hyper-V with no problems.  However, I did encounter problems setting up FreeBSD 13.1 in Hyper-V. I eventually gave-up on getting FreeBSD 13.1 to work in Hyper-V. I tried a few different ideas, but I was never able to get X-Windows to recognize the keyboard. The keyboard worked fine to type in startx, but once X started, the keyboard wouldn't work.  It was a little disappointing not being able to get FreeBSD working in Hyper-V, but alas, some times such things happen. To stay within the BSD family, I decided to try out OpenBSD. I had very little knowledge of OpenBSD, but I decided to get it a try in Hyper-V. Unlike FreeBSD 13.1, X Windows inside OpenBSD