Monthly Archives: June 2011

MK9: Fatalities

BARAKA
FATALITY 1 – (punch) ← → ↓ → (1)
FATALITY 2 – (punch) → → ↓ ↓ (3)
PIT FATAL. – (vary) ↓ ↓ ↓ ↓ (3)
BABALITY – (jump) →←→ (4)

CAGE (also: JOHNNY CAGE)
FATALITY 1 – (touch) → → ← ↓ (3)
FATALITY 2 – (punch) ↓ → ↓ → (4)
PIT FATAL. – (vary) ↓ ← → (BL)
BABALITY – (jump) →←→{4)

CYBER SUB-ZERO
FATALITY 1 – (jump) ↓ ← ↓ → (2)
FATALITY 2 – (jump) ↓ ↓ ← ↓ (1)
PIT FATAL. – (vary) ↓ ↓ ↑ (BL)
BABALITY – (jump) ↓ ← → (BL)

CYRAX
FATALITY 1 – (touch) → ↓ → ← (2)
FATALITY 2 – (jump) → ↓ ← → (1)
PIT FATAL. – (vary) ↓ ↓ ↑ (BL)
BABALITY – (jump) ↓ → ← (2)

ERMAC
FATALITY 1 – (jump) ↓ ↑ ↓ ↓ (BL)
FATALITY 2 – (jump) → ← → ↓ (4)
PIT FATAL. – (vary) ↓ ↑ ↓ ↓ (3)
BABALITY – (jump) ↓↓←↓(2)

JADE
FATALITY 1 – (full) ↑ ↑ ↓ → (1)
FATALITY 2 – (sweep) ← ↓ ← ↓ (4)
PIT FATAL. – (vary) ← → ↓ (BL)
BABALITY – (jump) ↓↓→↓(4)

JAX
FATALITY 1 – (touch) ← → → ← (2)
FATALITY 2 – (punch) → → ← ↓ (3)
PIT FATAL. – (vary) ↓ → ↓ (1)
BABALITY – (jump) ↓↓↓(3)

KABAL
FATALITY 1 – (punch) ← → ← ↓ (1)
FATALITY 2 – (sweep) ↓ ↓ ← → (BL)
PIT FATAL. – (vary) ↓ ↓ (4)
BABALITY – (jump) →↓ ← (3)

KANO
FATALITY 1 – (punch) ← ↓ ← → (1)
FATALITY 2 – (punch) ↓ ↓ → ← (4)
BABALITY – (jump) →→↓↓(3)

KITANA
FATALITY 1 – (sweep) ↓ ↓ ← → (2)
FATALITY 2 – (sweep) → ↓ → ← (3)
PIT FATAL. – (vary) → ↓ ↓ (3)
BABALITY – (jump) →→↓→(4)

KUNG LAO
FATALITY 1 – (sweep) ← → → ← (2)
FATALITY 2 – (punch) ↓ ↓ → ← (1)
PIT FATAL. – (vary) ↓ → ↓ (BL)
BABALITY – (jump) ↓ → ↓ (2)

LIU KANG
FATALITY 1 – (punch) → ← ↓ ↓ (3)
FATALITY 2 – (jump) ↓ ↓ → ↓ (4)
PIT FATAL. – (vary) ↓ ↓ ↓ (1)
BABALITY – (jump) ↓ ↓ ↓ (3)

MILEENA
FATALITY 1 – (jump) ← → ← → (2)
FATALITY 2 – (jump) ← → ← ↓ (3)
PIT FATAL. – (vary) ↓ ↓ ↓ (1)
BABALITY – (jump) ↓ ↓ → ← (2)

NIGHTWOLF
FATALITY 1 – (jump) ↓ → ↓ ← (4)
FATALITY 2 – (punch) ↓ ↓ → ← (1)
PIT FATAL. – (vary) ↓ ↓ ↓ (BL)
BABALITY – (jump) →←→← (4)

NOOB SAIBOT
FATALITY 1 – (jump) ← → ← ↓ (4)
FATALITY 2 – (jump) ↓ ↓ ← ↓ (BL)
BABALITY – (jump) →↑→ (1)
PIT FATAL – (vary) →↓→ (BL)

QUAN CHI
FATALITY 1 – (sweep) → → ↓ ↓ (1)
FATALITY 2 – (sweep) ↓ → ↓ → (4)
PIT FATAL. – (vary) ← → ↓ (2)
BABALITY – (jump) →↓← (2)

RAIDEN
FATALITY 1 – (jump) ↓ → ↓ → (1)
FATALITY 2 – (sweep) ← → → ↓ (4)
PIT FATAL. – (vary) ↓ ↓ ↓ (2)
BABALITY – (jump) ↓←↓ (4)

REPTILE
FATALITY 1 – (sweep) → → ↓ ↑ (3)
FATALITY 2 – (sweep) ↓ ↓ → ← (1)
PIT FATAL. – (vary) → ↓ ↓ (BL)
BABALITY – (jump) ← → ← ↓ (3)
FATALITY 3 – (jump)←←→↓(BL)

SCORPION
FATALITY 1 – (touch) → ↓ → (2)
FATALITY 2 – (touch) ← → ← (3)
PIT FATAL. – (vary) → ↓ ↓ (1)
BABALITY – (jump) ↓←→↓ (2)
FATALITY 3 – (jump) ↓↑↑(2)

Kratos*: PS3 only
Fatality 1 – D,D,B,F,2 (Close)
Fatality 2 – D,B,D,F,1 (Jump)
Stage Fatality – D,D,D,3 (Varies)
BABALITY – D,F,B,2 (Jump)

SEKTOR
FATALITY 1 – (full) → ↓ ← → (3)
FATALITY 2 – (full) ↓ ↓ → ← (1)
PIT FATAL. – (vary) ↓ → ↓ (BL)
BABALITY – (jump) ←↓↓↓(4)

SHANG TSUNG
FATALITY 1 – (sweep) ← ↓ → (3)
FATALITY 2 – (jump) ↓ ↓ ← ↓ (2)
BABALITY – (jump) ↓ ← ↓ (3)
PIT FATAL – (vary) ↑↑← (3)

SHEEVA
FATALITY 1 – (sweep) → ↓ ↓ → (1)
FATALITY 2 – (punch) → ← → ← (4)
PIT FATAL. – (vary) ↓ ↓ ↓ ↓ (1)
BABALITY – (jump) ↓↓↓←(4)

SINDEL
FATALITY 1 – (sweep) ← → ↓ → (1)
FATALITY 2 – (sweep) ← → ↑ (2)
PIT FATAL. – (vary) ↓ ↓ ↓ (1)
BABALITY – (jump) ↓↓↓↑

SMOKE
FATALITY 1 – (sweep) ← → ← → (1)
FATALITY 2 – (punch) ← ← ↓ → (2)
PIT FATAL. – (vary) → ↑ ↑ (1)
BABALITY – (jump) ↓ ← ↓ → ↓

SONYA BLADE
FATALITY 1 – (jump) ↓ ↓ ← → (1)
FATALITY 2 – (sweep) ↓ ← → ← (4)
PIT FATAL. – (vary) ← → ↓ (2)
BABALITY – (jump) ← → ↓ ← (3)

STRYKER
FATALITY 1 – (punch) → ↓ → (3)
FATALITY 2 – (punch) ↓ → ↓ → (RT)
PIT FATAL. – (vary) → ↑ ↑ (3)
BABALITY – (jump) ↓→↓←(2)

SUB-ZERO
FATALITY 1 – (sweep) ← → ↓ → (4)
FATALITY 2 – (punch) ↓ ← ↓ → (2)
PIT FATAL. – (vary) → ↓ ← (2)
BABALITY – (jump) ↓ ← ↓ (4)
FATALITY 3 – (punch) → ↓→ (2)

“Why is there no /var/log/messages any more?”

Woah!  I just noticed this was missing.  I have used this for many years as my go to location for messages in my Ubuntu Linux environments.
With the newest update of Ubuntu this seems to be gone.  {Shocker}

 

But, there is no need for worrying…
The logs I was looking for are in /var/log/syslog. This was a deliberate decision in natty to reduce log duplication (everything logged to /var/log/messages was always being logged to /var/log/syslog as well).

The Daily Reboot –

There are times when you had a bad system and know it.  And the action to keep it available is rebooting daily.  While I am not in favor of the reboot, it may be necessary.  So I use the following steps on a pesky Ubuntu server I know.

Log into your Ubuntu server and ‘sudo –i’ to enter the root console.  Place a file ( I named mine reboot ) in the /etc/cron.daily/ path with the following contents:

#!/bin/bash
reboot

 

This will create a very simple shell script to be run daily.  But for this to all work you need to also make that script executable or this will not work.

 

To make the script executable, do the following:

  1. Ensure your script is in the /etc/cron.daily/ path
  2. Modify your script to be executable by using the following commands  ‘chmod a+x /etc/cron.daily/<name of script (reboot in my case)>
  3. Ensure your script will run by running:  run-parts –test /etc/cron.daily/ – the output will be all scripts located in that path, if you see yours, then it is working

 

If you want to immediately run your script , run “run-parts –verbose /etc/cron.daily”

Kernel Panic Reboot (Ubuntu)

While I never had this happen on my Ubuntu Web Server, I have known a system in my life that seems to panic and lock up. Ubuntu Server doesn’t have this enabled by default, so I enabled it by adding the following to /etc/sysctrl.conf

‘kernal.panic=60′

This will auto reboot my server 60 seconds after a kernel panic

Skype Disruption

Today I find myself slightly frustrated when  I attempted to load Skype @ my office.  To my surprise Skype is having issues yet again all following its acquisition to Microsoft’s hands. Announced on the heartbeat page http://heartbeat.skype.com was the following.

“A configuration problem has meant that some of you have been disconnected from Skype.

We’ve identified the cause of the problem, and have begun to address it. If you’ve been affected, you should start to see improvement in the next hour or so. You shouldn’t need to manually sign back in to Skype – it should reconnect automatically when it’s able to do so.

We apologize for the disruption to your conversations.”

 

Later adding the following as an update:

“We are continuing to address today’s problems, and are seeing indications that the situation is improving.

If you were disconnected from Skype earlier, you shouldn’t need to manually sign back in to Skype – it should reconnect automatically when it’s able to do so”

 

 

Skype’s outages are coming during a transitional time for the company. Last month, the software giant announced plans to acquire Skype for $8.5 billion. Once the deal closes later this year, Skype will become its own division at Microsoft under the supervision of its current CEO Tony Bates. Microsoft has said that it plans to integrate Skype into its Kinect motion-gaming peripheral, Windows Phone 7, and other platforms.