I’m really glad this post was able to help you. I’m sorry but I don’t think I can help with your zlib problems. It was almost 2 years ago that I dealt with chrooting Python myself, so my memory is not exactly fresh, and unfortunately I don’t have an OpenBSD machine around anymore to have a tinker with. I did some Googling to see if I could find anything, and here’s the best I could find:

Here is a small open source program for chrooting Python on OpenBSD. I had a look at the source code and as far as I could tell from a quick glance it’s not doing anything particularly specical, just copying across library files. However, I did notice that right at the end it runs the command “chroot %s /sbin/ldconfig /usr/local/lib”, where %s gets replaced with your chroot directory. The comment for this bit of code says “Runs the command to generate a new ld.hints.so file in the chroot directory”. In other words, this script is not just copying the regular ld.hints file across like I did, but actually using some program to generate a new one. It is possible that this may make a difference for your problem, but it’s really just a guess. I hope it helps.

when i try to import zlib, i get ImportError: Cannot load specified object

zlib.so is where supposed to be: usr/local/lib/python2.6/lib-dynload/zlib.so*

any kind off help will be welcome… thank you in advance

any progress? I was really hoping to see the part where you start using arduino – I have the same motives tu start building a ROV – to have an interesting reason to learn smth. new

Thanks for your comment, sorry it took me so long to get around to approving it.

I think the Atari 2600, and other popular, clearly American machines like the Commodore 64 (not that this was intended as a gaming machine, but its commercial success was. I understand, largely due to its role as such), were largely responsible for my conception of video gaming as being primarily US-originated, these machines having predated the machines which were very plainly Japanese, like the NES and Master System. Thinking about it more carefully, I shouldn’t have made that inference because I *had* played Donkey Kong, a well known Nintendo creation, on the Atari, but I guess I never made the connection and asked myself which other Atari classics were Japanese (Frogger and Galaxians too?!). It’s nice to have a clearer understanding of how things played out in those days.

- The first coin-operated video game to be commercially sold was “Computer Space” by Nolan Bushnell and Ted Dabney (both Americans) in 1971 followed by “Pong” in 1972. By the end of 1972, they had named their fledgling company Atari.

- The first home video game console was created by Ralph Baer (an American) and released in May 1972 by Magnavox under the name Odyssey.

- American-based Atari released the incredibly popular Atari 2600 in 1976, one of the most successful home gaming consoles in history.

By the end of the 1970s through the early 1980s, however, the Japanese video game industry was flourishing and they were indeed responsible for many of the popular and well-remembered classics from that era: Space Invaders, Pac-Man, Galaxian, Galaga, Donkey Kong, Frogger, Dig Dug, Zaxxon, etc. But American developers contributed several excellent games from that same period: Asteriods (Atari), Battlezone (Atari), Bezerk (Stern), Centipede (Atari), Defender (Williams), Missile Command (Atari), Joust (Williams), Q*bert (Gottlieb) and Star Wars (Atari) to name a few.

Technically speaking, I would venture to say the world’s first interactive video game was a missile simulator invented in 1947 by two Americans (Thomas Goldsmith and Estle Ray Mann) using cathode ray tube technology and analog circuitry, allowing the player to position a dot on the screen with screen overlays used for targets.

Regards,

JP

I certainly didn’t mean to imply that C was irrelevant today. Looking back at it, the “without a compelling argument in favour of it” part of my statement probably should have been elaborated to make it clear that compelling arguments do exist in a lot of cases, like writing operating systems or software for small embedded environments.