|| Hacker TEST ||

( Herewith a compendium of fact and folklore about computer hackerdom, cunningly disguised as a test. )

Scoring – Count 1 for each item that you have done, or each question that you can answer correctly.
If you score is between:         You are

0×000 and 0×010       ->        Computer Illiterate

0×011 and 0×040       ->         a User

0×041 and 0×080       ->         an Operator

0×081 and 0x0C0       ->         a Nerd

0x0C1 and 0×100       ->         a Hacker

0×101 and 0×180       ->         a Guru

0×181 and 0×200       ->         a Wizard

Note: If you don’t understand the scoring, stop here.

And now for the questions…
( …and this may take a while. But, if U R a true hacker then it shouldn’t deter U… )

0001 Have you ever used a computer?

0002 … for more than 4 hours continuously?

0003 … more than 8 hours?

0004 … more than 16 hours?

0005 … more than 32 hours?

0006 Have you ever patched paper tape?

0007 Have you ever missed a class while programming?

0008 … Missed an examination?

0009 … Missed a wedding?

0010 … Missed your own wedding?

0011 Have you ever programmed while intoxicated?

0012 … Did it make sense the next day?

0013 Have you ever written a flight simulator?

0014 Have you ever voided the warranty on your equipment?

0015 Ever change the value of 4?

0016 … Unintentionally?

0017 … In a language other than Fortran?

0018 Do you use DWIM to make life interesting?

0019 Have you named a computer?

uTorrent Tweak/Hack: Increase Download Speed

The following is a comprehensive  list of public trackers. You will need to add them in your tracker list for a particular torrent which is downloading very slow. Right-Click on the torrent which is very slow and go to Properties. Then under the General tab, you’ll notice a list of existing trackers for the selected torrent.  Just paste the below list right there. On … Read More

via 2600Hertz

HowTo: Hack into any Executable using GDB

Hacking does not have to be a bad thing, as you see here.

GDB, the GNU Project debugger, allows you to see `inside’ another program while it executes –or– what another program was doing at the moment it crashed. . GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act: Start your program, specifying anything that might affect its behavior. Make your program stop on specified conditions. Examine what has happened, when your program has stopped. Ch … Read More

via 2600Hertz