Show HN: I486SX_soft_FPU – Software FPU Emulator for NetBSD 10 on 486SX
https://github.com/mezantrop/i486SX_soft_FPU
Discussions: https://discu.eu/q/https://github.com/mezantrop/i486SX_soft_FPU
Show HN: I486SX_soft_FPU – Software FPU Emulator for NetBSD 10 on 486SX
Link: https://github.com/mezantrop/i486SX_soft_FPU
Discussion: https://news.ycombinator.com/item?id=43815116
Ah, the brave souls resurrecting FPU emulation for the fossilized #i486SX CPU on #NetBSD 10 - because who doesn't want to relive the adrenaline rush of 90s computing? 
In this GitHub saga, watch as developers valiantly attempt to make turtles fly, proving once again that #nostalgia is the true enemy of progress. 
https://github.com/mezantrop/i486SX_soft_FPU #FPUemulation #90sComputing #HackerNews #ngated
BSDCan is in Ottawa, with tutorials June 11-12, 2025, talks & BOFs June 13-14, 2025
Registration is open - https://www.bsdcan.org/2025/registration.html
Also see https://blog.bsdcan.org/2025/03/18/bsdcan-2025-talks-tutorials-and-registration/ for descriptions and tips, contributions: https://indico.bsdcan.org/event/5/contributions/
EuroBSDCon 2025, Zagreb, September 2025 -
The Call for Talk and Presentation proposals for EuroBSDCon 2025 is open.
Submit yours at https://events.eurobsdcon.org/2025/
Please also visit the main website https://2025.eurobsdcon.org/ for information about the conference.
See you in Zagreb!
#eurobsdcon #bsd #conference #freebsd #openbsd #netbsd #unix #development #devops #freesoftware #libresoftware @eurobsdcon
BSDCan is in Ottawa, with tutorials June 11-12, 2025, talks & BOFs June 13-14, 2025
Registration is open - https://www.bsdcan.org/2025/registration.html
Also see https://blog.bsdcan.org/2025/03/18/bsdcan-2025-talks-tutorials-and-registration/ for descriptions and tips
@BoxyBSD was always for BSD based systems only. I focussed to push the whole BSD community and to encourage people to try BSD based systems (such like #FreeBSD. #NetBSD, #OpenBSD, etc.) but I'm not sure if it might provide more value to the whole #opensource community by also supporting #Linux systems (such like #Debian, #Ubuntu, #RockyLinux, #SuSe and more).
I'm not sure if the #BoxyBSD project still provides a value for the community right, now.
What do you think?
As it approaches, the excitement for the upcoming #BSDCan keeps growing. It'll be my first time in Canada, and therefore my first time at BSDCan, and it will be a great opportunity to meet people I couldn't meet at #EuroBSDCon in Dublin. In the meantime, the next EuroBSDCon is also getting closer. All in all, when I look at the coming months, I feel an overwhelming sense of positivity and enthusiasm!
I took the opportunity of the #GoToSocial upgrade to 0.19.0 to also start polling the #prometheus endpoint using the #VictoriaMetrics vmagent. This lead to identifying a bug (I think) so the gentle devs now have another PR to deal with 
Regarding OSes, this is #OpenBSD polling and storing metrics from #NetBSD and rendering them using #OmniOS and #pkgsrc.
Who said I was a sane person 
25 years ago today I registered my domain:
$ whois netmeister.org | grep Creation
Creation Date: 2000-04-24T02:15:22Z
One of my best decisions tech-wise was to run my own stack on my own domain (HTTP, SMTP, DNS, and whatever else). It forces me to keep up to date with developing standards and protocols, lets me troubleshoot and debug on a level otherwise impossible and is well worth the occasional "ugh, wtf now?" headaches you inevitably run into.
(And of course it runs #NetBSD. :-)
I try to use and love #NetBSD.. however every time i get pkgin working for a current login, the next time i reboot or log back in with a new session, none of it works. Do I need to export all the variables set when I setup pkgin?
Maybe i don't read enough of the documentation to lock it in. I want to love it and give it a serious chance in my environment. But getting packages to get setup is really a big hurdle for me. 
Testing #nginx on #NetBSD on my Raspberry Pi Zero W, connected via wifi:
http:
wrk -t4 -c50 -d10s http://192.168.111.143
Running 10s test @ http://192.168.111.143
4 threads and 50 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 70.52ms 18.01ms 133.58ms 73.66%
Req/Sec 170.04 38.91 280.00 65.00%
6816 requests in 10.07s, 5.54MB read
Requests/sec: 677.05
Transfer/sec: 563.99KB
Not huge, but stil 677 requests per second.
In https:
wrk -t4 -c50 -d10s https://192.168.111.143
Running 10s test @ https://192.168.111.143
4 threads and 50 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 764.43ms 397.17ms 1.99s 75.79%
Req/Sec 14.31 10.93 69.00 78.64%
418 requests in 10.07s, 17.66MB read
Socket errors: connect 0, read 0, write 0, timeout 38
Requests/sec: 41.51
Transfer/sec: 1.75MB
Much worse - but I expected it. Still, 41 requests per second in https is more than I expected.
If this message made it to you, it means the migration from #GoToSocial 0.18.3 to 0.19.0 went ok. The whole upgrade process, database migration stuff included, took only a couple of minutes; the #SQlite database is 1GB large. Of course, it runs on #NetBSD; using the official build.
I'm going to compile the NetBSD kernel directly on the Raspberry Pi Zero W, which is running NetBSD.
Let's wait and see 
