And here we are. #NetBSD is simply amazing.

#unix #runbsd #retrocomputing #486

After making myself a new, smaller kernel and install floppies - only needed two, as opposed to six for the stock kernel..

Attempting to install #NetBSD on this 486.. gonna need some more work before that works I'm afraid.

(Read the alt text for more info)
#retrocomputing #moreram

@tom@epsom.social Mind sharing the tls config? Key lengths, curves, ciphers and protocols?

@tom@epsom.social fully expect I have to build a bunch of stuff myself. Including netbsd. But I expect snac to build nicely and not require any special gymnastics. :)

I'm thinking of running it on a 120/133MHz AMD 5x86 or something like that. It should (at least) have 64MB RAM, possibly 128 if I can get it to cache the whole range.

A bigger challenge will be the Nintendo WII - it has, I believe, 24MB or something like that? But at least the CPU should be vastly superior to any 486..

How much memory does Apache use then? It sounds like unnecessary bloat even with modules disabled. But maybe that's just me still clinging to 20+ year old impressions of Apache being bloated by definition.

Do you do TLS in Apache too? On a K6-II?

@gyptazy@gyptazy.com Still runs circles around a 1998 chip though. But it shows what good code can get out of questionable hardware.

Cc @grunfink@comam.es @gumnos@bsd.cafe @rubenerd@bsd.network

Happy to please :D Now would it be considered cheating if I ran snac on a 486 but with TLS handled elsewhere (simply for lack of CPU instructions to do EC TLS)? :)

CC: @gumnos@bsd.cafe @rubenerd@bsd.network @grunfink@comam.es

And finally, the screenfetch output. Full text in description.

And here's the innards. Curious eyes might spot some old and dear sound cards, other than that the highlight is of course the mainboard and the CPU board, which is replaceable. And the CPUs, obviously.

This is the "aquarium case", as it has become known around the office. It has a nearly-invisible batman-symbol embossed on the front, and a similar cutout in the back. Beats me why, but it's kinda cool.

Since nobody asked, here are a couple of pictures of the rig. It's not posing for the picture (I didn't tell it what was going on), so it's as messy as usual.

I'll post each picture as a reply to this post, as snac doesn't like multiple attachments..

Enjoy. And wish the poor box luck serving this.

#servertorture #retrocomputing

Yeah I agree. It's absolutely awesome - also that #NetBSD (and all the other #BSD variants) are first-class citizens. Thank you, @grunfink@comam.es!

CC: @rubenerd@bsd.network

I'm on NetBSD and at least pkgin knows nothing about OpenBSD's httpd (I think)..
Do you have any idea of the memory footprint of h2o when doing TLS and proxying?

Any idea of its memory footprint in such a case? When doing TLS?

Sadly not on NetBSD though :)

Damn I like the whole css-or-bust approach to styling that #snac has. I mean I know many (most?) others do a bit of the same but this is just delightful.

So..TLS aside, what is the most lightweight reverse proxy I can use instead of nginx in front of this thing? You know, in case I would like to move the instance from this beefy PPro to, say, a #486 or a #Nintendo Wii running #NetBSD? :)

#retrocomputing #BSD #stupididea

TIL today: secp* curves are orders of magnitude slower than X25519 and prime256v1. At least on a Pentium Pro/Pentium II-class CPU.
#retrocomputing #forgetwhatyouknow

Posting and boosting this certainly put the box under some duress.. Changed ssl_ecdh_curve from secp521r1:secp384r1; to X25519:prime256v1; now; let's see if that helps.

After a fair bit of fiddling, this #snac instance is now .. operational, I think? And this is officially my first post here.

See also my main fediverse presence: @ltning@anduin.net

About this instance, at the time of writing:
- OS: #NetBSD 10
- Reverse proxy: nginx
- CPU: Dual Pentium Pro Overdrive, 333MHz
- RAM: 512MB EDO
- NIC: 3Com 100Mbit PCI NIC
- Storage: SATA 1.0 (CF and SSD)

#retrocomputing #butwhy