I noticed the weekdays was missing from
xclock‘s digital display when run in FreeBSD
base/head aka 11.0-ALPHA6. FreeBSD
stable/10 doesn’t have this problem. Continue reading Weekdays missing from
xclock‘s digital display
… FreeBSD gives you the ability to make a choice how you want your boot prompt, splash screen, X login, desktop environment and applications. This, in my opinion, makes it very professional compared to systems that force a given set of settings upon the user, and there is no way to make a different choice.
Stated by “Polytropon”, 27 Feb 2015.
Configuring X11 is more or less a dark art, and you must almost be a wizard of the Slytherine House to get modern X.org 1.14.7 working on a FreeBSD guest in VirtualBox.
Nonetheless, through lots of experimentation this evening, have I finally arrived at this configuration file:
Identifier "Keyboard Defaults"
Option "XkbLayout" "no"
Identifier "Mouse Defaults"
Option "CorePointer" "on"
Somehow, you need both the
InputClass and the
InputDevice sections to get the mouse working as it did in previous versions of X.org. The option
CorePointer is also key to the success.
Not only have I achieved Norwegian keyboard layout, the mouse sends its events to the X Server, and the mouse cursor is able to leave the FreeBSD guest whenever I want.
Maybe I’m the next Voldemort afterall.
I have a bunch of FreeBSD VMs running in VirtualBox. They all share a number of virtual harddrives, and among them are a virtual harddrive with the common contents of
My ports configuration of
emulators/virtualbox-ose-additions have the
X11 options set. This is useless on some of my simpler VMs, as those VMs have no need for any X11 ports, but they could sure benefit from having the VirtualBox additions installed. These simpler VMs are usually used only to test ZFS in FreeBSD in various configurations.
I could juggle the settings for
emulators/virtualbox-ose-additions for each time I’m updating the VirtualBox additions port on my VMs, but I decided to create a local slave port disabling the
X11 options. Maybe this port, with the necessary tweaking, could sit among its siblings in the official
OPTIONS_EXCLUDE= OPENGL X11
COMMENT= VirtualBox additions for FreeBSD guests without OPENGL and X11
For now you must copy the
/var/db/ports/local_virtualbox-ose-additions-additions-nox11/options file to
/var/db/ports/emulators_virtualbox-ose-additions-additions-nox11/options, or else
dialog4ports(1) will keep nagging you until kingdom come.
I guess this problem stems from early processing of
bsd.port.mk as done by the master
Makefile at a time when the
CATEGORIES variable was set to
I’m probably not paying enough attention to new developments in FreeBSD after all. After updating the installed ports in my VMs running
base/stable/10, X11 stopped working. It turns out the new version of X.org requires KMS and what not in the kernel. This doesn’t fare well with VMs running inside VirtualBox.
The solution? Place
/etc/make.conf file and recompile everything, or at least recompile everything belonging to the X.org subsystem. I opted for the former, spending roughly five hours recompiling 443 ports.
The VMs running
base/stable/9 hasn’t been affected yet, but I figured it’s best to play safe and I amended the aforementioned line in the
/etc/make.conf file on those VMs.