sjmulder

I agree that OSM is amazing, but

> The cool thing isn't so much os9map (yes it's cool)

OS9Map is absolutely the cool thing here, especially if you consider the platform lacks basics such as TLS and JSON parsing.

Doesn't the loaded code have to be patched for relocations?

Even DOS has environment inheritance!

Web/SSH/mail server using the built in httpd, sshd and smtpd. Very happy with it.

And on my laptop, occasionally, to experience it in person.

I dual boot OpenBSD on it, and it's been doing fine. The out of the box experience is pretty bare although the default window manager cwm is surprisingly nice once you get to know it. Note that apmd, the power management daemon used to manage CPU speed and low-battery suspend, is not enabled by default. The high-DPI screen required some adjustments in Xresources (I haven't dared try a multi-monitor, mixed DPI setup).

NetBSD seemed okay to but I've only used it a little bit. It actually set up X pretty well for the screen using some built in script with heuristics to determine font size from the screen metrics.

Turns out the rule works perfectly fine, I just forgot to enable IPv4 forwarding in sysctl (in addition to IPv6, which I did enable).

A 'charade'? Just having some fun running NetBSD on unusual hardware and learning something along the way. There's no cheating some imaginary game you seem to think I'm participating in.

It would be a fun project to do a homebrew HTTP server (and I wouldn't be surprised if it had been done already) but in this case I actually mean to replace my Pi 'home server' with this Wii, and for that I want SSH, git, web, mail, and all that, so practically, NetBSD was a good option.

There's also the fact that there's a modern, up-to-date Unix distribution for this in the first place, how cool is that.

I meant to replace it with IP forwarding from a secondary IPv4 address on another host running OpenBSD, but I haven't been able to get that to work yet. Perhaps any OpenBSD/pf folk here have an idea? This is my config (where in the real file the variables are literals):

  pass in on egress inet to $secondary_ipv4 \
    af-to inet6 from $ipv6 to 2a02:a45f:8eaa::2/128

All I get is timeouts and traceroutes with infinite hops. First I tried rdr-to, but that complains of the address family mismatch.

How is that? These are vendor packages