why stop using GNU screen?

I've been using GNU screen effectively for the last couple of years and although I've heard about tmux I've never considered changing. Well, basically for commodity purposes and because screen did the job.....

So, for those unfamiliar with these type of tool, tmux and screen are software apps that allow you to multiplex VT sessions.  Let's say they are window managers for text console.

more @:

• http://en.wikipedia.org/wiki/Tmux
• http://en.wikipedia.org/wiki/GNU_Screen

Recently I've hit some limitations of screen and decided to try out tmux (which actually does a great job). 

Obviously I am still used to screen interface and commands, so the path to get a more "proficient" level with tmux is going to be evolutive as it always is.

I found an interesting comparison blog post about both tools here: 

http://www.techrepublic.com/blog/linux-and-open-source/is-tmux-the-gnu-screen-killer/

Cheat sheet

tmux < -- to --> screen :

• http://www.wikivs.com/wiki/Screen_vs_tmux
• http://www.dayid.org/os/notes/tm.html

First Post

This blog started today because a friend asked "what is /dev/null ?".

So, why start a blog after that question? First of all, there is so much "garbage" information on the Web nowadays. Information that should be redirected to the null device :-P

Secondly, I've started talking with Pedro Gomes about the idea of create a blog with useful geek information. Like useful hacks, informational stuff, programming stuff, etc.

Besides sharing useful information with the world, it is a good repository!

Oh, btw /dev/null it's a virtual file of Unix-like operating systems. This special file discards all the information written to it but can be used for reporting successful writing of data.

It can be used to redirect the unwanted output of a program to it. It's called the black hole in computer jargon.

Psst, if you log in a machine and you don't want that your commands are logged, just redirect .bash_history to the black hole ;-)