5 ms·

Can you share how it's doing cpu/memory wise and his it's holding up in general under what I assume I heavy load from HN?

smoppi 5y ago
Video: https://www.youtube.com/watch?v=erM0K0oXk4M https://www.youtube.com/watch?v=erM0K0oXk4M In the end I minimized the HTTPSERV.APP window so that scrolling down the text would not consume too much CPU time.
smoppi 5y ago
Right now I cannot even access it locally from my lan, but it does answer to some of my pings. The HDD led is also blinking, which means that it is in fact answering to some HTTP requests. The TCP/IP stack is compiled for 64 simultaneous sockets.
- ForOldHack 5y ago
  Please paste an image up on Archive.org, so at least we can stare at the 'pre-meltdown' server. P.s. I used a 486 as a router for years, and even upgraded it when I found a Pentium Overdrive... which of course was vulnerable to the F00F bug...
  - busymom0 5y ago
    https://web.archive.org/web/20220116193852/http://486servu.dy.fi/ https://web.archive.org/web/20220116193852/http://486servu.d...
- CodeWriter23 5y ago
  Next iteration: Caching HTTP server
- tentacleuno 5y ago
  I can't access it either. It looks like it's just timing out. We did it, guys! :D
loloquwowndueo 5y ago
Not holding up great it seems :)
- velmu 5y ago
  Loaded now. This is what's there: "Tämä palvelin käyttää graafista 16-bittistä lEEt/OS-käyttöliittymää. Järjestelmä on yhdellä 1,44 megatavun 3,5 tuuman levykkeellä. Tämä sivusto on kiintolevyllä. BBS on 360 kilotavun 5,25 tuuman levykkeellä. Vieraile myös BBS-purkissa portissa 486 (telnet)." Translated: "Server uses a graphic lEEt/OS-user interface. The system is on a single 1.44 MB 3.5 floppy disk. This site is on a hard drive and the BBS is on a 360 KB 5.25 inch floppy disk. Visit the BBS on port 486 (telnet)."
- jeffbee 5y ago
  We used to serve serious traffic off 486 machines, so if anything it's probably a software issue. Perhaps FreeBSD/i386 would be an appropriate choice? If you weren't there you probably don't realize that the 486 was a huge leap over the 386. We don't get 100% generational improvements these days. The 486 enjoyed a long life and its later incarnations were giving contemporaneous Pentium models a run for the money, and I'm not even counting socket-compatible upgrades from AMD and so forth. You could put 64MB RAM and big L2 caches and there were PCI motherboards in the later 486 years. Consider that the AMD Geode was basically the last 486 standing, and it was (is) more than adequate for routing between or firewalling fast ethernet links, serving HTTP etc.
  - prirun 5y ago
    I paid $8700 for a tower 25MHz 486 back in the day. Sheesh!
  - smoppi 5y ago
    My system is 100% 16-bit code and cannot access more than 640 kB of memory, and that's why it is so limited. I could probably increase the maximum amount of sockets and file handles to give it more capacity, but it still has its limits.

smoppi 5y ago

Video: https://www.youtube.com/watch?v=erM0K0oXk4M https://www.youtube.com/watch?v=erM0K0oXk4M In the end I minimized the HTTPSERV.APP window so that scrolling down the text would not consume too much CPU time.

smoppi 5y ago

Right now I cannot even access it locally from my lan, but it does answer to some of my pings. The HDD led is also blinking, which means that it is in fact answering to some HTTP requests. The TCP/IP stack is compiled for 64 simultaneous sockets.

ForOldHack 5y ago
Please paste an image up on Archive.org, so at least we can stare at the 'pre-meltdown' server. P.s. I used a 486 as a router for years, and even upgraded it when I found a Pentium Overdrive... which of course was vulnerable to the F00F bug...
- busymom0 5y ago
  https://web.archive.org/web/20220116193852/http://486servu.dy.fi/ https://web.archive.org/web/20220116193852/http://486servu.d...
CodeWriter23 5y ago
Next iteration: Caching HTTP server
tentacleuno 5y ago
I can't access it either. It looks like it's just timing out. We did it, guys! :D

loloquwowndueo 5y ago

Not holding up great it seems :)

velmu 5y ago
Loaded now. This is what's there: "Tämä palvelin käyttää graafista 16-bittistä lEEt/OS-käyttöliittymää. Järjestelmä on yhdellä 1,44 megatavun 3,5 tuuman levykkeellä. Tämä sivusto on kiintolevyllä. BBS on 360 kilotavun 5,25 tuuman levykkeellä. Vieraile myös BBS-purkissa portissa 486 (telnet)." Translated: "Server uses a graphic lEEt/OS-user interface. The system is on a single 1.44 MB 3.5 floppy disk. This site is on a hard drive and the BBS is on a 360 KB 5.25 inch floppy disk. Visit the BBS on port 486 (telnet)."
jeffbee 5y ago
We used to serve serious traffic off 486 machines, so if anything it's probably a software issue. Perhaps FreeBSD/i386 would be an appropriate choice? If you weren't there you probably don't realize that the 486 was a huge leap over the 386. We don't get 100% generational improvements these days. The 486 enjoyed a long life and its later incarnations were giving contemporaneous Pentium models a run for the money, and I'm not even counting socket-compatible upgrades from AMD and so forth. You could put 64MB RAM and big L2 caches and there were PCI motherboards in the later 486 years. Consider that the AMD Geode was basically the last 486 standing, and it was (is) more than adequate for routing between or firewalling fast ethernet links, serving HTTP etc.
- prirun 5y ago
  I paid $8700 for a tower 25MHz 486 back in the day. Sheesh!
- smoppi 5y ago
  My system is 100% 16-bit code and cannot access more than 640 kB of memory, and that's why it is so limited. I could probably increase the maximum amount of sockets and file handles to give it more capacity, but it still has its limits.