With any ISP your going to be paying a rental fee whether you use their shit or not. I work for a DSL provider and know other who work for comcast, and yet others that work for hughesnet and other ISPs. No matter what you do or what you try, your always going to pay that rental fee. I would say keep the shitty modem they give you since your always going to be paying for it, then use your own routing device.

The plus side is, since your paying for this shitty modem monthly, do with it what you will. I have pulled apart my modems from my ISP and found the headers to flash my own firmware. Hell, one time I had everything soldered into the headers then called my ISP, forced them to push a firmware update, then had a dump of the full update and all. With a binwalk, I had access to everything I ever needed.

Moral of the story, they will charge you for the modem/router whether you use it or not. Might not show up on your bill, but in the end your still paying for the shit.

You usually need to manually bind the Ctrl+Alt+T terminal shortcut though, at least in Debian/Ubuntu-like distros.

Everything I mentioned is manual key binding except the tty shell. Also Mint and Ubuntu ctrl+alt+t bring up a shell for me right out of the box, no manual anything.

Sorry for it being vimeo, but this was at a con we have in town.

Link.

Did you use to play Tiberian Sun back in the day by chance?

Wow, I haven't heard that from someone in a while. I'm playing Tiberian Sun atm. You can get it free from cnc-comm.com now, the released it to the public along with other old CnC games.

@OP:
Welcome to le boards.

Prophets are not perfect in any means.

Welcome to le boards

Modularity. Let system heavy handly heavy stuff. Let the lighter stuff handle the lighter stuff. The CPU and GPU is set up the way it is for a reason. I have to say, greater minds than our own have thought and re-thought this same reasoning. Conclusions result in consumer electronics. Yes military and others may have higher/better stuff, running multiple GPUs instead of regular instructions on a CPU. But this is all consumer.


Grab yourself some FPGA's and test shit out for your self.

There is no learning from this sorry OP.

I have to say that there is a lot you need to learn I suggest picking up a different language that forces things. Maybe a flavor of C or Java maybe. The code posted is like said just code. Bad code but at least there is effort. You need more practice, and something as loose as Python is not where you need to focus on. I suggest Java or C# or something.