I wonder about the level of VAX support. Do they just have old code lying in the repository, do they build it, or do the devs actually have a working VAX machine and they test new builds?
Not a dev, but as i understand it as a Vaxstation 4000 owner who boots up from time to time to enjoy the beeps:
a) build.sh allows cross compilation, which helps with build validation
(although openbsd built native until they dropped vax ~3y ago)
b) there are a few dedicated devs on vax. these pretty much do the work as a hobby,
and things are best effort, but generally in sync with the rest of the tree. most
of these own a vax or three, but you can also run on SimH and probably other
vax emulators.
c) really, the system source is modular enough that adjusting device drivers for well
documented hardware which has existed for years, and tweaking a few
already-implemented since the 80s macro primitives is most of what is needed to
keep things running -most of the adjustments to the system itself happen higher
up the stack (e.g in the generic c portion of the kernel, or in the c library).
Granted, this does mean knowing the ISA and HW in and out, and having skills to
debug/reason about low-level instruction/hardware sorts of issues, but, hey,
that's who codes open source os'es anyway.. Besides, if you are a true VAX BSD UNIX hacker,
you've been tweaking your kernel sources since you manually toggled in the 3BSD bootstrap
in 1979 :b
I wonder about the level of VAX support. Do they just have old code lying in the repository, do they build it, or do the devs actually have a working VAX machine and they test new builds?