bootsect /nt60 c: /mbr

Once I did this, that machine was back in action. And it only took me two weeks or so in order to get around to it.

Our guild was recently discussing them, as someone in the guild had this happen to them for a second time... And in going back and forth between myself and someone who thinks that Blizzard is making a mint off these things (hint: they don't) Someone else replied with the following in the thread, and I thought I would share it with a much more general audience.

PERSONALLY

I think the only real, permanent, and logical way for blizzard to fix this 'hacker' problem is by raising up a massive army of Undead Nazi Vampires, lead by a shirtless Gerard Butler to lead an invasion into China and Russia, overthrowing the local governments on a crusade to flush the hackers out from where they live! Blizzard would then consolidate power and turn the two largest countries in Asia into worlds first corporately owned country. With this display of power, combined with their new military might, no one would dare try to hack a blizzard game ever again!

This plan has drawbacks however, as legions of undead vampires (who happen to be nazi's) would soon grow restless, and crave human flesh. After blizzard loses its hold on such creatures, the Vampires would launch a full scale assault on Israel, instantly springing the United States, the UN, and NATO to its aid. By this time the other middle eastern countries, now coupled with their new found undead allies, would join in the onslaught and unite against the rest of the world. World War III would break out, the devestation would be horrible, and the world would cower before the unstoppable Undead Vampire Nazi's.

That is...until the Dave creates a super virus that will specifically target and destroy the 'undead' plague; Effectively crippling the Undead army, and their lust for flesh. With the them out of the way, the path would be clear for the Allied nations to finish the war in a quick manner. Millions would have died in the first global war in nearly 70 years.

The world will want someone to blame. At the UN trial, all the execs from Blizzard will be put on trial, and tried for war crimes for creating the Undead Nazi Vampires in the first place. All of their property will be seized, and all the WOW servers will be shut down, effectively ending the happiness of me, and millions of others around the world.

.....

So unless you want THAT to happen...Get an Authenticator. Its not a perfect solution, but its better than undead Nazi Vampires.

Well done.

1) 'service': a program that responds to requests from clients. Each
service is identified by a "bus name" which clients use to find the
service and send requests to it. The bus name usually looks like
"org.foobar.Baz". A program can claim more than one bus name; NM claims
org.freedesktop.NetworkManager and
org.freedesktop.NetworkManagerSystemSettings, each is a unique serivce
which provides different functionality to clients.

2) 'object': a method of organizing distinct entities, much like
programming languages have objects. Each object is uniquely identified
by an "object path" (basically a pointer) that looks like
"/org/foobar/Baz/235235". Each request sent to the service must be
directed to a specific object. Many services have a base object with a
well-known path that you use to bootstrap your communication with the
service.

3) 'interface': each request belongs to an interface, which is simply a
way of logically separating different functionality. The same way that
object-oriented languages like Java or C++ or GLib define an
"interface"; a specific API that different objects can implement, but
the caller doesn't need to know what type the object is, just the
interface. Interface names often look like D-Bus service names, but
have no relation to them.

4) 'method call': a request for an operation or information that a
client sends to the service; method calls are defined by an Interface
and are sent to objects.

Say you have a binary called "mcdonaldsd" that provides a D-Bus service
called "org.fastfood.McDonalds". Clients that want to talk to this
service use "org.fastfood.McDonalds" to direct requests to mcdonaldsd.

mcdonaldsd provides a base object called "/org/fastfood/McDonalds".
This object implements the "org.fastfood.McDonalds" interface, which
defines the method calls:

- GetItems(void) -> ao
- Order(ao) -> b

GetItems returns an array of object-paths representing all the things on
the menu that you can order. So if you call it you'll get something
like this returned:

[ '/org/fastfood/McDonalds/Item/0', '/org/fastfood/McDonalds/Item/1' ]

Each of these returned object paths is a pointer to an object;
mcdonaldsd probably even implements these as objects internally using
Java or C++ or GObject or whatever. These objects are probably
completely different (one may be a burger, one may be a drink) but they
all implement a common interface "org.fastfood.McDonalds.Item".

The org.fastfood.McDonalds.Item interface has the following method
calls:

- GetName
- GetType (either TYPE_BURGER, TYPE_DRINK, or TYPE_FRIES)
- GetPrice
- Consume

So even if you don't know what /org/fastfood/McDonalds/Item/0 is, you
still can get a lot of information about it, enough to decide whether
you want to order it or not.

Assume that item "0" is a "BigMac" and item "1" is "Coke". These are
clearly different objects, but each still has a name, a calorie count, a
price, and can be consumed.

Next, since each item is different (even though they all implement the
common org.fastfood.McDonalds.Item interface) each item type will
implement other interfaces that define functionality specific to that
type of item.

So item "0" (BigMac) implements the org.fastfood.McDonalds.Item.Burger
interface which has the following methods:

- Unwrap
- AddMustard
- RemovePickle (nobody likes those stupid limp pickles anyway)

And item "1" (Coke) implements the org.fastfood.McDonalds.Item.Drink
interface which has the following methods:

- PutLidOn
- InsertStraw
- RemoveStraw

Remember, since both objects *also* implement the base
org.fastfood.McDonalds.Item interface, you can use the Consume() method
to consume both items. But clearly, you don't want to include the
InsertStraw() method on the generic org.fastfood.McDonalds.Item
interface, because all items implement that interface, and it would be
pretty funny if you tried to call InsertStraw() on the BigMac object.
People would stare.

So interfaces are about logically separating method calls that have
specific functionality, and thus any object that wants that
functionality can implement that interface, instead of having every
object type duplicate all the calls of that interface.

So, with pseudocode:

# Get local proxy for the remove mcdonaldsd service
bus = get_service("org.fastfood.McDonalds")
mcds = bus.get_object("org.fastfood.McDonalds", "/org/fastfood/McDonalds")

burger_path = None
drink_path = None

# Lets read all the menu items
menu_items = mcds.GetItems()
for object_path in menu_items:
item = bus.get_object("org.fastfood.McDonalds.Item", object_path)
print "Item: %s price %s" % (item.GetName(), item.GetPrice())

# Now let's figure out what we want to order; we'll order
# the first burger we find and the first drink we find, but
# only one of each. We just had breakfast so we're not that
# hungry.
item_type = item.GetType()
if item_type == TYPE_BURGER and burger is None:
burger_path = object_path
elif item_type == TYPE_DRINK and drink is None:
drink_path = object_path

# We've found a burger and drink on the menu, lets order them
if burger_path and drink_path:
break

food = mcds.Order([burger_path, drink_path])
if food.len() == 0:
print "Oops, not enough money or something. Need to get a job."
sys.exit(1)

# Yay, we got our order. Now we take off the damn pickle
burger = bus.get_object("org.fastfood.McDonalds.Item.Burger", burger_path)
burger.RemovePickle()

# And we're taking this to go, so we need a lid and straw for the drink
drink = bus.get_object("org.fastfood.McDonalds.Item.Drink", drink_path)

drink.InsertStraw()

try:
drink.PutLidOn()
catch Exception, e:
print "Oops, straw already inserted!"

# We're distracted by the smell of the burger and put the
# straw in before we put the lid on. Oops. Take the straw
# out, put the lid on, and then re-insert the straw
drink.RemoveStraw()
drink.PutLidOn()
drink.InsertStraw()

# All ready. Now we can walk out and consume the burger and drink;
# note that even though burger_proxy and drink_proxy were created
# with D-Bus interfaces specific to their food type, we don't really
# need to create another interface just to call the generic Consume()
# method which both the burger and drink implement. Just give the
# method call the generic interface.

burger.Consume(dbus_interface="org.fastfood.McDonalds.Item")
drink.Consume(dbus_interface="org.fastfood.McDonalds.Item")

One is a Belkin N1 Wireless Notebook card, Part #F5D8011 - ath9k based, although I've gotten it recognized by the kernel and I can get an IP address via dhcp, as well as connected via WPA2, I can't seem to pass traffic.
Two is a Buffalo AG54 WLI-CB-AG54L, this one seems to be ath5k based, although I haven't attempted to use this one at all yet.

Currently towards the bottom of the todo list, is to get these both working, preferably using the N1 as an access point, so I can test out the speeds of the Efika MX's wireless. This has a secondary goal of seeing if the wireless issue that I have (currently I cannot seem to ssh into any wireless clients) is the AP I am using (pfSense based) or if it is something more; I'm guessing the former.

As some people have read, I got an Efika MX OpenClient from Genesi, and I've had a chance to work with it quite a bit. One of the things that I wanted to play with was Kismet on it, as I think the Efika MX Smartbook would make an excellent platform for wardriving (amongst many other things), being compact, lightweight, and having gps and wireless built in, with a very long battery life.

So, I gave it a shot, and it most definitely works (I've keyworded Kismet ~arm for the 2010.01.1 release) using the latest kernel (2.6.31.12.3-ER1) as of this writing, as well as the latest firmware for the wireless card from Ralink ( USB Firmware 22 released 03/31/2010. This is with the mac80211-based rt2800usb driver, NOT the rt3070sta driver from staging.

There is definitely a lot of potential in these little machines, and I really wish I had the means to buy more of them, just so that I had a few around to play with different things rather than having the one and swapping out the sdcard (assuming I'm not doing it on the pata ssd drive in the device.) I am really looking forward to when the smartbook gets released.

It was kind of a disaster.  I'm running on a Quad Core, 2.4ghz machine, and double clicking on a contact would take up to 25 seconds for the window to show up.  I was not a happy camper.  Watching htop, I could see that my DBus session bus was working hardcore.  100% cpu usage on 1 core.

No problem, I thought to myself, whipped open my handy terminal, ran "dbus-monitor --session" to watch the traffic that was causing it to use so much cpu and.... nothing.  Zilch.  There was no (apparent) traffic going on but the session bus was still using 100% cpu.

I popped over to the Gnome bugzilla, and started reading through bugs, but none were coming close to what I was seeing.  In desperation, I turned to the faithful Google.    And I searched... and came up empty - not so much empty as simply results that weren't helpful at all.

I let it go for a few days, asked a couple people if they were having any issues, and most don't use Empathy, so that was a bust.  Then I was looking around while I was "at work" which really meant I was sitting in the office as opposed to my room using the computer, and I came across Bustle; http://willthompson.co.uk/bustle/

Bustle is very nice, in that it can show you timings.  Once I had that compiled, I used Recordmydesktop to take a video of me using Empathy, with Bustle running, logging everything that went on with Empathy.  Then I popped in to the Empathy IRC channel (#empathy on irc.gnome.org) and mentioned in the channel that it was taking a long time for my IM windows to open, and pointed them at the video ( http://dev.gentoo.org/~steev/files/empathy-dbus.ogv (21MB)) and then at the two screenshots of Bustle ( http://dev.gentoo.org/~steev/files/screenshots/empathy-bustle1.png andhttp://dev.gentoo.org/~steev/files/screenshots/empathy-bustle2.png ), and Danni replied to me, asking why I was using the logger, when it shouldn't be enabled.  So I disabled it, and removed telepathy-logger from my system, re-compiled Empathy, and sure enough, the IM window pops up instantly.  I've removed the dependency as well as got rid of the useflag (with a note in the ebuild about why) and committed it to the Gnome overlay.  Due to Danni saying that no one should be using telepathy-logger, I've also package.masked it in the Gnome overlay.  I must say, using Bustle is *very* nice, and I'd like to thank Will Thompson for writing it.

I also smiled at the "How?" section of the Bustle website, considering that was the exact purpose for me downloading it.

I'm hoping to write an ebuild for Bustle, and apparently it is really easy to do with Haskell as the Gentoo Haskell team has a script that you run that will write the ebuild for you.  I haven't started working with it yet, but I definitely plan to, as Bustle is now definitely on my radar for usage in debugging what is going on with apps and their DBus usage.

Gentoos build their nests out of rocks, which are then jealousy guarded. Particularly nice rocks are offered as gifts by male Gentoos to females to curry favor.

All this time my ex's thought I was just being cheap...

Just posting it here for future reference

gsl.ko:

license=Proprietary
description=GSL driver
author=Advanced Micro Devices Inc.
depends=

gpu_z430.ko:

license=Dual BSD/GPL
description=Device driver for AMD 3D graphics core
author=Advanced Micro Devices Inc.
depends=gsl

Anyone happen to know where to find the GPL source for that gpu_z430 module?