blog.technocake.net

Mac OSX is having opengl installed by default. However compiling a program that uses it wasn’t so straight forward.
How do you link the openGL library to your executable?

Took me a hard time googling this one, but eventually I found this blog post: http://dandesousa.com/2010/01/16/compiling-opengl-on-mac-os-x-or-linux/ .

gcc helloGL.c -Framework OpenGL

in linux / unix I think it’s :

gcc helloGL.c -lGL

for windows(in msys f.eks) I think it’s:

gcc helloGL.c -lopengl32

So in short, three different library names for three different os-environments.

Salmon, is the name of our bachelor project. Ours? Yeah, Erlend Blegstad and I have joined efforts to create a network administrating program .

Our first major breakthrough was: http://salmon.im/2012/02/07/first-topology-discovered-by-the-salmon-graph-discovery-by-spiral-swim-algorithm/

When I find myself in times of  trouble, monty python comes to me.

Speaking words of lispers : let it pdb let it pdb

Python seems always to amaze me when i come across built in functionality that is awesome and useful both at the same time. Im writing a challenge

for the netchalonged system  (see http://svn.technocake.net/repos/dev/code-phun/netchallonge )  when I was in a need for more debuging info. A quick google search revealed me this super nice article about pdb -> python debuging.  I compozed this cheat sheet summary of it. Read it yourself

in short:

import pdb
...
pdb.set_trace()
-- code to debug --


From the start, computer networks where closed mysterious things that only those designing it had a comprehensive overview of how it all worked. Each network where custom made, from hardware to communication protocols – custom to the needs of each organization ordering them. Then entered an era of agreement and standardization. And out of all this a protocol was born with the rise of the world wide web to transport those documents. HyperText Transfer Protocol. (HTTP). But it is now destined to die some might say. Are we not going to be able to browse the web anymore?

Security is an issue
Back when networks where closed, the posibilites of somebody or something in the middle of a communication link to eavesdrop on the content seemed impossible. Now it is too convenient for anyone with the slightest knowledge to do exactly this, listen in what your doing. As the human world is digitalizing with an increasingly amount of our daily life enacted on the web, there is a concern of privacy. Surveilance, fraud, control. The possibilities the one whom possesses the flow of your communication has are mind-blowing.

It is not encrypted. Http that is. And hence all inhabitants of the world have a potential open source to acces a vast amount of information. Information about you, your habits, the ones you care about and even your location of any given time in the worst case scenario. Enough mumble jumble. The risk could dramatically be redused by killing HTTP. The protocol that transports all your webpages, your facebook chatting, your emails on the clouds, your friends pictures and most of the world wide web. How can we manage without it?

We replace it with HTTPS. Which encrypts all data transported over the network. And hence eavesdropping suddenly becomes highly more complex. There is always a possibilty, to device a man in the middle attack. But constraining the amount of information that is clear to read for anyone possessing it, will be a major step in securing the world. HTTPS is exactly the same as HTTP, except that in encrypts all data transmitted and could also potentially authorize and authenticate the communicating entities.

Reference:

89-10-207-101:~ technocake$ iperf -c 89.10.206.196
————————————————————
Client connecting to 89.10.206.196, TCP port 5001
TCP window size: 129 KByte (default)
————————————————————
[ 3] local 89.10.207.101 port 56153 connected with 89.10.206.196 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.5 sec 515 MBytes 412 Mbits/sec
89-10-207-101:~ technocake$

root@snapp:/home/technocake# iperf -c 89.10.206.196
————————————————————
Client connecting to 89.10.206.196, TCP port 5001
TCP window size: 16.0 KByte (default)
————————————————————
[ 3] local 158.37.91.141 port 39666 connected with 89.10.206.196 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.1 sec 42.5 MBytes 35.1 Mbits/sec
root@snapp:/home/technocake#

say whoot?

http://www.linusakesson.net/programming/tty/index.php