default.theme.tar

And my precious key bindings, see this post to understand why it is from F7 to F10.

For this to work, just copy/paste this into your irssi:

/bind meta2-18~ key F7
/bind meta2-19~ key F8
/bind meta2-20~ key F9
/bind meta2-21~ key F10

And this:

/bind F7 /q
/bind F8 /names
/bind F9 /window prev
/bind F10 /window next

The fist block is just binding the real key names with F names for comprehension.

First it’s unbootable, it says some file is missing, you replace the file, some other file is missing, then you put in the windows cd and start the repair. Now it boots, time to re-activate windows, it just hangs because it can’t load internet explorer because it is all corrupted somehow. Believe me this happens frequently.

This is how you fix it and it’s reallty easy, the goal is to reinstall Internet Explorer, now you think “Safe Mode with networking support” but this mode isn’t accessible at this time. You will have to download it from another sane installation. Downloading IE8 from microsoft will do the trick, be sure it is the stand-alone installer that doesn’t require internet connection. Uncheck “Install updates” and you’re done.

Now reboot and pray that damn window will just pop up.

You can easily fix this and use regular PgUp/PgDn by simply adding a line to your ~/.screenrc. I really don’t know why this isn’t a default setting except that it seems to mess with Vim scrollback.

Here’s the line:

termcapinfo xterm ti@:te@

Enjoy.

The problem with zsnes is that the devs doesn’t seems to care anymore, which is understandable. But what happens to people like me who runs a 64-bit OS ? Nothing. The zsnes team haven’t planned porting afaik.

BUT, somehow, someone made a package of zsnes with the old good 1.42 version when you were able to use the netplay, and the best of it, it runs on 64bit. It’s a 32bit binary but the package is preconfigured to use linux32 and it runs pretty fine.

Here it is.

We will use a terminal multiplexor GNU Screen, which provide multiple terminals. We will also implement a neat tab bar to allow naming/showing tabs and automatic session re-attachment capability.

Follow these steps to significantly enhance your distant shell experience, you will need to install screen and ssh, mutt and irssi are optional.

The first step involves using environment variables in order to detect if the login is locally originating or not. If the user is logging from a distant machine, we will reattach an existing detached screen session or create a new one.

When logging in remotely, the most evident distinction i’ve found between a local and remote shell is the environment variable SSH_CONNECTION=, with this var we have a way of detecting remote logins easily and launch something else accordingly.

Insert in your ~/.bashrc:

if env | grep -q SSH_CONNECTION; then
. ~/.screenlogin.sh
fi

The previous lines will launch .screenlogin.sh upon a remote connection, a second script which will contain:

DETACHED=`screen -list | grep Detached | wc -l`
if [ “$DETACHED” = 1 ]; then
screen -DR
fi

Make the script executable:

chmod +x .screenlogin.sh

Now exit and login back again.

As long as they keep using the same methods, all you need to do is use a decent torrent client like Ktorrent who gives you these kinds of options:

[X] Use encrypted protocol
[ ] Allow unencrypted connections

I noticed that if you allow unencrypted connections it does not get any better, probably because they can catch a couple of torrent packets and spot the port then apply port throttling, otherwise it could be just another online game that runs on a random port.

There is one inconvenient to this method, not everybody uses decent torrent clients, so you lose the participation of some of them. While running it encrypted only, i connected to many Azureus, Transmission, libtorrent based, they should then contain such options.

Let’s create it and paste this into it:

#hardstatus string ” %wb%-w%wr%n %t%-%+w %=%D %d %M %y %c”
#hardstatus string “%r%c%k | %w% ? (%h)% ?”
#hardstatus string “%{gk}[ %{G}%H %{g}][%= %{wk}%?%-Lw%?%{r}(%{W}%n*%f %t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B} %m/%d %{W}%c %{g}]“
hardstatus string ‘%{= c}[ %{W}%H %{c}][%= %{= w}%?%-Lw%?%{c}(%{W}%n*%f%t%?(%u)%?%{c})%{w}%?%+Lw%?%?%= %{c}][%{W} %d/%m %{W}%c %{c}]‘

bindkey -k F1 prev
bindkey -k F2 next

screen -t irssi 1 irssi -c irc.freenode.net
screen -t mutt 2 mutt
screen -t monitor 0 lwatch -i /dev/xconsole

hardstatus alwaysignore hardstatus alwayslastline

The whole aesthetic thing reside in the first uncommented line, this is where it sets what is displayed in the hardstatus line which is always the last line. You can find documentation about the variables that can be used to display different types of information in the screen man page. ($ man screen).

As for the bindkey, you’ve guessed they bind keys to go forward and backward in your terminal tabs, and yes F1 means F11, don’t ask me why. I use F11 and F12 because i intend to use F9 and F10 in irssi to move between windows.

Verify the current certificate gmail is using with this command:

openssl s_client -connect smtp.gmail.com:995 -showcerts

Hit Ctrl-c to terminate the command once you got something like this:

—–BEGIN CERTIFICATE—–
MIIC3TCCAkagAwIBAgIDCDijMA0GCSqGSIb3DQEBBQUAME4xCzAJBgNVBAYTAlVT
MRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4IFNlY3VyZSBDZXJ0
aWZpY2F0ZSBBdXRob3JpdHkwHhcNMDcxMDI1MTc1MzE2WhcNMDkxMjI0MTg1MzE2
WjBoMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEWMBQGA1UEBxMN
TW91bnRhaW4gVmlldzEUMBIGA1UEChMLR29vZ2xlIEluYy4xFjAUBgNVBAMTDXBv
cC5nbWFpbC5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAO03QxerFKZV
8yeomuL4zSl8Pr7hMWnKMMgp/CwhwadeBmL0LQHHbjL/6z/Z59ZQvrztqkwhchA2
APKzUwRVTyn7Shx6vBqk6oFmTqoOLmY6hbq6l8uVdUv0AfbHwio8CnLpK2+nbuFl
flPwx1DH0E3grD8+CrH5SmScfTWbDkcXAgMBAAGjga4wgaswDgYDVR0PAQH/BAQD
AgTwMB0GA1UdDgQWBBTJRG/OFpZt+BV43JM3NshHMjpwazA6BgNVHR8EMzAxMC+g
LaArhilodHRwOi8vY3JsLmdlb3RydXN0LmNvbS9jcmxzL3NlY3VyZWNhLmNybDAf
BgNVHSMEGDAWgBRI5mj5K9KylddH2CMgEE8zmJCf1DAdBgNVHSUEFjAUBggrBgEF
BQcDAQYIKwYBBQUHAwIwDQYJKoZIhvcNAQEFBQADgYEAOKr3mhxtwFCS3J6lbeaf
3KrHKi935BZkI75sRbON+hog0t2ovcM2i7fxs3xneH8USLsHgfxNBj9tkMogMK/K
sO/NUVZ/IfyqcNNkp2619qTQXthKRH42JKpAKgNhT1bdno3pxn+eDEpqmU3CE7IP
HDCjWOK1fGkZ/yFAuTxuxAc=
—–END CERTIFICATE—–

Copy & Paste it to some file, let’s say gmail.pem in /usr/share/ssl-cert/ (debian-specific)

Stay in that directory and type:

c_rehash .

Then:

openssl x509 -fingerprint -md5 -noout -in gmail.pem

The first line will create a symbolic link based on the hash value (a fingerprint) we will use in our ~/.fetchmailrc, the second prints out that MD5 fingerprint, copy it and open your .fetchmailrc in your favourite text editor
and add something that look likes this:

poll pop.gmail.com with proto POP3
user ‘USERNAME@gmail.com’ there with password ‘PASSWORD’
options keep ssl sslfingerprint ’44:A8:E9:2C:FB:A9:7E:6D:F9:DB:F3:62:B2:9E:F1:A9′
sslcertck sslcertpath /usr/share/ssl-cert/

It’s time for the final run test, just type fetchmail and watch it fetch your mail without complaining.

Append this to the end:

relayhost= [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous

smtp_destination_rate_delay = 60
relay_destination_rate_delay = 60

mailbox_command = /usr/bin/procmail -a $EXTENSION

The two paths you see above, /usr/bin/ & /etc/postfix will remain the same on almost any GNU/Linux distro, if you want to set this up on FreeBSD, it will be /usr/local/bin & /usr/local/etc/ respectively.

Next, create the sasl_passwd file in the /etc/postfix directory, insert the following:

[smtp.gmail.com]:587 USERNAME@gmail.com:CLEAR_TEXT_PASSWORD

Replace the two highercase variables with your own, save and quit.

Then type this to hash the file so it could be used by postfix:

postmap hash:sasl_passwd

This will result in a sasl_passwd.db, this is what hash:/etc/postfix/sasl_passwd refers to.

Restart postfix:

./etc/init.d/postfix restart

The final step is to test if it works well, to do so fire up mutt or your preferred mail client and send a mail.

You will notice there is some warning messages in /var/log/mail.log, don’t worry about them:

certificate verification failed for smtp.gmail.com[XXX.XXX.XXX.XXX]:587: untrusted issuer /C=ZA/ST=Western Cape/L=Cape Town/O=Thawte Consulting cc/OU=Certification Services Division/CN=Thawte Premium Server CA/emailAddress=premium-server@thawte.com

The fact you dont *fully* trust google doesnt mean you can’t send mail through them.

Section “InputDevice” Identifier “keyboard”
Option “XkbRules” “xorg”
Option “XkbLayout” “ca”
Option “XkbVariant” “fr”
EndSection

Just modify your keyboard section with the above Xkb options.

And there you are, with a french canadian keyboard layout! Now i can watch pictures with french accents in the filename…