Hacker News new | past | comments | ask | show | jobs | submit | mbbrutman's comments login

Cute article, but I'm not quite sure how you missed the mTCP HTTPServ program ...


I'm sure I can go for a few more years until the next patch ...

On a more serious note, the web server is the problem here. I've tried to run long periods of time before but eventually it would crash. I finally found a 10+ year old parsing bug that wasn't handling quoting correctly, and it was some sort of crypto coin mining JSON request that tripped the bug. So even what I thought was bullet proof years ago turned out to be broken by changes in the user traffic.


This is a priceless anecdote, thanks for sharing!


Sadly the project is mostly unrelated to my day job. I started mTCP at least 6 years before joining Google and at most of my time at Google is spent on much less fun things.

On the plus side, when I finally do get around to building a cluster of these and a load balancer I'll know what to do. ;)


Its probably on par with the feature set of googles internal load balancers :P


Maybe, with some qualifications. A machine that is powered on but serves almost no traffic would also qualify but not be terribly interesting.

I'm just happy it's been surviving the hug of death for 12+ hours now. Given the age and software that might be the true accomplishment.


There were several speeds of the V20, including the base version at 5Mhz. Using it as a drop-in replacement and keeping the system clock speed the same the NEC V20 would still give you a 15 to 20% performance bump because it used less clock cycles when executing many insgtructions.

(This machine has not been altered to speed the clock.)


The machine continues to receive the hug of death .. especially with our friendly Europeans waking up. Have faith, it's still running. (And it's been surviving like this for four hours now.)

I've turned down the logging level a little bit and turned off the beeper. On this machine, a 50ms beep on the motherboard buzzer is 50ms of delay. :)


I think it's impressive how your site's managed to stay online when many sites hosted on much more powerful hardware haven't been able to handle HN frontpage levels of traffic.


The power of good old static sites. I saw some number of the amount of electrical power going to web servers and it was like single digit percents.

The js-web is a huge waste environmentaly and it is sad since js is mostly used to spy and show ads.


Thanks ... I think people are having time-outs so it's not anywhere near close to perfect, but the machine has been running at 100% for five hours or so now and it is not crashing, so I'm happy.


I very friendly opened the link, and it is still serving pages. The images are pretty slow to load, though. While reading the page, I thought it was just text, but then suddenly a banner appeared.

Great demo of what such a machine can do, and how much we take our 3GHz, 12 core machines for granted.

BTW, how do you keep it dust-free?


What OS signature do you get when you portscan it? :)


http://floppy.museum also running mTCP HTTPServ, but on 80286 class hardware.

(That was featured earlier this year on HN.)


486? Nah. 4.77Mhz NEC V20, which is just slightly faster than an 8088.

This should tide you over: http://www.brutman.com/PCjr/pcjr_web_server.html

The main page is the best link. You might want to try back later after the initial rush; the machine is getting pounded.


Got through today. Very impressive work!


FreeBSD is crusty, but is it really bad enough to compare to DOS 5.02?

Besides, who needs 32 bits when 16 will do ...

(Not serious.)


> Besides, who needs 32 bits when 16 will do ...

Hahaha, well played! :-)

Seriously, though, it is impressive to have a DOS machine running a web server in today's environment.

I assume dynamic content is produced via Sidekick[0]...

(ducks)

0 - https://en.wikipedia.org/wiki/Borland_Sidekick


FreeBSD is fine; FreeBSD with 4000 days of uptime would concern me just like a Linux box with that much uptime.


Haha :) I always extend my respect for such stuff.. It just shows how everything is bloated and ballooned today.. You barelly can browse modern web with 32bit today.. VSZ hits the sky (3GB).


100+ days of runtime on nearly 40 year old hardware not designed as a server exposed to all of the garbage coming in on port 80.

Remember, this is a home computer from the mid 1980s. This thing is way outside of it's duty cycle. And the software is holding up pretty well too, even during what is effectively a DoS attack on a DOS machine.


Oh they mean a real web server exposed to the internet (not hiding behind an NGINX). Impressive.

Hug of death means I didn’t see the article


Wow expectations sure have come down! When that computer was new, people had uptimes measured in years, 100 days was pedestrian.


And we were all on HN 40 years ago huh?


Well it’s about a computer from 40 years ago! That’s why I don’t see what’s so special; any computer from that era that still works today could easily run for a hundred days.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: