OpenBSD's model and philosophy match both my requirements and expectations
perfectly, Theo. I'm just not too fond of stuff unexpectedly breaking -
admittedly because I missed out on this specific thread -, but for which
Stuart's tip is an excellent mitigation indeed.
Kind regards,
Dirk
--
A manual xorg config with the vesa driver brought X back to life, but not
until I set machdep.allowaperture=2 in /etc/sysctl.conf . Thanks for your
reply, Matthieu. I do hope 6.7 doesn't come with similar surprises, though
--
Sent from:
Touché.
I should probably rephrase this as "operating a slightly less insecure
environment as compared to running vanilla Windows 10 on contemporary COTS
hardware". And finding it really hard to throw away perfectly good hardware
that suited the intended purposes really well until Matthieu
Hi Matthieu,
It would seem I'm a bit (too) late to this party. In short: I'm running a
high security environment leveraging the combined power of contemporary
OpenBSD and ancient i386 hardware stuffed with RAM, but untouched by all
kinds of modern BIOS/EFI/processor "management" technology. My
