Slashdot Mirror
Contiki on Ethernut
randomErr writes "Many of you may remember Contiki, the OS and GUI for the C64 and many other 8 bit platforms, which was posted on Slashdot in March. Adam Dunkels has ported Contiki to a more modern platorm: the open source Ethernut board. You can also see the working webserver and VNC server."
You can also see the working webserver and VNC server.
:)
If that webserver is hooked up to the net, you won't be seeing it for long.
My blog
The answer should be obvious: a web server able to run on a C64 can run on any embedded system that can emulate a 6502 CPU. This means I can put a web server into my mouse. The possibilities are stunning...
Ceci n'est pas une signature
Just say it's rumored to contian SCOde - all hell will break lose.
If you keep throwing chairs, one day you'll break windows....
Now go forth, Slashdot readers, and give that server a good kick in the ethernuts!
There's a Mercedes gap too. I want one and can't afford one, but it's not government's job to do anything about it.
Imagine a low cost, already documented, platform that could be used for say plastic injection machine controllers. Think about a Minitel like device for a $100.
You say things that offend me and I can deal with it. Can you?
It seems so unfair, Ethernut vs. Slashdot vs.
/cgi/tcp page and check the connections, truely evil.
Almost like David vs. Goliath, except in this case, David has two broken arms, no legs, 3 gunshot wounds center mass, and massive blunt trauma to the head. And Goliath is a hungry T-Rex.
I gotta say, the thing appears to still be responding right now as I post, not bad, not bad at all. Not necessarily *working*, but responding. Hit that
HA. I got to see the true Slashdot effect in action.
... that's right, TWO... connections. Literally, a few seconds later I refreshed the page and constantly got garbage in return. (Basically, it looked like the server would never output the entire HTML document. I'd sometimes see some gibberish, sometimes some CSS code, sometimes only the navigation table...) After about 60 seconds of refreshing the page, I finally saw the page again. Results: about 50 connections. And this Slashdot article only has 19 comments so far.
:D
I went to the Current Connections screen and only saw 2
Burn little server, burn.
Karma: NaN
And, it seems like the web server is withstanding the Slashdot effect! I remember there was actualy a C64 based web server that was actualy able to hold up based on some pretty impressive TCP hacks that made the connections 'stateless' (by embedding state in the TCP sequence number, IIRC)
:)
:P
That said, I doubt a 14 mhz chip would really have that much of a problem dealing with hits. I think most of the systems that 'go down' when hit by a hit torrent do so because A) They run out of bandwidth, get capped, etc. or B) They are using super-bloated web app code when they really don't need to. You often see things like "MySQL errors" and the like from too many user connections. I think a lot of web developers don't really bother to code for efficiency at all. I mean seriously, the work you need to do to serve a mostly static page is really tiny. An intelligent caching routine should solve most of the problems, but most web-apps it seems get all data out of the DB every run, possibly doing multiple queries. Keep in mind a 386 running Apache can saturate a t1 line. That would have a clock speed of about the same thing, I think the fastest 386 was about 25 mhz. Of course, this is a 32 bit chip, not 8
The way autopr0n works, I have a class system that holds all the data, and gets updated independently of the database whenever new data is entered. I hardly ever need to do a query to get new data out of the system. Unfortunately, this means that it's using code I wrote myself, which is just buggy as hell : P. Oh well. It runs 'well enough'
autopr0n is like, down and stuff.
Hey, just kidding. :)
We are all evil minions armed with Web Browsers , attacking whoever the Slashdot Mastermind points to.
Slashdot Sig. version 0.1alpha. Use at your own risk.